# Kiduna Studio Design-System Instructions

## Objective

Design a focused, Realm-aware conversational Studio that covers the accepted capability baseline without reproducing a page-per-feature product.

## Source order

1. Canonical Kiduna taxonomy where supplied.
2. Owner decisions and accepted design gates.
3. This pack's approved design-system documents.
4. V1 capability evidence and repository snapshots.
5. Historical prototypes as design evidence only.

Never silently merge conflicting terminology or treat a proposal as canonical.

## Required working method

1. Read `START_HERE.md`, `OPEN_DECISIONS.md`, and the document relevant to the current gate.
2. Use the appropriate skill in `skills/`.
3. State the single design question for the round.
4. Produce one bounded artifact and measurable review criteria.
5. Separate inherited requirements, owner decisions, proposals, and missing evidence.
6. Update the decision register after review.
7. Do not proceed to a later gate without the required acceptance.

## Design invariants

- One active Realm, one current Focus, and one dominant surface.
- Main conversation/work is default; Atlas is entered on demand unless owner review changes this.
- Elements support Preview, Address, Lens, Stage, Action, Gate, progress, and Record as appropriate.
- Connected systems remain hidden until relevant.
- Collaborators are visible through contribution, presence, and authority—not permanent equal-weight portraits.
- Consequential Actions expose authority and require the correct human or governance Gate.
- Use a restrained espresso, cream, sky-blue, gold, mint, and danger palette.
- Prefer composed natural geometry over irregular organic silhouettes.
- Design lifecycle, failure, retry, cancellation, expiry, staleness, partial completion, and recovery.

## Coverage rule

A capability is not complete because a route or control exists. It must have an intentional entry, normal flow, state model, authority, exception handling, result, and recovery path.

## Prototype rule

Do not build a broad prototype until Gates 0–4 in `WORKING_PLAN.md` are accepted. Prototype only the accepted scenes and patterns.
