---
name: audit-kiduna-capabilities
description: Audit whether a Kiduna Studio design or prototype genuinely covers the inherited V1 capability inventory. Use when reviewing screens, journeys, prototypes, Realm definitions, or engineering handoffs; mapping capabilities to interaction patterns; finding lifecycle, authority, exception, provenance, or recovery gaps; and distinguishing visible controls from complete user outcomes.
---

# Audit Kiduna Capabilities

Read [capability-families.md](references/capability-families.md). If the working pack includes the source catalog, use capability IDs as the stable keys.

## 1. Set the audit scope

Record the artifact version, source version, persona, Realm, and journeys being audited. State explicitly which capabilities are out of scope rather than treating absence as failure.

## 2. Evaluate outcomes, not controls

A capability is not covered merely because a route, endpoint, button, card, or model exists. For each in-scope capability, record:

- user outcome and entry point;
- chosen interaction pattern;
- normal lifecycle states;
- privacy, visibility, role, permission, and authority behavior;
- connected-data or Actor dependencies;
- error, interruption, recovery, and reversal behavior;
- resulting Record, provenance, and audit evidence;
- design acceptance criteria and evidence location.

## 3. Classify coverage

Use one status only:

- **Proven** — the outcome and all material states are demonstrated with evidence.
- **Partial** — the happy path exists, but states, authority, recovery, or evidence are incomplete.
- **Claimed** — prose or a control names the capability, but the outcome is not demonstrated.
- **Missing** — no meaningful coverage exists.
- **Out of scope** — explicitly deferred with rationale and dependency.

## 4. Identify systemic gaps

Group gaps by interaction pattern and system behavior, not only by capability ID. Look especially for repeated omissions in:

- proposal, authorization, execution, receipt, and rollback;
- privacy and visibility boundaries;
- state change and attention;
- provenance and Records;
- connected services and unavailable dependencies;
- Compute and Treasury consequences;
- Realm intelligence and appropriate Stance.

## 5. Deliver the audit

Return:

1. coverage summary by capability family;
2. capability-level matrix with evidence links;
3. systemic gap register;
4. contradictions and missing evidence;
5. prioritized design experiments or decisions;
6. measurable conditions for moving each Partial, Claimed, or Missing item to Proven.

Do not invent product requirements to close gaps. Label new proposals.
