Design Round 6 · Deliverable 1 · The first invitation, end to end · renders spec v5.2 · July 10, 2026

Moto prepares the system for swyx, one person, invited well

The founding act of Creating from Within, every beat designed: Moto meets Ki and makes his ally out of it (1a) · his ally triggers the Profiler and takes the intake conversationally (1b) · the profile card comes back correctable, and sending is the flow's one gold moment (1c) · the invitation as swyx sees it, pre-account (1d) · swyx enters through the R5 onboarding and lands in a first Chat that starts in the middle (1e) · he flips the mode and the same conversation renders as a place (1f) · and the two of them reach Studio, cut to exactly three jobs plus one package handoff (1g). Live's full grammar is canvas 02; the mode products are canvas 03; the /handle pages are canvas 04. Every screen carries its IN · AUG 10 or OUT mark for the cut.

A fresh ecosystem has exactly one inhabitant: Ki, the Genesis Ally. Ki greets, explains just enough — never a tour — and its first real job is to help Moto personalize an ally of his own out of Ki. Ally creation is a conversation, not a settings form: the name, the handle (checked live, unique across members and allies), the Contract's first sentences, and a plain statement of what the new ally already knows about its Source. Nothing here is signed — an ally is stated trust, revocable by a sentence.

Moto tells Taro he wants to invite Shawn "swyx" Wang. Taro checks he isn't already a member, then triggers the Profiler — the first Program — and walks the input list as conversation: the handles that matter, one defining work, the relationship in a sentence, the why, the landing container, the proposed starting grants. The member is not filling a form about a stranger; he is preparing the system for a particular person.

The Profiler returns one card in the thread. Front: what the system now knows and at what access level. Back: the sources it used, each a citation. Moto can correct anything by saying so; nothing sends until he signs. Extending a code is a sovereign act — one of the three signed acts at launch — so sending the invitation takes press-and-hold, and the gold ceremony marks it.

The code travels as a link in a DM. Pre-account, the page is the R5 invitation grammar extended by one thing the Profiler makes possible: it reads like it was written by someone who knows his work, because it was — Moto's two lines verbatim, plus one honest sentence about what was prepared. What the registry proves and what a person wrote are typographically distinct and never blended.

11:47kidunaverse.com/k/9R4T-SW

a Kinship Code · unique to you · checked against the registry just now

Moto invited you, Shawn.

what this code proves

Issued by Moto — member of Kinship Duna, a registered organization: WV Org 628407, West Virginia Secretary of State. Admits one person — you — to membership, with a seat in the Kiduna Club cohort. Lapses July 24. It cannot move money and shares nothing about you.

from Moto · his words

"We've traded notes on agentic systems since 2024; you named the era we're building for. I want the first outside eyes on the Kidunaverse to be the person who'd call it honestly — and I think you'd build in it."

Before this link was sent, Moto prepared the system for you: it has read the AI Engineer essay and your public writing, holds what it learned where only you, Moto, and your future ally can see it — and shows you all of it, correctable, the moment you enter.

Enter — about five minutes →

no account yet · nothing sent to Moto until you choose · what was prepared?

R5's proof grammar + the Profiler's two additions: Moto's verbatim lines, and the preparation disclosed pre-account

Three registers on one page, never blended: registry claims in plain type with checks · Moto's voice in italic behind a rule · the system's disclosure of its own preparation in the system's voice.

The preparation is disclosed before the account exists. A system that studied you and said nothing would be surveillance with good manners. The sentence states what was read, where it's held, and that he can correct it — the "what was prepared?" link expands the full source list from 1c, pre-account.

Unique to a person, rendered personally. "Moto invited you, Shawn" — the page addresses him because the code admits only him. If the link is opened by someone else, nothing breaks and nothing personal shows beyond his first name; the code simply won't join anyone else.

Still no selling. No product tour, no cohort name-dropping, no urgency. What the Kidunaverse is gets answered by Ki, inside.

Onboarding is R5's designed flow, adopted whole — account · wallet · ally naming, one act per page, then the $100 step with exactly three options (R5 canvas 01, 1b–1e). R6 adds what the Profiler changes: Ki greets him by his work, his ally (he names it Latent) wakes already fluent, the first Chat starts in the middle of a real conversation — and the relationship card with Moto is designed conversationally, both sides stated.

The mode switch lives at the top of the app, always: two words, Chat · Live. Flipping it is a designed moment — the thread sinks, the Club rises around the same sentence (crossing grammar, 1400ms), and the last exchange stays readable in the ally band. swyx arrives as himself: Latent beside him, Taro visible across the room in an exchange he can walk toward and watch, and one contextual action surfacing by proximity. Full Live grammar: canvas 02.

No Studio redesign this round — R5's posture stands (one conversation over a live workspace). The create-from-within cut offers exactly three jobs: maintain your ally · invite someone · develop a Move — and one demonstrated handoff: Studio hands Claude Code a self-describing package, the result returns, and unpacks into the graph, recorded like any work. Everything else Studio will be is absent, not hidden.