# Working Plan

## Collaboration cadence

Use short design rounds. Each round should contain:

1. one design question;
2. one bounded artifact;
3. one recommendation;
4. one review decision; and
5. one logged consequence for the next round.

Do not disappear into a broad prototype pass. Do not ask the user to review dozens of unrelated screens at once.

## Gate 0 — Interaction thesis

**Status:** Accepted July 19, 2026

### Question

Is the default Studio presentation a focused Realm conversation/workspace, with a broader Atlas orientation view entered on demand within the Field?

### Deliverable

The brief, diagnosis, and three-scene experiment described in this pack.

### Completion criteria

- The dominant surface is agreed.
- The roles of Chat/Work, Element Lens/Stage, and Atlas are distinct.
- The user can state what still feels wrong in terms of hierarchy rather than decoration.

## Gate 1 — One-center shell

**Status:** Accepted July 19, 2026

### Question

Can one shell move between calm conversation, a structured instrument, and an expanded Element without losing clarity?

### Deliverable

Three connected high-fidelity scenes using the same Realm and visual system.

### Completion criteria

- The primary Focus is identifiable in three seconds.
- One surface has at least 60% of the visual weight.
- No more than three objects appear elevated.
- The active Realm, Ki, and next action are clear.
- The same conversation persists across all scenes.

## Gate 2 — Realm intelligence

**Status:** Gate 2A accepted July 19, 2026. Gate 2B.1 primary scenes complete and included in a preliminary engineering-planning handoff; owner review remains open. Gate 2B.2 exceptional scenes have not started.

### Question

Does each Realm feel capable, contributive, and legitimately agentic before the user configures its machinery—and can collective agency remain understandable without surveillance or a dashboard?

### Deliverable

### Gate 2A deliverable

- Canonical Taxonomy Version 1.3.3 and change provenance;
- shared collective-agency, contribution, attention, and Record model;
- Field–Realm–Panel–Scene–Portal semantic model;
- three Realm Intelligence Contracts:
  - Inner Clinic research/health Alliance;
  - The Nature of Work transformation Organization; and
  - 2nd Cavalry living-history, service, and connection system;
- nine intention flows and nine substantive exceptional-condition flows;
- cross-Realm behavior matrix; and
- exactly six written Gate 2B scene briefs, one normal and one essential exception per Realm.

### Gate 2B deliverable after Gate 2A acceptance

Six behaviorally faithful, reviewable scenes applying the accepted Realm contracts to the accepted one-center shell. Gate 2B must not design Atlas or begin production engineering.

Gate 2B is being reviewed in two bounded rounds:

- **Gate 2B.1 — primary scenes:** complete in the separate local review site at `../kiduna-studio-gate-2b1`; owner decision pending.
- **Gate 2B.2 — exceptional scenes:** not started; begin only after explicit owner direction.

### Preliminary engineering handoff boundary — July 19, 2026

The package created between Gate 2B.1 and Gate 2B.2 is authorized for production-engineering planning and reversible foundational exploration only. It is not Gate 7, does not approve unresolved proposals, and does not authorize engineers to infer a production domain model from fixture data. Gate 2B.2 and later design gates remain necessary before implementation completeness can be claimed.

### Completion criteria

- Each Realm provides different useful intelligence and instruments.
- Wisdom, Stance, Abilities, Automations, and Connections are inferable through behavior.
- Calendars, integrations, and operational plumbing stay hidden unless relevant.
- Limits, privacy, and required authority remain understandable.
- Contributions preserve Source, scope, visibility, authority, provenance, retention, correction, and resulting Record.
- Ki can reflect eligible collective Wisdom without exposing private conversation, inventing consensus, or creating person-level surveillance.
- Field activity and cross-Realm attention remain understandable without requiring a continuously visible Field or notification dashboard.
- Medical behavior preserves source applicability, consent, uncertainty, clinician review, privacy, and escalation limits.
- Historical behavior preserves originals, rights, contested accounts, reconstruction status, editorial authority, and correction.
- Confidential, proposed, legacy, and legally unverified source material remains distinguishable from canon.
- Each Gate 2B scene has observable acceptance criteria and tests one named hypothesis.

## Gate 3 — Element grammar

### Question

Can every important thing be recognized, previewed, addressed, expanded, staged, acted upon, and returned?

### Deliverable

One Element grammar board plus four live flows:

- Source;
- Artifact;
- proposal/decision;
- schedule or other interactive data instrument.

### Completion criteria

- Entity type is clear without relying on color alone.
- Provenance, state, and relevance appear at Preview.
- Lens and Stage have distinct purposes.
- “Move into main chat” has consistent behavior.
- proposed changes, Gates, progress, and receipts are connected.

## Gate 4 — Atlas and context movement

### Question

Can the user get the big picture without the map becoming the task interface?

### Deliverable

A three-state Atlas sequence:

- open from a live Focus;
- orient around relevant Realms and work;
- enter or return while preserving context.

### Completion criteria

- Atlas is filtered by intention.
- Layers are deliberate and sparse.
- Realms, active work, and relationships are distinguishable.
- The prior conversation and selected Elements survive the transition.

## Gate 5 — Capability-pattern audit

### Question

Can the 172 capabilities be covered by the accepted patterns without recreating 209 screens?

### Deliverable

A capability-to-pattern matrix with priority, state, authority, and gap.

### Completion criteria

- Every capability has an intentional primary design outcome.
- All consequential and asynchronous capabilities have Gate, progress, failure, retry, and Record decisions.
- Operator-only and retired capabilities are explicit.
- Terminology conflicts remain flagged.

## Gate 6 — Visual, motion, and conversational system

### Question

Does the accepted interaction system carry the right Kiduna feeling consistently?

### Deliverable

Tokens, type, spacing, surfaces, icon grammar, motion rules, conversation components, and accessibility states.

### Completion criteria

- The inside feels continuous with outside-the-Field work.
- Sky blue remains primary; gold and mint remain rare semantic signals.
- Geometry is composed and stable.
- Motion explains state and scale.
- Contrast, text size, keyboard focus, reduced motion, and responsive behavior are specified.

## Gate 7 — Integrated prototype and engineering handoff

### Question

Can engineers understand and implement the system from validated interactions rather than aesthetic interpretation?

### Deliverable

- scoped functional prototype;
- prioritized user stories;
- canonical component and pattern inventory;
- state and acceptance matrix;
- interaction and motion specification;
- capability coverage audit;
- `AGENTS.md` and `CLAUDE.md` engineering controllers;
- validated reusable skills; and
- a review walkthrough.

### Completion criteria

- No design proposal is mislabeled as canonical taxonomy.
- Every prototype behavior traces to a user story and pattern.
- Every accepted pattern includes normal, exceptional, authority, and recovery states.
- Engineers can walk through the system without oral explanation.
- Deferred capabilities and unresolved decisions are explicit.

## Turn protocol

For each round:

1. Codex states the precise question and expected review time.
2. Codex produces only the bounded artifact.
3. The user responds with keep/change/remove notes.
4. Codex logs the decision and updates affected documents.
5. Codex proceeds only to the next agreed round.

Target review time per round: five to fifteen minutes.
