# Capability Coverage Strategy

## Baseline

The supplied V1 audit contains:

- 209 reviewed screens;
- 172 normalized capabilities;
- 1,386 visible UI-control evidence rows;
- 1,140 API endpoint declarations; and
- 894 model/type declarations.

The audit's central finding is correct: the system is not primarily missing nouns or routes. It is missing coherent lifecycles, scope, state, dependency visibility, authority, recovery, and audit.

## Do not replace 209 screens with another screen catalog

Each capability must be assigned one intentional design outcome:

1. conversation;
2. inline instrument;
3. Element Lens;
4. Element Stage;
5. guided flow;
6. Atlas orientation layer within the Field;
7. Action Gate;
8. execution timeline;
9. Realm Lens;
10. operator/admin surface;
11. automation/API-only with visible status and Record; or
12. explicitly retired.

A capability may use several patterns across its lifecycle, but it should have one primary home.

## Capability families

| IDs | Family | Count | Primary design treatment | Priority |
|---|---|---:|---|---|
| CAP-001–014 | Identity, account, and access | 14 | Preserve the strong outside-the-Field flows; bring account, entitlement, wallet, and recovery into guided flows and Lenses. | P1 |
| CAP-015–025 | Onboarding | 11 | Conversational Realm/Ally setup with reviewable generated structure and resumable progress. | P1 |
| CAP-026–038 | Agents and relationships | 13 | Agent/Presence Lens, conversational creation, proposed changes, lifecycle controls, relationship Atlas layer. | P1 |
| CAP-039–047 | Chat, voice, and action timeline | 9 | Main conversation, contextual routing, event timeline, voice state, cancellation, and recovery. | P0 |
| CAP-048–063 | Skills, automations, tools, and approvals | 16 | Guided setup, compact instruments, execution timeline, Action Gates, operational Pulse, and history. | P0 |
| CAP-064–080 | Wisdom, graph, and prompts | 17 | Realm/Agent Wisdom Lens, Source Elements, retrieval instrument, dependency Lens, health Pulse, proposed diff. | P0 |
| CAP-081–096 | Communities, contexts, roles, and invitations | 16 | Realm Lens, Atlas, guided invitation, permission preview, membership Record, notification brief. | P0 |
| CAP-097–117 | Studio and game building | 21 | Conversational plan, hierarchical Element composition, Stage, validation instrument, diff, version and publish Gate. | P1 |
| CAP-118–130 | Assets and scenes | 13 | Collection tray, type-specific Element Lens, visual Stage, dependency impact, generated knowledge and sync Pulse. | P1 |
| CAP-131–143 | Runtime, progress, and analytics | 13 | Scene/Runtime Stage, live Pulse, event timeline, progress Lens, analytical instrument, privacy controls. | P2 |
| CAP-144–161 | Markets, governance, treasury, and DUNAs | 18 | Proposal instruments, governed Gates, transaction timelines, Treasury Lens, deterministic Records. | P1/P2 |
| CAP-162–172 | Public, CMS, publishing, and operations | 11 | Keep public work outside the Field; use editorial Stage, release Gate, operations Pulse, and explicit retirement. | P2 |

## P0 product stories

The first design system is incomplete until a user can:

1. State an intention to Ki without selecting a module first.
2. See which Realm is active and understand its purpose.
3. Receive a focused attention brief rather than a wall of notifications.
4. Bring an Element into the main conversation by selecting, searching, mentioning, or dropping it.
5. Preview an Element and understand what it is, where it came from, and why it is relevant.
6. Expand an Element without losing the conversation.
7. Ask about an Element through Ki or the relevant Realm Actor.
8. Pin or stage an Element for sustained work.
9. Compare or compose several Elements when the task requires it.
10. Receive a proposed change with sources, impact, authority, and reversibility.
11. Complete an appropriate confirmation, approval, vote, signature, or governance Gate.
12. See long-running work progress and cancel, retry, or recover it.
13. Receive a durable receipt or Record after an Action.
14. Switch Realms without losing the prior Focus.
15. Enter the Atlas to understand the wider system and return to the same work.
16. Use connected systems such as calendars without managing their interfaces unless needed.
17. Inspect and improve a Realm's Wisdom, Stance, Abilities, Automations, and Connections on demand.
18. Invite collaborators, then continue to experience the shared work—not a permanent people dashboard.

## Cross-cutting acceptance contract

Every capability review must answer:

- What user intention triggers it?
- What Realm owns the context?
- Which Presence or Agent acts?
- What is the Source of authority?
- Which Elements enter or change?
- What is visible by default?
- What appears only on request or exception?
- Which states can occur?
- What can fail, expire, become stale, or partially complete?
- Which Gate is required?
- What Record persists?
- How does the user return to the originating conversation?

## Coverage phases

### Phase A — Interaction foundation

Cover CAP-039–096 through the main conversation, Element lifecycle, Realm Lens, Action Gate, timeline, and Atlas.

### Phase B — Creation foundation

Cover CAP-015–038 and CAP-097–130 through conversational setup, collection, Lens, Stage, diff, dependency, version, and publish patterns.

### Phase C — Consequential systems

Cover CAP-144–161 through authority previews, governance, Treasury, transaction phases, receipts, and recovery.

### Phase D — Runtime and operations

Cover CAP-131–143 and CAP-168–172 through operational Pulses, live timelines, analytics instruments, privacy, and operator surfaces.

### Phase E — Outside-the-Field completion

Complete CAP-001–014 and CAP-162–167 using the existing strong web/onboarding language, then connect those flows cleanly to the inside-Studio system.

## Definition of coverage

A capability is not covered because a route, button, or API exists. It is covered only when its entry, normal flow, important states, authority, exception handling, result, and recovery path are intentionally assigned and reviewable.
