# UX SPEC — DESIGN ROUND 6
**Kidunaverse · renders Spec v5.2 (July 10) · R2–R5 remain in force except as amended here · July 10, 2026**
Pairs with: `01 First Invitation R6.dc.html` · `02 Live R6.dc.html` · `03 One and Live Products R6.dc.html` · `04 Kidunaverse Directory R6.dc.html` · `05 Create-from-Within Cut R6.dc.html` · `MOTION-ADDENDUM-R6.md` · `OPEN-QUESTIONS-R6.md`.

---

## 0. The sentence, composed

R3's sentence still governs: **one dialogue with your ally, and everything else is a card that gets bigger for a minute.** R6 adds the round's own sentence on top: **the member prepares the system for the person they're inviting.** Everything new this round — Ki's first session, the Profiler, the personal invitation page, the fluent first Chat, the mode products, the /handle pages — is that one sentence rendered at different points of the arc. Nothing in R6 adds a second paradigm; Live is Chat's second rendering, and the mode products are subtractions, not siblings.

## 1. Renames and canon absorbed from v5.2

- **Chat and Live** are the modes; "Move" as a mode name is retired everywhere. R5's canvas 02 ("Move") is superseded in name and extended in substance by R6 canvas 02; its grammar survives intact.
- **Moves** are the authored Live experiences (scenes, vibes, games) built in Studio; Kidunaversity is the first. The sim flag is orthogonal to Move-ness: real Moves take solid borders and real gold; only sim-flagged Moves take mint-dash-hollow.
- **Six surfaces**: Kiduna (kiduna.app) · Kiduna Live (kiduna.live) · Kiduna One (kiduna.one) · Kiduna Studio (desktop + kiduna.studio) · Kiduna Express (kiduna.express) · Kidunaverse (kidunaverse.com with /handle directories).
- **Source** is the word for an ally's owner; **every ally is Ki personalized**; conversations between people run Source 1 → Ally 1 → Ally 2 → Source 2; every invitation code is unique to one person.

## 2. The first invitation (Deliverable 1) — the design decisions

**Beat 1 — Ki's first session (01 · 1a).** Ki explains just enough: three sentences of world, then the first act. Ally creation is conversation — the naming, the live handle check (one namespace across members and allies), the Contract's three first sentences, and a provenance statement of what the new ally knows about its Source. The takeover is continuity, not construction: Taro inherits the thread and the memory because it *is* the same system with a new face. No gold anywhere — an ally is stated trust.

**Beat 2 — the Profiler intake (01 · 1b).** "I want to invite X" triggers the check-then-offer pattern (already a member? connect; new? Profiler). The input list is asked item by item, each with its reason stated ("so I read the right material, not everything"). The assembled list is restated whole before anything is read: **consent precedes collection.** The relationship sentence and the why remain member-authored verbatim forever — they are the two lines the invitee will read as the member's own voice.

**Beat 3 — the profile card (01 · 1c).** Front = what the system now knows and at what access level (who-will-ever-see-this is a consequence, so it lives on the front). Back = every source used, as citations; removal is forgetting, not hiding. Correction is conversational. **Sending is the flow's one gold moment**: extending a code is a signed act (with join and domain binding, the third of three at launch), so it takes press-and-hold and receives the ceremony.

**Beat 4 — the invitation as swyx sees it (01 · 1d).** The R5 proof grammar extended by exactly two things the Profiler makes possible: the issuer's two lines verbatim (italic, behind a rule — a person's voice, typographically distinct from registry claims), and **the preparation disclosed pre-account** (what was read, where it's held, that it's correctable). A system that studied someone and said nothing would be surveillance with manners; the disclosure is therefore not optional copy — it is the page's second job.

**Beat 5 — swyx enters (01 · 1e).** Onboarding is R5's flow adopted without redesign. The ally (Latent) wakes fluent and **opens with provenance** — the disclosure is the first message, the conversation the second. The first Chat starts in the middle: a sentence only someone who read the defining work could open with. The relationship card is R5's two-sided grammar, each side authored by its own member, no signature.

**Beat 6 — the switch and the creating (01 · 1f–1g).** The Chat ⇄ Live switch is chrome — two standing words — because a mode must feel cheaper than a door. Continuity is carried by the ally band across the 1400ms crossing. Studio ships as the create-from-within cut: **exactly three jobs (maintain your ally · invite someone · develop a Move)** and one demonstrated package handoff to Claude Code (context + ask + constraints out; records back, cited to the package). Everything else Studio will be is absent, not hidden.

