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.

1a

## Moto meets Ki — the very first session on a fresh ecosystem

IN · AUG 10

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.

9:02 Friday
Ki · the Genesis Ally · Kinship Duna
Good morning. I'm Ki — the ally this ecosystem was born with. Right now the Kidunaverse is you, me, and a registered organization in West Virginia. Everything else gets created from inside.
Two things are worth knowing before anything else: you talk, I act — there are no menus to learn. And the first thing to make is your own ally: me, personalized to you. Want to start there?
Yes. What do you already know about me?
Exactly what the founding record states, nothing more: you are Moto, the founder of Kinship Duna, its first member, and the Source of the ally we're about to make. Anything else, you'll teach it — and it will say so when it's guessing.
make my ally what can you do? what is a Source?
Ki explains just enough — three sentences of world, then the first act · chips are one-tap sayables, and saying them does the same
9:11 Friday
Ki · making your ally
Call it Taro.
Taro. The handle @taro is free — handles are one namespace for members and allies, so no one else will ever hold it. Yours is @moto, from the founding record.
Taro's Contract · first sentences · yours to change anytime
Taro works for Moto and answers only to him. It may speak with anyone, spend nothing without him, and share only what a grant states. When it is unsure whether something is his to share, it isn't.
what Taro knows today: the founding record, this conversation, and whatever you teach it — each with its source kept.
Say the word and Taro takes over this conversation — same thread, same memory. I stay Ki, and I'll greet everyone you invite.
wake Taro edit the Contract
the naming, the handle check, and the Contract's first sentences — all in the thread · no gold: nothing here is signed
Every ally is Ki personalized — so ally creation is not construction, it's introduction. The design renders that: Taro doesn't "boot up," it takes over the same thread with the same memory.

Why the Contract is three sentences. The Contract will grow for the rest of Moto's membership; its first form has to be readable at a glance and true forever. Each sentence maps to a hard boundary the graph service enforces on every tool call — the card's back (tap) shows the mapping.

The handle is the one field-like moment, and it still isn't a field: Ki checks the namespace live and answers in a sentence. Uniqueness across members and allies is canon — kidunaverse.com/taro will be a page (canvas 04).

What Taro knows about its Source is stated with provenance from minute one — "each with its source kept" is the same citation grammar every later claim uses.

1b

## Preparing the system for swyx — the Profiler's conversational intake

IN · AUG 10

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.

2:26 Tuesday
Taro · Kinship Duna
I want to invite Shawn Wang — swyx.
He isn't a member anywhere I can see, so this is a true invitation. I'll start the Profiler — it reads only what you point it at, and holds what it learns at the level you set. Which handles matter?
X and GitHub are @swyx, Bluesky is @swyx.io, LinkedIn under his full name — and latent.space is his.
Got them. One or two works that define him — so I read the right material, not everything?
"The Rise of the AI Engineer" — June 2023. And Latent Space generally.
And the parts only you can give me: how you know him, in a sentence — and what you hope to build together. That second one becomes the invitation's substance.
land him in Kiduna Club propose starting grants
the input list as a conversation — each item asked for by its reason ("so I read the right material, not everything")
the working input list · refined by use
who Shawn "swyx" Wang · X/GitHub @swyx · Bluesky @swyx.io · LinkedIn · latent.space
the work"The Rise of the AI Engineer" (Latent Space, June 2023) · the Latent Space corpus
the relationship"We've traded notes on agentic systems since 2024; he named the era we're building for."
the why"I want the first outside eyes on the Kidunaverse to be the person who'd call it honestly — and I think he'd build in it."
the where Kiduna Club, with the launch cohort
the grants Moto proposes to share: the Kidunaverse spec and its history · his open calendar slots. Asks nothing of swyx up front.
Every line above is quotable back and editable by saying so. Nothing is read until Moto has seen this list whole.
the assembled list, restated once before the Profiler reads anything — consent precedes collection
The Profiler is the signup funnel inverted: instead of interrogating the newcomer, the system studies for their arrival — and shows its homework before anything sends.

