Unclassified
05 · Work View
Work as the common unit of activity — ownership, participants, objectives, context, state, evidence, dependencies, outcomes, and handoffs.
Work Is the Coordination Medium
Humans and AI do not coordinate by re-explaining the organization in conversation. They coordinate through durable Work.
Work is the common unit of activity that carries objective, context, and state — so humans and AI can hand off without losing continuity.
BUSINESS CONTEXT
│
▼
WORK
┌─────────────────────────┐
│ objective │
│ participants │
│ business context slice │
│ state & history │
│ evidence │
│ dependencies │
└─────────────┬───────────┘
│
┌─────────────┼─────────────┐
▼ ▼ ▼
HUMAN TWIN SPINE AGENT
Workbench Workbench (actor)
│ │ │
└─────────────┼─────────────┘
▼
OUTCOME
│
▼
VERIFY → SPINE
What Work Contains
| Field | Meaning |
|---|---|
| Ownership | Who is responsible. Every Work has a human owner, even when an agent is executing a subtask. |
| Participants | Human, Twin, Spine Agents involved — each with identity and authority. |
| Objective | What business objective or outcome this Work serves. |
| Context | The Business Context slice and Active Context Bundle it is grounded in. |
| State | Current state and history (created → assigned → in-progress → awaiting approval → executed → verified → closed). |
| Evidence | What proves what actually happened — receipts, verification, reconciliation. |
| Dependencies | What this Work depends on and what depends on it. |
| Outcomes | What was achieved, with what evidence, reconciled to what Spine update. |
| Handoffs | Governed transfers between human, Twin, and agents — with full context, not a summary. |
Work Owns the Thread
- A Work thread carries communication — messages, agent updates, Twin reasoning — all scoped to the Work and the Business Context it belongs to.
- A Work handoff moves state and evidence, not just text. The next participant hydrates from the Work object and the Spine, not from a pasted transcript.
- Closing Work is not a UI action. It is a verified Spine update with projection invalidation and rehydration.
Human / AI Participation
| Pattern | How it works |
|---|---|
| Human owns, Twin assists | Twin assembles context, proposes plan, drafts approval; human decides. |
| Human delegates to agent | Agent takes a subtask with its own continuity and authority; posts evidence back to Work. |
| Agent → agent handoff | Second agent hydrates from same Work + Business Context; no re-briefing. |
| Agent → human return | Human reviews agent evidence, verifies, and closes or iterates. |
All governed. All auditable.
Where to Go Next
<CardGroup cols={2}>How Work moves: Business Intent → Context → Plan → Govern → Execute → Verify → Spine.
How multiple agents share Work without reconstructing context.
How the Active Context Bundle for this Work is built for each participant.
</CardGroup>