One room
Line, Watch, field, selected causal line, tape, one drawer, and the mobile machine strip. No pages, tabs, assistant pane, or permanent navigation rail.
Design package / August 10, 2026
Work OS V2
The interaction target for the real Work OS operator: one room for consequential work, with proof, Nathan's word, machine work, outcomes, and receipts kept on one causal line.
- Direction
- Switchboard + Causal Loom
- Prototype
- Complete and clickable
- Verification
- 36 E2E / 153 safety checks
- Production
- Not wired; five arcs remain
Selected room
One causal field, not an AI chat home
Binding contract
What the next team must preserve
consequence proof your word machine work outcome receipt
Truth over theater
Facts and maybes remain distinct. Progress uses named stages and real units. Every claimed action reaches a trace or receipt.
Nathan keeps authority
Suggestions are free; acting requires his word. Mail stops at a reviewed, receipted draft. Sending is never automated.
History is append-only
Words remain verbatim. Machine interpretation stays separate. Corrections, undo, close, and reopen append rather than erase.
Handoff library
Open these in order
- Clickable prototype The selected interaction target. Exercise it before reading implementation detail.
- Prototype-to-product implementation handoff Production owners, component boundaries, five build arcs, tests, and invariants.
- Complete design guide Room hierarchy, visual constitution, interaction grammar, mobile, motion, and copy.
- Internal Work OS tool guide How to build useful internal tools without creating maintenance work or fake automation.
- Mobbin research addendum What current AI products taught us, what we borrowed, and what geography we rejected.
- Completion and verification audit Requirement-level evidence, repaired gaps, honest production boundary, and remaining gate.
Production sequence
Build the real product in five arcs
Word
Real append-only words, options, judgments, correction, and receipts.
Work
Editable effort proposals, approval, factual runs, stop, replay, and rejection.
Memory
Dig, sourced deltas, promises, learned arithmetic, and corrections.
Custody
Draft review and placement, provider receipts, close, and reopen.
Daily driver
Real data, responsive behavior, keyboard, observability, rollout, and rollback.
Current proof
What the prototype actually proves
36end-to-end checkpoints
153control and safety checks
44/44declared actions exercised
0external requests or console errors
It proves the interaction design and local behavior. It does not prove authenticated persistence, live source freshness, provider effects, production orchestration, or deployment readiness.