# Work OS V2 - Seven Product Goals

Date: August 9, 2026
Status: design package ready for Nathan's judgment

The earlier Decision Studio package is research material. The destination is the
one-room Work OS described by the authoritative handoff.

## Product definition

Work OS is one continuous causal field:

`consequence -> proof -> your word -> machine work -> outcome -> receipt`

It is the operating interface over the existing Work OS substrate. It is not an
AI chat product, dashboard suite, or parallel orchestration system.

## Goal 1 - Lock the product contract

Reconcile the eleven laws, authoritative handoff, reference instrument, flow
mockups, production surface, and safety boundaries.

Status: **complete**

## Goal 2 - Convert research and V1 lessons into product rules

Deep-search current AI work, research, draft, and learned-state interfaces on
Mobbin. Audit the tightened V1 instrument for what V2 carries, reworks, and
deliberately leaves behind.

Status: **complete**

## Goal 3 - Select the room-level design

Explore complete directions and choose a distinctive composition that preserves
dense scanning and the full causal story.

Selected: **Switchboard structure plus Causal Loom focus behavior**

Status: **complete**

## Goal 4 - Build the entirely clickable product prototype

Cover command parse, dense triage, proof, Nathan's word, effort proposals, live
efforts, rejection, corrections, capability growth, draft custody, receipts,
the actionable Dig, people court state, five-second recovery, weekly close,
keyboard, both themes, reduced motion, and mobile.

Status: **complete**

## Goal 5 - Verify every visible promise

Exercise every control, command class, keyboard path, safety invariant,
responsive state, and provider boundary. Fix accessibility and interaction
defects found by the audit.

Status: **complete**

Evidence:

- 36 end-to-end browser checkpoints;
- 153 control and safety checks;
- 28 isolated scenarios;
- all 44 declared controls exercised;
- no external requests or browser console errors.

## Goal 6 - Publish the product and build guides

Deliver the rationale, design guide, internal-tool guide, implementation
handoff, final recommendation, and completion audit.

Status: **complete**

## Goal 7 - Confirm the room and begin production arcs

Collect Nathan's room-level design judgment. If confirmed, bind the design to
the existing `/operator` React tree and canonical Work OS contracts in five
arcs: Word, Work, Memory, Custody, and Daily driver.

Status: **waiting for Nathan's design judgment**

## The checkpoint

Evaluate the prototype as the Work OS itself:

> Does this room feel like an operator already working inside your world, and
> what still feels like software you would have to manage?

The next engineering move depends on that answer. If the room is right, start
Arc 1. If the room is wrong, revise the composition before wiring production.
