# Design Round 8 — The Field, on Four Surfaces
**The prompt Moto runs in Claude Design · 2026-07-13 · read `skill-updates/cofounder-canon-2026-07-13.md` AND `cofounder-canon-2026-07-11.md` FIRST — they supersede older track text**

---

You are designing Round 8: **the Kiduna client — the Field — across its four surfaces.** The Field is the UI/UX convention for the Kinship Agency Protocol the way the browser is to the web: always live, always connected, because the agentic internet never stops changing state. People will build other apps and games on KAP; the Field is the canonical interface, and this round defines it.

**Canon (binding):** A **Scene** is a complete, attached realm inside the Field; moving between Scenes requires a **Portal in each Scene** (edge or interior). The contextual HUD carries chat and can go opaque for focus. ACTIONS appear where you are when something needs you. **The major nodes each need a canonical Field representation:** Member · Relationship (a first-class dyadic node, per-Organization — the same two people relate differently in different Organizations) · **Community** (3+ members — replaces "Guild") · Alliance (formalized Community: multi-sig wallet, proposals/policies) · Institution (KYB'd non-DUNA entity) · Project · **Organization** (the public word — never "duna" in member-facing copy; the legal container everything lives within) · Ecosystem (kap://eco.domain.net). **Five agent types:** Allies (exactly one per member; member → ally → ally → member; your ally filters all input per your preferences) · Actors (invoked by allies/organizations/alliances/projects for work) · Sentinels (keep both fields clean; escalate) · **Envoys** (formerly Electors — trade pass/fail tokens in Forums; vote and act for you in alliances and organizations under your instruction) · Operators (run the Forums). Every action any of them takes happens inside an Organization, as a member of it; anything not in a specific one is in Kinship Duna by default. Only a Source directs an ally.

## Inputs (attached zip: the Kiduna Kit)

Read the two canon deltas first, then `create-from-within.md`, `surfaces.md`, `architecture.md` (+ the Technical Specification and White Paper inside the kit), `kinship-graph-flow.html` (the graph workflow — note its vocabulary lags canon), design-r6 (the member journey cut — adopted) and design-r7 (Studio round + Moto's sixteen rulings appended to both rounds' OPEN-QUESTIONS files — those rulings are law). `_ds/…/colors_and_type.css` binds every pixel; carry `_ds`.

## Deliverable 1 — The Field grammar, canonical

Before any surface: the Field itself. Scenes and Portals (both ends, edge and interior); the contextual HUD and its opacity; ACTIONS appearing in place; how each major node above *looks and behaves* as a thing in the Field — a Member present, a Relationship you can stand inside, a Community versus an Alliance versus an Institution, a Project with its stable Scene identity (a materialized room is earned by scale — ruling 1), an Organization as the container everything sits within, an Ecosystem as the ground itself. The always-live quality: what it means that the Field is never a static page.

## Deliverable 2 — Studio (kiduna.studio · Windows/Mac/Chromebook/Linux · Flutter/Flame)

The building surface, same Field, more verbs: building organizations, alliances, and allies; adding content; modifying system prompts; connecting accounts. **Designed ground-up for collaboration:** real-time sharing with other builders in the same Scene; materials that organize themselves; GitHub links; **package transfer directly between client computers** and to network storage. Work through inspecting, interacting with, modifying, and enhancing **both Allies and Actors** — the inspection grammar is this round's hardest design problem; give it real screens. Honor R7's rulings (quarantined manifest violations; Docket as projection; two signatures; gold only into the authoritative Record).

## Deliverable 3 — Live (kiduna.live · iOS/Android)

The Field in the hand: the member's daily surface. The cohort journey (R6, adopted) rendered in the new grammar; participation and simple approvals (ruling 4 — complex diffs, grants, uploads, and acceptance stay in Studio); the switchless single interface with the HUD doing the work.

## Deliverable 4 — Express (kiduna.express · Chrome)

The Field meets the open web: browsing with registered/unregistered rendered honestly (a stranger, not a threat); everything you do through Express happening, by default, inside Kinship Duna; registering resources and domains with an Organization; your ally acting across pages under your authority.

## Deliverable 5 — TV (kiduna.tv · Android/Google TV)

The Field at ten feet: what CTV is *for* (presence, watching the world you belong to, Scenes as places a room of people can visit together), the remote-first input grammar, and what TV refuses to do (no signatures, no money — state it).

## Deliverable 6 — The cut

Every screen in/out for the first shippable client on each surface, closing with the cross-surface test: one member's day touching all four surfaces without the Field ever feeling like four products.

## Law (violations are bugs)

Community, never Guild · Organization, never "duna," in member-facing copy · five agent types by name (Envoys, not Electors) · member → ally → ally → member, always · only a Source directs an ally · registered/unregistered for resources, trusted/untrusted for relationships · Compute is "prepaid usage credits that power intelligent agents"; no investment/ROI/earnings language anywhere · members never users · handle never username · gold only into the Organization's authoritative Record; light for everything that happens to you · press-and-hold is the signature; practice version only in Kidunaversity · never render HEARTS, meters, scores, badges, or leaderboards · Practice Credits (never "scrip") · no identity-sameness claims without registered proof · all money authorization on the web (kiduna.cash is the wallet home) · examples only from the real Organizations and real people.

## Output format

One folder `design-r8/` in a zip: `MANIFEST.md` · `UX-SPEC-R8.md` (the Field grammar first, then the four surfaces) · `.dc.html` canvases (desktop 1440 for Studio; mobile 390×844 for Live; browser chrome for Express; 1920×1080 ten-foot for TV; use `_ds` and carry it) · `MOTION-ADDENDUM-R8.md` (Portals, HUD opacity, ACTIONS arriving, cross-surface continuity) · `OPEN-QUESTIONS-R8.md` — sharpest disagreements, one per item, alternatives with reasons. Build what canon says even where you disagree, and flag; where canon is silent, decide and flag.
