# Start Here

## What this package answers

It shows the strongest current evidence for how Kiduna should feel and behave outside and inside the Studio:

- Outside the Studio is a polished web journey into Kiduna.
- Inside the Studio is a desktop/laptop application experience built around one active Realm, one current Focus, one dominant conversational surface, and one continuous conversation.
- Instruments, Sources, Elements, decisions, and Records appear because the work requires them, then recede.
- Realm differences come from intelligence, Stance, contribution rules, authority, and Records—not decorative skins.

## What is inherited, accepted, proposed, or unresolved

- **Canonical:** Kiduna Core Taxonomy 1.3.3 and its stated provenance.
- **Accepted design constraints:** Gate 0, Gate 1, and Gate 2A decisions recorded in `program-definition/DECISION_LOG.md`.
- **Current design evidence:** Gate 2B.1 primary scenes; owner revision/acceptance remains open.
- **Working proposals:** Focus, Lens, Stage, Attention Thread, Contribution Envelope, one-center shell, and other terms explicitly labeled non-canonical.
- **Unresolved:** all items in `OPEN_DECISIONS_AND_RISKS.md` and `program-definition/OPEN_DECISIONS.md`.

## Review order

1. Outside the Studio steps 1–5.
2. Inside the Studio designs 1–3 to understand the shared shell.
3. Inside the Studio designs 4–6 to understand Realm-specific intelligence and trust.
4. Presence Story for human purpose.
5. Engineering Notes for observable behavior and boundaries.
6. Program contracts and evidence only after the visual walkthrough.

## Stop condition

Do not advance from planning into production implementation when a decision affects authority, privacy, clinical custody, consent, governance, provenance, retention, correction, treasury, identity, or agent autonomy. Record the question and return it to the design/product process.
