Kiduna Team · The Record

# How the spec got here

Every version preserved, every turn explained in one line. Newest first. Nothing here is shameful; it's how design actually happens when you write things down.

← Kiduna Team home
Design R7 · 2026-07-11 — current

## Kiduna Studio, whole — the Project gets its room

Round 7 is in, complete, rendered on the Lightbrush integration throughout: the Project as a first-class primitive (creation with its receipt, the anatomy card, and — decided and flagged — a Scene of its own at the on-the-fly grade); the desktop layout grammar with the HUD and its refusals (canvas 02 was drawn against the morning canon — read its chat panes as the contextual HUD's opaque state; the Field is the only interface); collaboration through the server (presence, handoffs, working on each other's machines, the four-quadrant trust matrix, one Sentinel effect); the coding-agent seam (package out → in-flight visible in the Field → return and unpack with provenance — and acceptance built as the fourth gold act, with the counter-argument stated); ally maintenance and Scene authoring; the cut (the slice test: one real Project end to end); and Studio on the phone as the pulse, not the workshop. Six open questions await Moto: a Scene per Project, gold for acceptance, the spacebar peek, mobile Studio, the server's one refusal, and where ACTIONS accumulate.

UX Spec R7 01 The Project 06 The Cut Open Questions
v5.4 canon · 2026-07-11

## The Field is the only interface

Evening canon (recorded in the 2026-07-11 delta, which wins over the tracks until the fold): there is no Field-and-Chat split — the Field is the only interface, with chat living inside a contextual HUD that can go opaque when the member wants to focus on an action or a conversation. Everything the end-user needs is represented in the Field — a box full of Bluesky posts is a box. Studio has the same UX as Live — the Field — running on your computer with access to your files, Claude Code, Codex, Google Docs, Meet, and whatever else you connect; it's where everything gets entered, uploaded, and defined. The two agent types refined: Allies represent, are guided by, and support members; Actors don't represent members and aren't controlled by them — they have functions, and Builders and Creators can name their own Actor types. The R7 Studio prompt rewritten around all of this (design-r7). Next up: the serious initial spec — what this is, how it works, how we build it out.

The canon delta R7 prompt (revised) Surfaces
v5.3 canon · 2026-07-11

## Getting serious: the Server, the Protocol, the Network — and the Field

