# PROMPT 6 — Studio in Action: four representative views

**YOU ARE EXECUTING, NOT REVIEWING.** This is a single-session assignment. Controlling vocabulary: `01_CANON-BRIEF.md` (taxonomy v1.3.6). Personas and all fixture data: `PERSONAS.md` and `data/personas.json` from Prompt 1 — do not re-derive them. Design continuity: your own `DESIGN-CANON.md` and `LAYOUT-AND-INFORMATION-ARCHITECTURE.md` remain in force. The design system is settled — fine-tune, never restyle.

## The assignment

Design **Kiduna Studio in action**: four high-fidelity views, one per lead persona, that together demonstrate the whole Studio grammar — the Field, Panels across the opacity continuum, Media components (labels, icons, connectors, widgets) appearing in both the Field and in Ki's panel, and the live interplay between acting in the Field and talking with Ki. These four views become the reference set we iterate against, so make each one a real working moment drawn from the persona's fixture, not a showcase collage.

**The layout constant:** Studio is the desktop Surface. The Field occupies the primary area; **Ki is the persistent conversational panel on the right**, carrying text, voice affordance, and interactive Media (chips, buttons, sliders, press-and-hold controls, structured cards). Tapping something in the Field and saying something to Ki feed one system: every view must show at least one moment where a Field selection changes Ki's context and one where a Ki exchange changes what the Field shows.

## View 1 — Alice · authority you can inspect

Alice is in **Service Alliance**, reviewing what changed while she was away: a grant awaiting her confirmation and a Record comparison (two versions of an operating agreement). Show: Realm Elements with classification chips; an **inspect** affordance opened on the grant (true type, containment, permissions, provenance); a version-comparison Panel (translucent — she's referencing the Realm behind it); Ki summarizing exactly what the grant authorizes and what still depends on Bob, ending with a **Confirmed**-level accept chip in the Ki panel. Her script is terse text; Ki answers with facts and one clear next action. Failure state to include: a stale authority warning (a grant referencing a role that changed).

## View 2 — Bob · the span of care

Bob is in his **Cell view** (Kinship Duna context): twelve invitees as aggregate-activity Elements (plain time-based states — active now / this week / this month / quiet / paused — never scores), two flagged quiet; invitation states for two pending invites; a role agreement he's waiting on; this month's lineage distribution as a fact card. Show: Ki in voice mode (transcribed) helping him prepare two *separate* check-ins without inferring why anyone is quiet; a distribution walk widget (every hop inspectable); the invite-creation card (Kinship Code · Handshake · private trust level · private relationship note · private welcome context) collapsed but present. Warmth without surveillance is the design test.

## View 3 — Carol · the catalyst's bench

Carol is in **Dunaversity**, mid-build on *How to Be a Cricket Fan*: Wisdom Drops as labeled containers (with attribution and classification chips, all four treatments visible); the movement skeleton with the Curator's placement rationale on one item; the contribution queue holding one submission being **accepted** (Record) and then **integrated** (distinct step); a versioned Media comparison (draft 3 vs draft 4) side-by-side with Ki; and the **press-and-hold Deliberate publish** control in its gold treatment — shown pre-commit, with the "what's public" preview Panel (opaque — full attention). Her script: expansive voice turning decisive; Ki reflects the pattern back and marks the exact moment something becomes public.

## View 4 — David · boundaries and ceilings

David is in **Mountain River Trail**, inspecting a small Actor he built for field Records: the Actor's card showing its bounded authority (reads, tools, Compute ceiling, duration, Realm context — all explicit); a Compute meter as plain fact; three offline-prepared draft Records in a pending state ("will commit on verified connection + your confirmation"); a classification boundary moment — Ki declining to retrieve something outside the Realm's permission, quietly, with the reason inspectable. His script: terse, sequential; include his offline-return moment ("what happened while I was out?" → a compact, factual digest). Low density, field-legible, recovery and safety visible.

## Requirements across all four

1. Every rendered Element carries the inspect affordance; show it opened at least once per view.
2. Confirmation grammar consistent and visible: Autonomous (silent, logged), Confirmed (one tap), Deliberate (press-and-hold, gold), with the control never being the permission — the authority line appears in the Ki panel each time.
3. The four privacy classifications appear across the set with their four unmistakable treatments.
4. Money renders as facts; $KIDUNA at the fixture price (1 $KIDUNA = 0.25 USDC, dated); the execution-mode chip visible where anything is simulated.
5. Persona-true Ki scripts (per the cross-persona review matrix): at least four exchanges per view, showing one Field→Ki and one Ki→Field interaction each.
6. No feeds, no scores, no navigation chrome — composition, not menus. "In Kiduna," never "on Kiduna."

## Deliverables (files, versioned — never loose prose)

`studio-in-action/` containing: four HTML mocks in the existing design system (`alice.html`, `bob.html`, `carol.html`, `david.html`) driven by `data/personas.json` · `SPEC.md` (layout constants, Panel opacity choices, component inventory additions with names) · `KI-SCRIPTS.md` (the full scripted exchanges per view) · updates to `ROUTE-MANIFEST.md` · and a closing **taxonomy impact statement** ("Taxonomy updated" with specifics, or "No taxonomy change" with why). STOP after delivering; wait for markup before any further view.
