> ## Documentation Index
> Fetch the complete documentation index at: https://docs.theubik.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace basics

> Understand the queue, evidence, actions, and audit trail that structure daily trade work.

The workspace is built around one operating question: what needs a decision before it becomes customer risk, margin leakage, clearance delay, or owner ambiguity?

## Main areas you will use

| Area            | Purpose                                                                                  |
| --------------- | ---------------------------------------------------------------------------------------- |
| Operating queue | Work prioritized by urgency, risk, owner, and readiness for review.                      |
| Source context  | The email, document, meeting, chat, or system detail behind the recommendation.          |
| Action panel    | The reply, task, approval request, or handoff proposed for review.                       |
| Activity trail  | The record of who reviewed, edited, approved, rejected, assigned, or escalated the work. |

## Queue states

| State                                                    | When you see it                                                                   |
| -------------------------------------------------------- | --------------------------------------------------------------------------------- |
| <span className="ux-label is-primary">Now</span>         | Review before lower-priority work because a promise, owner, or deadline may move. |
| <span className="ux-label is-support">Found</span>       | Ubik detected a change that may affect downstream plans.                          |
| <span className="ux-label is-destructive">Analyse</span> | The item needs human judgment before a recommendation is safe.                    |
| <span className="ux-label is-success">Ready</span>       | The action is prepared and waiting for approval, assignment, or writeback.        |

## Handoff modes

Every queue item carries a handoff chip that tells you who has the next move.

<span className="ux-handoff is-human">Human → Review</span>  
<span className="ux-handoff is-agent">Agent → Drafting</span>  
<span className="ux-handoff is-system">System → ERP queue</span>  
<span className="ux-handoff is-final">Final → Committed</span>

## Good operator habits

<CardGroup cols={2}>
  <Card title="Source before speed" icon="search-check">
    Approve when the source, owner, and action are clear. Fast unsupported work creates downstream rework.
  </Card>

  <Card title="Route by authority" icon="route">
    Move routine work through the queue; escalate price, margin, promise-date, finance, or compliance decisions.
  </Card>

  <Card title="Keep the trail useful" icon="history">
    Leave enough context for a future operator to understand what changed and why the action moved.
  </Card>

  <Card title="Teach the memory with variety" icon="brain">
    RFQs, PO chases, supplier follow-ups, margin checks, meeting recaps, and vendor reviews make deviations easier to spot later.
  </Card>
</CardGroup>

## Theme and readability

Ubik supports light and dark modes. Choose the mode that gives your team the clearest daily read, especially when reviewing grey secondary text, source snippets, and long approval trails.