# Design Round 6 — Creating from Within: Chat and Live, and the First Invitation
**The prompt Moto runs in Claude Design · 2026-07-10 · spec v5.2**

---

You are designing Round 6 for the Kidunaverse — the agentic internet built by Kinship Duna, shipping open source (Apache 2.0) on **August 10**. Round 5 delivered the cohort journey. Round 6 designs the surfaces for **Creating from Within** (`create-from-within.md` in the kit — read it first): the minimum necessary to start creating with the system, centered on one act done perfectly — **Moto sets up his ally and invites swyx** — and on the first real design of **Live**.

**Canon since R5 (binding):** the two modes are **Chat and Live** ("Move" as a mode name is retired; **Moves** now means the authored Live experiences — scenes, vibes, games — built in Studio; Kidunaversity is the first). Six surfaces: **Kiduna** (the app, first KAP client, kiduna.app) · **Kiduna Live** (kiduna.live — Live alone) · **Kiduna One** (kiduna.one — Chat alone) · **Kiduna Studio** (desktop + kiduna.studio) · **Kiduna Express** (kiduna.express) · **Kidunaverse** (kidunaverse.com, with **/handle** directory pages; "handle," never "username"). The owner of an ally is its **Source**; every ally is really the Genesis Ally — **Ki** — personalized; conversations between people always run Source 1 → Ally 1 → Ally 2 → Source 2. Every invitation code is unique to one person.

## Inputs (in the attached zip)

The **Kiduna Kit v1** — the complete v5.2 spec. Read `create-from-within.md`, then `surfaces.md`, `orchestration.md` (§1 Ki and Sources; §5 the Profiler), `roles.md` §1, `legal.md` (binding copy rules), `sentinel.md` (never render meters). Design rounds r2–r5 are inside and in force where not superseded — R5's cohort-journey canvas (design-r5/) is the onboarding baseline; extend it, don't redo it. `_ds/…/colors_and_type.css` is binding for every pixel; carry `_ds` in your output. The old Studio prototype (`studio-prototype/app.html`, if attached) remains the anti-pattern.

## Deliverable 1 — The first invitation, end to end (the through-line)

Design every beat of the founding act:

1. **Moto meets Ki and makes his ally.** The very first session on a fresh ecosystem: Ki (the Genesis Ally) greets, explains just enough, and helps Moto personalize his own ally out of Ki — the naming, the **handle** (unique across members and allies), the Contract's first sentences, what it already knows about its Source. This is ally *creation as conversation*, not a settings form.
2. **Preparing the system for swyx.** Moto tells his ally he wants to invite Shawn "swyx" Wang; the ally triggers the **Profiler**. Design the conversational intake of the input list — handles (X, LinkedIn, Bluesky, GitHub, latent.space), one defining work (["The Rise of the AI Engineer"](https://www.latent.space/p/ai-engineer), June 2023), the relationship in a sentence, the why, the landing container (Kiduna Club), the proposed starting grants — and the **profile card** the Profiler returns: front stating what the system now knows and at what access level, back showing sources used. Correctable before anything sends.
3. **The invitation as swyx sees it.** A unique, personal code traveling as a link — pre-account, it renders what it proves (who invited him, into what, registered to which legal entity) and reads like it was written by someone who knows his work, because it was.
4. **swyx enters.** Ki onboards him (the R5 onboarding flow is the baseline — reuse it); his ally is created *already fluent in his work*; the first Chat starts in the middle of a real conversation, not at zero; the relationship card with Moto is designed conversationally, both sides stated.
5. **First switch to Live.** swyx flips the mode: Kiduna Club as a place, Moto's ally and his own visible, an ally↔ally exchange watchable, one contextual action offered by proximity. The switch itself — Chat ⇄ Live, always available — is a designed moment: same conversation, second rendering.
6. **Into creating.** Moto and swyx in **Studio (the create-from-within cut)**: exactly three jobs — maintain your ally, invite someone, develop a **Move** — plus one demonstrated **package handoff** to Claude Code (Studio hands out a self-describing package; the result returns and unpacks into the graph). No full Studio redesign this round; design the minimal, honest version of these three jobs.

## Deliverable 2 — Live, its first full round

Live is the isometric rendering of the same Kidunaverse — the member still only converses with their ally, but **steers**, and can watch ally↔ally and ally↔actor interactions happen. Design: the HUD and menus in `_ds` grammar (what "sky = touchable" means on an isometric ground); contextual actions by movement and proximity; goals and scoring inside sim-flagged Moves (practice currency named in-fiction; nothing inside affects the Kidunaverse); the tile/sprite/event vocabulary; **the generative fallback** — where finished art doesn't exist, the models render a bounded room ("four others here; the far two are talking") that is legible and honest next to authored art; portals from Chat; and **kiduna.live as a front door** — arriving in Live directly, with Chat one switch away. Gold marks signed acts only; light announces what happens to you; no meters, no leaderboards, ever.

## Deliverable 3 — Kiduna One and Kiduna Live as products

The two modes offered whole: kiduna.one (Chat as just chat) and kiduna.live (the Live environment only) — same app, same ally, same graph. Design each one's front door, first minute, and the ever-present switch to the full app. These are the simplest possible invitations to the system; treat them that way.

## Deliverable 4 — kidunaverse.com, the create-from-within cut

Only what the first invitation needs: onboarding/registration (R5's designed flow, adopted), and the **/handle directory pages** — what a member's page and an ally's page each show at each access level, to a stranger, to a relationship, to a fellow member of a shared container. The protocol browser and full metrics defer to a later round.

## Deliverable 5 — the Create-from-Within cut

Mark every screen **in** or **out** for August 10, and close with one page: the minimum coherent slice, across Chat and Live, that lets Moto invite swyx — and lets swyx invite the next person the same day. The test of the cut is recursion: the invited can immediately invite, and the system that greeted them can greet the next person better because they're in it now.

## Law (violations are bugs, not opinions)

Vocabulary: Compute (never "compute currencies") · Forums (never markets) · **Chat and Live** (never "Reality," never "Move" as the mode) · **Moves** = authored Live experiences · relationship between two people (never "connection") · registered / unregistered (never "trusted"/"accountable" as artifact verdicts) · members never users · **handle** never username · **Source** for an ally's owner · Ki is the Genesis Ally. Money copy is legally binding: Compute is **"prepaid usage credits that power intelligent agents"**; never investment/appreciation/ROI/passive income/early-investor/financial-upside language; Founder is recognition only; no earnings claims anywhere. The gold ceremony (stamp, embers, haptic) marks signed acts and nothing else, forever; what happens *to* you is announced by light; press-and-hold is the signature everywhere (practice version only inside Kidunaversity). Never render HEARTS, meters, scores, balances-as-standing, or leaderboards. Receipts show machine-generated sentences over commands. Examples only from the real dunas, the real cohort, and swyx. All money authorization on the web. Deciding is never fundraising.

## Output format

A single folder `design-r6/` in a zip: `MANIFEST.md` · `UX-SPEC-R6.md` (the composed model: the invitation arc, Live, the mode products, the /handle pages, the cut) · `.dc.html` canvases (mobile 390×844 for Kiduna/One/Live; desktop 1440 for Studio and kidunaverse.com; use `_ds` and carry it) · `MOTION-ADDENDUM-R6.md` (especially the Chat ⇄ Live switch and Live's movement grammar) · `OPEN-QUESTIONS-R6.md` — your sharpest disagreements, one per item, alternatives with reasons. Where you disagree with v5.2, build what the spec says *and* state the disagreement; where the spec is silent, decide and flag.
