# Design Round 7 — Kiduna Studio, in the Field
**The prompt Moto runs in Claude Design · 2026-07-11 (revised, evening canon) · read `skill-updates/cofounder-canon-2026-07-11.md` FIRST — it supersedes older track text**

---

You are designing Round 7 for Kiduna: **Kiduna Studio, whole.** Studio is what we're building next, and it's the tool we'll use to build everything else — we create from within, so Studio has to be good enough to live in.

**The canon that changes everything you draw:** **The Field is the only interface.** There is no Field-and-Chat split anywhere in Kiduna — chat lives inside the Field's **contextual HUD**, which can become **opaque** when the user wants to focus on an action or a conversation. **Everything the end-user needs is represented in the Field**: a box full of Bluesky posts is a literal box, a Project is a place, a tool is an object, an ACTION appears where you are when something needs you. **Studio has the same UX as Live — the Field** — the difference is what it's *for* and where it runs: Studio is on your computer, where everything gets entered, uploaded, and defined, with access to your files and to connected tools and systems — Claude Code, Codex, Google Docs, Meet, whatever you wire in. **Projects** (a first-class primitive within Organizations) are Studio's central organizing principle. Two agent types only: **Allies** (represent, are guided by, and support members) and **Actors** (don't represent members, aren't controlled by members — they have functions; Builders and Creators can name their own Actor types). Servers form a mesh; trusted collaboration runs through the server. Relationships are trusted/untrusted; resources are registered/unregistered.

## Inputs (attached zip: the Kiduna Kit)

Read `skill-updates/cofounder-canon-2026-07-11.md` first, then `create-from-within.md`, `surfaces.md`, `architecture.md`, `integrations.md`, `organizations.md` §2 (the real dunas), `roles.md` §1 (the real people), `legal.md` (binding copy rules), `sentinel.md` (never render meters). Rounds r2–r6 are precedent for grammar (cards, receipts, gold/light, press-and-hold), but their Chat-as-separate-surface layouts are **superseded** — translate what survives into the Field + HUD. `_ds/…/colors_and_type.css` binds every pixel; carry `_ds` in your output.

## Deliverable 1 — The Field grammar on a desktop (the foundation of the round)

Before any feature: design how the Field works as the entire interface on a big screen. The contextual HUD — what it holds, how it changes with context, how it goes opaque for focus (a conversation, an ACTION, a document) and how you come back; where chat lives inside it; how voice rides it. How things are *represented*: information as objects and containers (the box of Bluesky posts, worked literally), tools as things with places, people and Allies present in space, Actors visibly at their functions. How ACTIONS appear in the Field when something needs you. The three Scene grades (crafted · generated · on-the-fly words-and-pixels) as one continuous fidelity ladder — show the same space at all three.

## Deliverable 2 — The Project as a place

A Project is Studio's spine: design its creation inside an Organization (a duna command with its receipt), its anatomy (purpose, members and grants, connected tools/agents/systems, Records, state), and its life **as a Scene in the Field** — walking into a Project, seeing its state at a glance, its history as something you can inspect, its ACTIONS surfacing where you stand. Use a real one throughout: **The Ceremony Machine's Lightbrush integration** — Moe's tools (Dowbot, Digital Dolly, RenderDeck) as connected systems with places in the Project's Scene, Elias's work visible as it happens.

## Deliverable 3 — Entering, uploading, defining

Studio is where everything comes into the Kidunaverse. Design the ingestion grammar in Field terms: drop files from your computer and watch them take their place (access level set at add-time, one gesture); connect an outside system (Google Docs, Meet, an MCP server) and see what it becomes in the Field; define things — an Actor type a Builder names and purposes, a skill, an automation — as conversation with your Ally plus objects in the space, never settings forms.

## Deliverable 4 — The coding-agent seam

The package handoff, in the Field: Studio composes a self-describing package (context, ask, constraints, return address) → Claude Code or Codex works it on the local machine → the result returns and unpacks into the Project as a recorded artifact with provenance. Design what the Field shows while an agent works elsewhere (the in-flight state as something visible in the space), failure and retry, and the moment of acceptance — flag if acceptance deserves the gold ceremony, and argue it.

## Deliverable 5 — Collaboration through the server

Two trusted members in one Project: presence in the same Scene, handoffs, sending files, syncing state, working on each other's computers — all mediated by the server, inside grants, everything traced. The trust boundary honestly rendered: what a trusted relationship unlocks that an untrusted one doesn't; registered vs unregistered resources inside a shared Project (the four-quadrant matrix, no fear language). One moment of the Sentinel's *effect* — a pacing nudge in a hot working session; no meters, ever.

## Deliverable 6 — The cut

Mark every screen **in** or **out** for the first shippable Studio. The test: Moto and one trusted collaborator run one real Project (the Lightbrush integration) end to end — upload, connect, hand off to Claude Code, get work back, record it, and see all of it in the Field.

## Law (violations are bugs)

**The Field is the only interface; chat lives in the contextual HUD** (never a separate Chat surface). Everything the member needs is represented in the Field. Compute is "prepaid usage credits that power intelligent agents" — never investment/ROI/passive-income language; no earnings claims. Members never users · handle never username · relationship never connection · registered/unregistered for resources, trusted/untrusted for relationships · the Field and Scenes (never "Reality") · Moves are authored experiences · ACTIONS appear in the Field when action is required · Allies and Actors are the only agent types; Builders/Creators may name Actor kinds · the Source owns the Ally; instruction only from the Source · gold marks signed acts only; light announces what happens to you · press-and-hold is the signature · never render HEARTS, meters, scores, or leaderboards · receipts are machine-generated sentences over exact commands · all money authorization on the web · examples only from real dunas and real people (Moto, Elias, Moe/Lightbrush, the cohort).

## Output format

One folder `design-r7/` in a zip: `MANIFEST.md` · `UX-SPEC-R7.md` (the Field grammar first, then Studio's jobs inside it) · `.dc.html` canvases (desktop 1440 primary; one mobile 390×844 canvas showing the same Field grammar compressed — decide what of Studio exists on the phone and flag it) · `MOTION-ADDENDUM-R7.md` (HUD opacity transitions, ACTION appearance, in-flight handoff states) · `OPEN-QUESTIONS-R7.md` — your sharpest disagreements, one per item, alternatives with reasons. Where you disagree with canon, build what canon says *and* flag it; where canon is silent, decide and flag.