Contextual action, not workflow. "I want to invite X" is a sentence, and the check-then-offer pattern (already a member? connect · in the alliance? invite there · new? Profiler) is Orchestration §6 verbatim. There is no Invite screen anywhere in the app.

The relationship and the why are member-authored and stay member-authored: the Profiler never paraphrases them, because they are the two lines swyx will read as Moto's own voice (1d).

Grants are proposed, not set. What Moto offers is stated up front and takes effect only when swyx accepts the relationship (1e) — stated trust, no signature, revocable by a sentence.

1c

## The profile card — correctable front and back, then the one gold moment

IN · AUG 10

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.

profile · Shawn "swyx" Wang front · what it knows
Writer and engineer; named the AI-engineer era in "The Rise of the AI Engineer" (June 2023); runs Latent Space. Works in public; his positions on agents are well documented and recent.
Your sentence about the relationship and your why are attached in your words, marked as yours.
held at relationship level — visible to you, to Ki for his onboarding, and to his own ally when it wakes. Never to the Club, never public. He sees all of it the moment he enters, and can correct it.
correct something flip · sources
front = consequence: what is now known, at what level, who will ever see it
profile · Shawn "swyx" Wang back · sources used
◆latent.space — "The Rise of the AI Engineer," Jun 2023 · read whole
◆latent.space — 14 further essays, 2024–2026 · titles and openings
◆X @swyx — public posts, last 12 months · sampled
◆Bluesky @swyx.io · GitHub @swyx — public profiles · read
◆LinkedIn — public page only · not logged in, nothing private
◆Moto — the relationship sentence and the why · your words, unedited
Nothing was read that isn't listed. Anything removed here is forgotten, not hidden.
back = context: every source a citation, subtraction honored as forgetting
sovereign act · extend a Kinship Code
One code, unique to Shawn "swyx" Wang, admitting one person to Kinship Duna with a seat in Kiduna Club. It travels as a link, lapses in fourteen days, and can be withdrawn by a sentence. Your name and your two lines travel with it.
hold to sign · extending…
press-and-hold · the signature everywhere · stamp + embers + haptic on commit
the flow's one gold moment — gold marks the signed act, never the arrival of the card
"Correctable before anything sends" is the Profiler's whole ethic: the system may study a person, but the member answers for what it holds — so the member sees it first, whole, with its sources.

The access level is on the front, not in settings: who-will-ever-see-this is the card's consequence, and consequence belongs on fronts (R3 card anatomy, unchanged).

Why gold here and nowhere else in the flow: naming Taro, running the Profiler, even composing the invitation are all revocable. Extending a code binds Moto's name to an admission — that is a signed act, and the only one until swyx's own join.

1d

## The invitation as swyx sees it — proof first, then a voice he recognizes

IN · AUG 10

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:47 kidunaverse.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.

1e

## swyx enters — onboarded by Ki, met by an ally already fluent in his work

IN · AUG 10

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.

12:20 Tuesday
Latent · your ally · Kiduna Club
I should say what I already know and where it came from: Moto pointed me at the AI Engineer essay and your public writing — the full list is a tap away, and anything you strike, I forget. Everything else about you starts now, from you.
So — the question you asked in 2023 is the one this place answers oddly: here the API surface is a relationship. Your ally is the only interface, and everything I do for you is on a record you can walk. Moto's around, and he's proposed to share the spec and his open slots with you. Want to see his side of it?
Show me. And what do I share back?
see everything you hold on me the relationship card
the first Chat starts in the middle — provenance first, then a sentence only someone who read the essay could open with
relationship · Moto ⇄ swyx both sides stated
Moto shares "The Kidunaverse spec and its whole history, and my open calendar slots — Latent can book them through Taro."
swyx shares "My reading of the spec as I go — notes included. Nothing from my drafts folder unless I say the piece by name."
Each side is written by its own member and editable only by them. No signature — stated trust, revocable by a sentence. Allies enforce the boundary on every exchange.
the two-sided relationship card (R5 grammar) — designed conversationally, in each member's own words
Fluency must open with provenance. An ally that greeted swyx with facts about himself and no sources would demonstrate exactly the future he'd warn people about — so the first message is the disclosure, and the second is the conversation.