## 3. Live (Deliverable 2) — the composed model

1. **Sky rims, never sky paint** (law since R5): the world is warm; the interface appears only as a thin breathing edge on what would respond to touch.
2. **The HUD is four elements** — container chip, contextual chips (≤3, ranked by distance then consequence), the ally band, sky rims. No fifth element; fuller UIs are Chat's slide-over cards, borrowed and returned.
3. **Steering is three gestures** — tap to walk, drag to look, pinch to rise.
4. **Access renders as geometry.** At range an exchange shows its public shape; within grants, proximity opens what both sides allow; what you cannot access never gets a chip — absence, not a locked door. Chips that depend on grants state their permission in their own label ("listen in — both sides allow it").
5. **Moves score in sentences.** Goals strike through; outcomes are told once, as story, in the debrief. Practice currency is named in-fiction (Foundry Scrip) before its wallet renders; sim ground is mint-cast and dashed; practice press-and-hold is hollow gold, no embers, no haptic. Numbers may exist inside the fiction; they never rank people.
6. **The vocabulary is a closed set** (02 · 2e): five tile classes, five sprite classes, five event classes. Growing the set is a Studio design act — versioned, named, everywhere at once — never per-scene improvisation.
7. **The generative fallback is a designed material.** Sentence first; nothing draws that the sentence didn't state; the "drawn live" chip never leaves; sprites and HUD identical to authored space. At launch the fallback is most of the world, on purpose.
8. **kiduna.live arrives on your own ground** — no lobby, no world-picker. The graph knows where your life here is.

## 4. The mode products (Deliverable 3)

1. **One door grammar for both**: a sentence about the mode · Sign in · "I have an invitation code" · a pointer to kidunaverse.com for the curious-uninvited. If the doors diverge beyond the sentence, the products have started competing.
2. **kiduna.one holds subtraction**: no mode switch in the chrome, no ground ever renders. Portals arrive as words; accepting is a stated handoff. Sovereign acts are undiminished — cards, press-and-hold, gold are Chat grammar and therefore One's.
3. **kiduna.live is 02 · 2a as a product**; the band expands to a slide-over thread for long-form moments; full threaded history is reserved for One and the app.
4. **The switch to the whole is a standing line, not a nag**: "the whole Kidunaverse · kiduna.app," bottom of the surface, never modal, never counting. Conversation and position travel on tap.

## 5. kidunaverse.com (Deliverable 4)

1. **Onboarding and registration: R5's flow, adopted.** No pixel changed this round; Ki's greeting on the first page may carry one line of the profile's warmth.
2. **/handle pages render at the viewer's level**: stranger (registry proof + one self-authored line + boundary sentence), relationship (the two-sided card is the page's center), shared container (texture of what they do there, citable). **Never balances, counts, or standing at any level.**
3. **Member pages and ally pages are different species**: a member's page centers a relationship; an ally's page centers its Contract — Source (linked), binding sentences, reachability. Ki's page (kidunaverse.com/ki) is the one ally page that offers conversation to strangers.
4. **Boundaries are the three sentences** (04 · 4c), verbatim across all pages: held closer · you see the ones you share · none of this page's business. No padlocks, no teasers, zero motion on closed things.
5. The protocol browser and public metrics defer (R5 canvas 04 stands as their design when they come).

## 6. The invariants, restated

Citations and consequence-ordering · gold = signature (three signed acts at launch: join, code extension, domain binding — the third deferred with Express) · sky = touchable · the card anatomy (front consequence, back context) · the four access levels · the Contract · one ally voice · drift, never navigation · members never users · handle never username · relationship never connection · registered/unregistered · Compute is prepaid usage credits that power intelligent agents · deciding is never fundraising · the Sentinel visible only as effects and plain sentences · receipts show machine-generated sentences over commands · press-and-hold everywhere, practice version only inside Kidunaversity · light announces what happens to you; never pulses for attention.

## 7. The cut

Canvas 05 is normative: fifteen screen-groups in, nine capabilities out, and the one-page slice whose test is recursion — Moto invites swyx before lunch; swyx invites the next person the same day; Ki greets that person better because swyx's corrections are in the graph now.