The product lineup restated as canon (full record: the 2026-07-11 canon delta, which wins over the tracks until the fold lands): Kiduna Server (anyone installs one; foundation + orchestration + protocol inside; a mesh — you install to contribute, and can be paid for hosting a duna's resources; a server is an ecosystem, with a genesis account — Mage — and the genesis Ally; ecosystems spawn ecosystems by code from another genesis account); Kiduna Protocol (a single Solana program interoperating with MetaDAO and Token-22; the decentralized registry; DIDs bridging AT Protocol, Kiduna, and chain; extended MetaDAO voting; NFTs not required — a registry and clear relationships are); the Network (the protocol instantiated; it connects ecosystems); Kiduna Live (THE end-user app: mobile → CTV → MR/VR/XR; one surface — the Field, the entire range of play, with Chat overlaid in a flexible HUD; Scenes are its bounded environments, from crafted to generated to on-the-fly; ACTIONS appear in Field or Chat when action is required); Kiduna Studio (Field + Chat; Projects — a new primitive within Organizations — are its central organizing principle; Claude Code/Codex interop; trusted collaboration through the server); Kiduna Express. The trust matrix: relationships trusted/untrusted × resources registered/unregistered. Everyone with an account is always a member of the Genesis Duna. Visitor added below guest; Mama Ayo restored to Catalyst (Black Love); Institutions can carry KYB. Track-by-track fold + the full voice scrub queued next.

The canon delta Surfaces Protocol
Site reorg + Architecture · 2026-07-10

## A real website: top menu, footer, Architecture, and the front door rewritten

kiduna.team reorganized on the same model as kinship.systems, kiduna.club, and kinship.institute: a sticky top menu (How We Build · The Spec · Architecture · The Record · Get Involved · the Kit) and a full site footer (the six surfaces, the institutions, the project) on every page. New Architecture section distilling the Protocol + Stack Architecture v1.0 — six layers, the one rule (the graph service is the sole policy and command boundary; intelligence proposes, deterministic code authorizes), the command path, the identity chain, ecosystems and KAP, and what's still open. The home page rewritten as an invitation: join us in building the agentic internet — intelligence and agency, safely collaborating and coordinating — from the inside out, regardless of role. Voice scrub begun (home, method, architecture); the track-by-track pass continues.

The new front door Architecture Get Involved
Design R6 · 2026-07-10

## Creating from Within, designed — and the August 10 cut

Round 6 is in, complete: the first invitation end to end (Ki's first session with ally creation as conversation · the Profiler's conversational intake and correctable profile card · profile and code bound into one signature · the invitation as swyx sees it pre-account · swyx entering with an ally already fluent in his work · the first Chat ⇄ Live switch · Studio at exactly three jobs with one Claude Code package handoff); Live's first full round (the four-element HUD and sky-rim law, proximity actions, access as geometry, sim-flagged Moves with goals but no meters, the closed tile/sprite/event vocabulary, the generative fallback room); kiduna.one and kiduna.live as products, deliberately thin; the /handle directory pages at three access distances; and canvas 05 — the Create-from-Within cut, normative for the August 10 build, closing with the recursion test: the invited can immediately invite. Where R5's fuller designs differ from the cut, the cut ships and R5 is the horizon. The round returned ten open questions — pre-account disclosure depth, one signature or two, Ki's public conversational door and who funds it, Live voice at launch, and more — awaiting Moto.

UX Spec R6 01 First Invitation 02 Live 05 The Cut Open Questions
v5.2 · 2026-07-10

## Create from Within: Live & Moves, KAP & ecosystems, the Kiduna Kit

Create from Within is adopted as the method (its own page): build the minimum necessary to start creating with the system — not an MVP, not lean/agile — then create everything else from inside; the first target is Moto setting up his ally and inviting swyx, prepared by the Profiler, the first Program (every code unique to a person; the member prepares the system for who they're inviting). The isometric mode is Live (superseding "Move"); the authored experiences — scenes, vibes, games — are Moves, built in Studio; six surfaces now: Kiduna (the first KAP client) · Kiduna Live (kiduna.live) · Kiduna One (kiduna.one) · Kiduna Studio (+ kiduna.studio, with a package-passing protocol to Claude Code/Codex) · Kiduna Express · Kidunaverse (+ /handle directories; "handle," never "username"). The Kinship Agency Protocol (KAP) is formalized — Agency Servers and Clients; one server installation = an ecosystem; the Genesis Ecosystem is Kiduna and its purpose is to propagate; everything ships Apache 2.0 on August 10; KAP is stewarded by Kinship Agents DAO, LLC (new Institution, with Lightbrush LLC as the first integration partner — agreement drafted, L-16). The hierarchy gains its foundation: Ecosystem → Organization → Alliance → Guild → Ally → Member, with Institutions redefined as a special Alliance outside it; members are Sources; every ally is the Genesis Ally Ki, personalized. The site itself refocuses — how we build and how you can participate — and the download is now the Kiduna Kit, for anyone.

Create from Within Surfaces Protocol §1a Institutions
Design R5, first delivery + v5.1 · 2026-07-10

## The cohort journey, designed

Round 5's first deliverable is in: the cohort journey, cast with real people — Crystal Stone's whole arc from the invitation she sees before she has an account, through onboarding at kidunaverse.com (one act per page), the $100 step with all three paths honestly ranked (Stripe headless onramp · connect a Solana wallet · send USDC to the new address) with pending/complete states and the return to the flow, into first Chat where her ally introduces itself and the relationship with Moto is designed conversationally — the two-sided relationship card, front stating each side's sentence, back showing the context used — plus one-panel vignettes of the rest of the launch cohort. The canvas passed the canon sweep clean (the legal money vocabulary is used correctly throughout — "a balance, not a fee; never an investment"). Still to come from the round: Move, the Studio redesign, kidunaverse.com and the protocol browser, and the MVP cut. Package rebuilt as v5.1.

The Cohort Journey canvas Surfaces §8 The R5 prompt
v5.0 · 2026-07-09

## Eleven tracks: the Surfaces, Chat & Move, relationships, and the launch cohort

The Experience track rebuilt as The Surfaces — the four products with their official homes: Kiduna (the Flutter/Flame app, kiduna.app + the stores, with two areas: Chat and Move — Move supersedes "Reality"; sim experiences are Games, Kidunaversity first), Kiduna Express (the browser extension, kiduna.express — the web filtered through Kinship Codes; registered social accounts), Kidunaverse (kidunaverse.com — the account everything needs, the protocol browser over the audit trail, and the three-option USDC onboarding: Stripe headless onramp · connect a Solana wallet · direct transfer), and Kiduna Studio (the desktop building surface, redesigned agentic rather than segmented — where relationships are designed and allies hold back-channel conversations). Canon: between two people it is a relationship, never a "connection." Two new tracks: Institutions (KII · Kinship Systems · Kiduna Club, with their homes and functions) and Integrations (inward MCP/APIs/local agents; outward our own API and MCP server, no privileged path). The launch cohort seated: eight catalyst parties and four more luminary placements, all starting within Kiduna Club. Build status: pgvector replacing Pinecone is live; graph nodes landing; secret missing from the implemented visibility enum — flagged as not optional.

Surfaces Institutions Integrations Roles
v4.9 · 2026-07-09

## The Core Team Package becomes the complete archive

A packaging release — the spec content stands at v4.8. The daily download rebuilt as the real archive of the entire effort: all nine tracks (source and rendered), the narrative canon, the engineering architecture, every design round with its canvases, the concepts and prototype, the versions record, and both queues — everything a core team member needs without visiting the site. New is the multi-LLM harness: START-HERE.md routes by tool, CLAUDE.md orients Claude Code and Cowork, AGENTS.md orients Codex, LLM-INSTRUCTIONS.md is paste-able into Claude and ChatGPT Projects, and KIDUNAVERSE-COMPLETE.md carries the whole spec as one file for chat uploads. The home page now leads with a version banner naming the current package, its build time, and the download.

Core Team Package (current) The home page
v4.8 · 2026-07-09

## Track 9: Legal — counsel's seven resolutions in force

Counsel answered the whole brief in one pass, and the answers became a track. All seven questions resolved and adopted as rules in force, in priority order: securities (Compute is "prepaid usage credits that power intelligent agents" — the binding avoid/always vocabulary; Founder is recognition only), money transmission (no discretion, ever: instructions fixed before money arrives, no redirecting/holding/reversing — "workflow software, not a financial intermediary" is now a design test), organizer compensation (commissions only on consumed Compute; earnings claims prohibited without statistics), worker classification (1099 confirmed; the never-introduce list; W-9/1099 pipeline from day one), trust accounting (trust money is radioactive — IOLTA → release → treasury → splits), insurance (three phases, never "insurance" before licensure), and recusal (endorsed and generalized toward a full conflict-of-interest policy). Five new matters stubbed: ToS, Privacy, Kiduna Club IP licensing, KII fiscal sponsorship (Service Alliance, Mycelial Aid, BiHome first), and patent provisionals. The legal queue now lives on its own page — Legal Items for Review — separate from the product decision queue. The track is held for one end-to-end counsel review before launch.

Legal (Track 9) Legal Items for Review Open Questions
v4.7 · 2026-07-09

## Track 8: The Sentinel — eight tracks now

The last queue decision (members never see HEARTS — no acronym, meters, or scores; the member-facing word is vibe) grew into the Sentinel's first design pass, as its own track. The frame: seven signals on six axes, each running −100 to +100 with health at zero — every virtue fails in both directions, so the Sentinel is a regulator guiding toward the zero point, never a maximizer. Meters attach to fields (contexts), never to persons; readings decay and carry provenance; the human and agentic fields are measured separately and kept clean (attribution before measurement; no agent ever optimizes a meter; stated-scope withholding is health, not deception — settling the old Vigil-vs-Sentinel tension). Regulation runs in graduated bands from quiet observation through agent-side ambient correction and plain-sentence disclosure to a hard human-in-the-loop boundary, with always-human categories (crisis, minors, privilege, coercion) that skip the bands entirely. Build order is constitutional: measurement first, escalation second, autonomy last.

The Sentinel Orchestration Open Questions
v4.6 · 2026-07-09

## Organizer economics decided; membership clarified

The oldest deferred item closed with real numbers. Lineage commissions attach to exactly one event — a Clan member's Compute purchase (USD/USDC exchanged for a duna's Compute, including the initial purchase that makes a member) — never to enrollment itself, work, splits, or votes. The default schedule, every duna's starting point and Kinship Duna's at launch: Gen 1 20% · Gen 2 5% · Gen 3 3% · Gen 4 2%, Catalyst-set at founding, Forum-changeable, tracked four generations deep. Settlement: USDC purchases pay organizers immediately; fiat purchases show as pending (earned, not yet on-chain) until funds bridge, expected monthly. Lineage is optional per duna — open door, invite-only, or invite-then-open (a new variance axis). Also clarified: the $100 lifetime membership is Kinship Duna's initial Compute purchase; each duna sets its own.

Real Work, Real Money §3 Roles Organizations Foundation §6
v4.5 · 2026-07-09

## Registration: the registry, the claims, and the word

The last open question decided, beyond the proposal: the member-facing vocabulary is registered / unregistered — not "trusted," and not "accountable" either, because registration proves traceability and nothing stronger. Protocol §4 rewritten: the decentralized Kiduna registry publishes exactly four address kinds (member FROST wallet · ally NFT inside it · alliance Squads wallet · organization Squads wallet bound to its WV Org ID, mapping to the SoS); Kinship Codes carry those addresses as JWT claims, which is how the registry rides the regular internet — email, web, any app; and anything can register — a domain (DNS TXT), a page or content (embedded code), a photo or video (hash) — becoming traceable back to a member, ally, alliance, and organization. Unregistered stays "a stranger, not a threat."

Protocol §4 Actions Foundation Open Questions
v4.4 · 2026-07-08 late

## Five governance decisions; the Open Questions page

Decided: no holdings-based recognition, ever (balances never surfaced publicly or for recognition); structural Institution recusal (enrolled members cannot vote on their Institution's contracts, enforced at the vote command) with always-disclosed enrollment; the guild-to-alliance promotion offer. A standing Open Questions page now carries the decision queue, each item with full context and spec links; the promotion ceremony was then decided (light, not fireworks — gold marks signed acts only), and receipt sentences were ratified as machine-generated only (the graph service generates the plain sentence from the command's own parameters — a build requirement; never hand-written). One item remains open with a worked example ("accountable" domain wording).

Open Questions Roles Protocol Actions
v4.3 · 2026-07-08 night

## The coherence rework: a spec, not a changelog

Every track rewritten as a standalone, timeless specification a new team member can build from: meeting references, addendum blocks, and design-round bookkeeping removed from the bodies (each page now carries a one-line changes note at the foot; history lives here). The home page became the synthesis — what we're building, why it's built this way, and how one act flows through all seven tracks. Experience §7 consolidates the complete UI design. The daily download is now the Core Team Package (for Jeya, Aashik, Elias): the whole site, offline-viewable, self-orienting.

The new home Experience (with the full UI design) Core Team Package (current)
v4.2 + Design R4 · 2026-07-08 evening

## Chat & Reality named; Actions and Roles tracks; R4 installed

Seven tracks now. The surfaces get canonical names (Chat; Reality). The Actions track inventories the baseline actions across both surfaces; the Roles track defines the nine roles and names the first Catalysts (Matt Simon, Mama Ayo), Luminaries (Teich, Four Arrows, Smith, Thatcher, Narvaez), and Institutions (Kiduna Club, KII, Kinship Systems; Circle as potential partner) — superseding the wealth-threshold level definitions. Design R4 delivered: redraws, the cream web-money surface, Kidunaversity, promotion/guild/institution moments, "accountable" domains; its six open questions await Moto. Role packages replace the single team zip.

Actions Roles R4 UX Spec R4 Open Questions
v4.1 · 2026-07-08 09:30 ET

## Protocol and Organizations join; the graph becomes the center

Two new tracks: the Kinship Agency Protocol (minimal on-chain scope — FROST members, ally NFTs, Squads alliances, Org-ID-validated DUNAs, Compute, votes; MetaDAO generalized to duna commands; DNS TXT records for internet-scale accountability) and the Organizations (all 31 dunas, the variance analysis, the badge ladder, Kidunaversity as the first Reality Game). Foundation re-architected around the in-house graph + pgvector; Institution and Guild nodes added; Allies and Actors become the two agent families; "Compute" is canonical.

Protocol Organizations Foundation (updated) Kiduna-Architecture
Design R3 · July 7, afternoon — current design round

## The one dialogue, rendered

Spec v4's experience made concrete: voice that never takes the screen (the composer becomes the voice band; barge-in and mid-thought switching designed); the card → fuller-UI → return loop with a visible return seam; treasury, Forum, grant ladder, and record as sheets; portals and two training scenes; the money handoff to the web and back. Sixteen screens, a motion addendum, and six sharp disagreements with v4.

UX Spec Key Screens Motion Addendum Open Questions
v4 · July 7, after the morning meeting — current spec

## Three tracks replace the appendix spec

One dialogue (text or realtime voice) with contextual actions; one agent system wearing personas; ten-node graph with Connections first-class and the four access levels (public / private / secret / personal) on everything; markets renamed Forums; one pass/fail token per member — never pay-to-vote; all money on the web; the isometric world promoted to Training with portals, regimens, ally roles, and no real financial impact.

Experience Orchestration Foundation
Design R2 · July 7, overnight

## One app: the Thread on a living ground

Five paradigms integrated as postures of one surface — deck present only when cards exist, rooms as takeovers, the Vigil as a residue-free lens, drift as an interruptible grounding crossfade, making in three beats. Its realm-expression and motion specs remain in force under v4.

Integration Key Screens Motion Realm Expression Making
The Working Organization v1.2 · July 7, evening

## First principles; the Account replaces the newspaper

Eight member moments derived function-first; the daily Edition retired for since-you-were-gone rendering; the two-worlds model (agent-centric app, people-centric networks) with the ambient ally correction; the 29-worker roster; four real dunas worked in detail. Still the narrative canon — read with v4's simplifications in mind.

v1.2 (current text) v1 (archived) the team brief that pairs with it
Interface Paradigms R1 · July 7

## Five wildly different concepts

Broadsheet, Commons, Docket, Vigil, Bell — each breaking three assumptions of the five-tab prototype. The exploration that broke the deterministic inheritance.

the canvas the overview
Launch Spec v3 · July 6, night

## The design north star bolted onto the tab spec

Edition/Docket north star, the Commons-seed ladder, and six appendices (agent roster, graph schema, HEARTS, Codes, wallet, Vibe) — the last version organized as spec-plus-appendices, and the version whose middle still believed in tabs.

archived page Drive copy
Launch Spec v2 → v1 · July 6

## The organization-not-platform reframe

v1 synthesized the launch whiteboard and team syncs (five-tab nav, one ally, $100 onboarding, 7× compute). Moto's markup made v2: Kidunaverse/Kinship Duna naming, the stack (Postgres + AGE, LangGraph, Flutter/Flame), Charleston, and the first six appendices.

v2 on Drive v1 on Drive

Prototype cuts from along the way: one — five tabs · two — the Edition · three — the Thread & Account (all superseded, kept for comparison)