Onboarding is not redesigned. The R5 pages run verbatim — passkey account, wallet as a fact, naming the ally, the three-path $100 step, gold only at the join. The only R6 change: Ki's greeting on the first page carries one line of the profile's warmth ("the essay was a good brief").

Latent is swyx's, entirely. Same Genesis Ally underneath, personalized by a different Source; Moto cannot command it, and the profile it woke with is now swyx's to keep, correct, or erase.

1f

## The first switch to Live — same conversation, second rendering

IN · AUG 10

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.

12:34 Chat Live
Moto's in the Club's space now — Taro with him. I can take you there; the room renders what I've been telling you.
Go.
the thread sinks · the space rises · 1400ms · tap anywhere to turn back
mid-crossing — the switch is in the chrome, not in a menu: two words, always present, both ways
you · with Latent
Taro · with Moto in an exchange · walk closer to see its shape
Kiduna Club · the Commons Chat Live
join Moto at the table
Taro is telling me which parts of the spec you've already argued with in print.
arrival — both allies visible, the ally↔ally exchange watchable by walking, one proximity action offered (sky, plain tap)
The switch is not a portal. Portals go somewhere; the switch changes how the same somewhere renders. That is why it lives in the chrome as two standing words — a mode has to feel cheaper than a door.

Continuity is carried by the ally band — the last Chat sentence rides through the crossing and keeps narrating on arrival. One conversation, two renderings, zero re-establishment cost either way.

Watching is governed by distance. The exchange between Taro and Latent surfaces only its public shape at range; walking closer within the relationship's grants reveals what both sides allow — access levels as geometry (02 · 2c).

1g

## Into creating — Studio cut to three jobs, plus one package handoff

IN · AUG 10 — the cut only

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.

Kiduna Studio · create-from-within cut container · the Moto ⇄ swyx relationship
workspace · the graph, this container's scope
Move draft · "Spec Walk"
a walkable tour of the Kidunaverse spec — swyx's idea, day one
the spec · shared by Moto
11 tracks · grant: read + annotate
package · out with Claude Code
"tile the spec's rooms" · context + ask + constraints · self-describing
package returned · unpacking into the graph
Claude Code returned 14 tile specs and a room layout for "Spec Walk." Each lands as a record in this relationship's scope, cited to the package. Nothing executed; nothing spent.
walk it in Live see the package
dropped material organizes itself · ambiguities become questions in the chat, never dialogs (R5 §4, unchanged)
the conversation · Taro, for Moto
Studio can do three things right now: maintain Taro, invite someone, and develop a Move. Everything else arrives when someone inside needs it and makes it.
Hand the tiling work to Claude Code — swyx's layout notes go with it.
Packaged: the room list, both your notes, the tile grammar, and the constraint that nothing draws what a sentence doesn't state. It's out. I'll tell you when it returns.
maintain your ally invite someone develop a Move
desktop 1440 (shown scaled) · the three jobs are the only standing chips · the package is gold-bordered only while it represents work signed out under Moto's name
The cut is the message: a Studio that can only maintain, invite, and make Moves says "everything else gets created from within" more credibly than any roadmap page could.

The handoff is honest about what Studio isn't. Studio doesn't code; the package protocol (context · ask · constraints out; records back, cited to the package) is demonstrated once here and is the same pattern Kinship runs on itself.

Recursion closes here: swyx, one hour in, can run 1b himself — his ally knows the Profiler because every ally is Ki. The invited can invite; that's the test of the cut (canvas 05).