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
Dunaversity · 2026-07-20 — current

## Dunaversity: the first duna, specced in a day, prototype live by night

The launch plan pivoted to Dunaversity first (release target July 25–27), and one day of step-by-step co-founder work produced the whole chain, now in dunaversity/: the spine (structure, tiered Creator role, Badges-as-NFTs, Wisdom-on-the-Field, the USDC-first economics with the unchangeable rules — lineage 30% initial / 18% lifetime, 3% Kiduna Club, 20%/$50K admin minimum — and Kinship Duna treasury consolidation), the four pathway narratives (Moto · Aashik · Matt · Paul), the UI/UX story set from first login, the Codex controlling brief, and the documented spec-design process. By evening: the Dunaversity prototype live with the Studio ↔ Live switch, and the Engineering Handoff v2 published with its source-of-truth order. Canon that day: Kidunaverse retired as the environment name (it's Kiduna); governance voting credits are valueless; $KIDUNA is for Compute, period. Kit v3.5 carries all of it.

The prototype Handoff v2 The stories Canon delta
v1.3.3 + the Engineering Handoff · 2026-07-19

## The taxonomy learns restraint; Studio gets its handoff

Canonical v1.3.3 supersedes v1.3.2 with owner-approved clarifications: the Field is always present but need not be continuously visible; Realms carry ongoing and collective agency (which never creates authority); Ki may reflect collective Wisdom only within permissions — never exposing private contributions, inventing consensus, or becoming surveillance; focused Panels and Scenes clarified without prescribing a Studio layout; an explicit boundary — Atlas, Focus, Pulse, Lens, Stage, and the one-center shell remain non-canonical working terms — and the taxonomy impact rule for every future design turn. The Kiduna Studio Preliminary Engineering Handoff is published on the Prototype page (post-Gate 2B.1: the five Outside journeys, the one-center experiment, three primary Realm Scenes, plans, stories, acceptance matrix, open decisions). Superseded taxonomy artifacts pruned sitewide; the kit drops r6/r7 and the pre-v1.1 graph pages. Kit v3.4.

Taxonomy v1.3.3 The handoff Canon delta
Canonical Taxonomy v1.3.2 COMPLETE · 2026-07-19

## All twenty-one sections — one Field, one Ki, Realms all the way down

Moto delivered the complete canonical document and it is installed verbatim as the taxonomy page (markdown). The twenty primary elements, fully defined. The headline changes: Ki is the Ally — one coherent Ally across the Kidunaverse, personalized per relationship, never a cast of separate assistants; Presence replaces "user" and "persona" (Singular · Plural · Visitor · Guest · Member · Cloaked, with Persona/Alias/Mask governing concealment); Realms generalize every container (including Member Realms, Offerings-as-Realms, and programs as a Realm type); four canonical Surfaces (Studio · Live · TV · Express, with Live controlling TV); the Founder rule resolved (first 100, or pre-close purchasers where a sale runs); Wizard/Mage bounded with cannot-lists — no superusers anywhere; Visibility as its own enforceable axis; Elements, Panels (opacity never changes permissions), Scenes and Portals fully specified. Ripple list for the fold is in the delta. Kit v3.3.

The taxonomy v1.3.2 markdown Canon delta
Canonical Taxonomy v1.3.1 · 2026-07-19

## Realms, Presences, and Treasuries — the canonical line begins

The taxonomy becomes the canonical working taxonomy v1.3.1 (a renumbered canonical line superseding the "v2.0 revised edition"). Installed from Moto's text (§§19–21 preserved verbatim): the Realm / Presence vocabulary (Realms are what can be entered; Presences are who participates; Ki is the Ally; Elements, Panels, Scenes-through-Portals, Privacy and Visibility, Wizard and Mage as bounded admin roles); the complete Treasuries section — any Realm may have one, wallets AND bank accounts, Squads for Organizations (Forum = authority layer, Squads = execution layer) and Alliances, three-share FROST for Members, External wallets by Connection, five-level treasury authorization (adding Multisignature), twelve invariants including no-universal-access; and Compute re-grounded on Realms with lineage 20/5/3/2 per-Realm. Sections 1–18 pending. Kit v3.2.

The taxonomy §§19–21 verbatim Canon delta
Core Taxonomy v2.0 + Programs · 2026-07-18

## The revised edition — Projects are Principals, Wallets are Resources, conflicts resolved; Programs added 07-18

Moto's revised Core Taxonomy (v2.0, as-is) replaces the morning page as the document of record; taxonomy.html now mirrors it. The big moves: Projects join the Principals (durable identity, delegated authority, no separate legal standing, Wallet optional); Resources become a core category with Wallets defined (external single-sig · FROST personal · Squad multisig; owner/beneficiary/controller/custodian distinguished; possession of a key share never establishes authority); Relationship = two or more Principals, able to live outside containment; personal becomes a rights dimension that can coexist with public/private/secret; Verified is a state, not an origin; and the five authorization levels (Autonomous · Confirmed · Deliberate · Governed · Prohibited) become the canonical permission grammar. Protocol licensing splits into two rules paid to Kiduna Club. Twelve resolutions recorded in the delta. 2026-07-18: Programs join the Principals — large-scale Organization initiatives containing multiple Projects, Alliances, Communities, and Relationships; Projects may nest inside Programs. Kit v3.1.

The taxonomy The v2.0 PDF Canon delta
The Core Taxonomy · 2026-07-17

## The primary elements, rebuilt — "if we get these right, we've won"

The Core Taxonomy page is live under Architecture and now leads the hero's first-read list: Principals (Member · DUNA · Alliance · Community · Institution · Relationship · Forum · Ecosystem, with the containment rules — alliances and communities inside dunas; institutions and members never), privacy always FOR a principal (one item can be private to several at once), media (the three engines — Wisdom, Stances, Abilities — plus Artifacts with generated/imported/verified/external origins), the five capability verbs, status (draft → registered → launched → active for dunas), the strict-Allies/free-Actors rule, trust default-low, deterministic first-class Actions, the roles ladder (visitor → guest → member → creator → builder; founders = first 100, automatic), and Compute with the Agency Premium and the new per-purchase default: 30% lineage + 1% Kinship Duna + remainder to treasury. Governance: launch as-is on staked-proposal futarchy, renamed Forums, rework post-launch (the BonkDAO attack is the cautionary case). Five recorded conflicts await Moto in the delta. Kit v2.9.

The taxonomy Source PDF Canon delta
Nightpaper v0.2 · 2026-07-16

## The nightpaper reaches the living world

Second revision of the day: v0.2. Relational agency now extends beyond the individual human into the living systems that sustain us — rivers, watersheds, species, future generations as participants in the conditions of life, represented where decisions are made; agency in nested relationships (person · organization · community · ecosystem), "an architectural requirement, not an ethical ornament." The Kinship Agency Protocol gets its right name; Kiduna TV joins the surfaces ("same world, four different experiences"); the registered×trusted trust matrix (low/medium/high, authority proportional to confidence) goes member-facing; the money section becomes duna-set economics. Variances flagged in the delta: consensus-guiding Forums vs one-Member-one-ballot, gold → "marked clearly," the investment disclaimer now footer-only, the August 10 date dropped from §IV. Kit v2.8.

The nightpaper Canon delta + variances
Nightpaper v0.12 · 2026-07-16

## The Genesis Nightpaper, revised — agency lives in the relationships

The Genesis Nightpaper is updated to v0.12 from Moto's revision. The heart of it: agency is located in the relationships between individuals, organizations, and ecosystems — the edges, not the nodes — and the Agentic Age holds agency in the relational field. New thesis sentence, the Institutional Age at ~nine thousand years, the byline now David Levine · Founder & President, Kinship Intelligence Institute, and the close now points early access at kiduna.ai. Same four figures; same designed page. Kit v2.7.

The nightpaper Canon delta
The Functional Prototype · 2026-07-15

## Ki is live — the prototype section opens

The first functional prototype is deployed at kiduna.design and has its own section — Ki greeting first in a continuous Studio Field, the Genesis opening built around the Create-from-Within loop. The canonical Ki package is posted for download: the Stance (System Prompt v1.0 — the runtime contract), the Wisdom (Genesis Ally Complete Operating Knowledge v2.5, built from Kit v2.5, pgvector-ingested with provenance), and the fourteen Skills (zip). Stack: Next.js/React, PostgreSQL 16 + pgvector (Neon), Apache AGE locally, Vercel. Prototype truth rule in force: simulation is labeled; identity, authority, receipts, and provenance are never fabricated. The prototype record holds the five phases, including the rejected redesign. Kit v2.6.

The prototype The section The skills Canon delta
Surfaces Design Bible v0.1 · 2026-07-14

## The design bible, posted

The Kiduna Surfaces Design Bible v0.1 is live on the Surfaces track — the visual and interaction canon for the Field grammar and every surface (Studio, Live, Express, TV), with the design directions. Also packaged as a downloadable bundle (html · pdf · docx · md · assets). Kit v2.5.

The bible The bundle
Graph Architecture v1.1 · 2026-07-14

## The operating graph, ratified — Persona · Visitor · Guest · Member

The Kinship Graph Architecture v1.1 replaces v1.0 as the RATIFIED build spec for August 10. The human-state vocabulary is the headline: Persona (the durable identity, Source of an Ally) · Visitor (unauthenticated) · Guest (authenticated, not admitted) · Member (active, legally effective Membership — the authority-bearing object; payment alone never creates it). Twelve owner ratifications are incorporated: restrictive Guest allowlist, Institution as first-class outside principal, one-Member-one-ballot with decision markets as information only, one authority class per DomainCommand, independently gated economics, lineage skip-up rule, 20% liquidity as versioned policy default, disclosed agency pricing (7x Member / 2x-of-Member for Guests), the continuously-verified legal adapter, Home Ecosystem migration, and the August 10 activation freeze. New Figure 5: the invitation lifecycle. Kit v2.4.

The spec PDF Canon delta
v5.6 · kiduna.ai + the Genesis bootstrap + the outward stack · 2026-07-14

## kiduna.ai is the front door; Ki greets first; the MCP server is the platform product

From the 7/14 Techneural sync, the Agentic Internet whiteboard, and the plug-in brief (all in the canon delta): kiduna.ai becomes the authoritative registration, wallet, and launchpad home for Kinship Duna (third key share; api.kiduna.ai; absorbs kiduna.cash) — linked from the hero. The Genesis bootstrap is canon: Genesis Ecosystem → Genesis Ally Ki ("Kinship Intelligence" — everyone's first conversation, effectively the initial interface) → the Mage account → Genesis Codes → the member, on any surface. Trust grammar: High/Medium/Low per Relationship side · registered-with-whom (DUNA · KYC · DNS TXT · AT Protocol DID) · the four privacy levels. Codes: person-specific, single-use, 15-minute expiry; generalized codes default-untrusted; zero spam — the system never contacts the unregistered. Permissions: Allow once / Allow every time. First Actor kinds named: Profiler, Project Creator, Code Manager. Guests: $10 minimum, Compute at 2x. Integrations §8 specifies the outward stack — api.kiduna.ai, mcp.kiduna.ai, the two-platform plug-in monorepo, the first eight skills. The launch deck The Agentic Internet Starts Here is published (August 10–11, Charleston). L-18 stubbed for the vocabulary pass. Kit v2.3.

Canon delta Integrations §8 The launch deck L-18
Graph Architecture v1.0 · 2026-07-13

## The operating graph, specified — and the gap list closed

The Kinship Graph Architecture v1.0 is installed under Architecture as the spec of record for the graph, replacing the Kinship Graph Workflow and resolving all thirteen canon gaps. Fifteen executive decisions, among them: the graph organized around Members, Allies, Organizations, and Actions; every Action resolves to exactly one Organization (Kinship Duna only as recorded, allowlisted default); DUNA as a legal-form adapter, not the ontology; Forum replaces Market; Actions modeled as a subgraph (request → authorization → command → run → external operation → Record); the Graph Command Service as the one deterministic boundary; money auditable in the graph but enforced by a double-entry ledger; one PostgreSQL transaction boundary with an outbox — no dual writes; launch as a modular monolith; the full ontology now, risky economics behind policy gates. Build target: August 10, 2026. Kit v2.2 carries the spec, figures, and PDF.

The spec PDF The closed gap list Canon delta
Design R8 · 2026-07-13

## The Field on four surfaces, delivered — and the graph gaps published

Round 8 is installed complete: the Field grammar (Scenes and Portals, the HUD, ACTIONS, canonical representations for all eight major nodes), Studio (collaboration, Ally/Actor inspection, package transfer), Live, Express (the open web with registered/unregistered and the Kinship-Duna default), TV (the ten-foot Field with its refusals), and the cut with the cross-surface test. Its open questions await Moto in design-r8. The Kinship Graph canon-gap list is published beside the workflow — thirteen gaps as the revision brief, plus what's aligned. Kit v2.1 is the complete package: both papers, the nightpaper, the graph workflow and gaps, the architecture PDF, and rounds r6–r8.

UX Spec R8 01 The Field Grammar Graph gaps Open Questions
v5.5 canon + Graph Workflow · 2026-07-13

## The Field on four surfaces; Communities, Envoys, and the node canon

The Kinship Graph Workflow is published under Architecture as-is (vocabulary gaps flagged separately). New canon (the 2026-07-13 delta, which wins until the fold): the major nodes — Member · Relationship as a first-class dyadic node, per-Organization · Community (replaces Guild; 3+ members) · Alliance · Institution (KYB via the registered agent) · Project · Organization (the public word — never "duna") · Ecosystem (kap://eco.domain.net). Five agent types: Allies (exactly one per member; member → ally → ally → member; the ally filters all input) · Actors · Sentinels · Envoys (formerly Electors) · Operators. Every action any agent takes happens inside an Organization, as a member of it; the default is Kinship Duna. The Field is canon as the browser-for-KAP — always live; Scenes with Portals at both ends. Surfaces and homes: kiduna.studio · kiduna.live · kiduna.express · kiduna.tv (CTV), plus kiduna.cash as the wallet home. The R8 prompt (the Field on four surfaces) is at design-r8/. The Kit is rebuilt lean at v2.0 — superseded rounds stay in the repo, not the zip.

Graph Workflow The canon delta R8 prompt
Genesis Nightpaper v0.1 · 2026-07-12

## The Genesis Nightpaper, published

The Kidunaverse: A New Architecture for Agentic Civilization — agency as the core attribute of life at every scale; the three ages measured by agency rather than tools (Kinship · Institutional · Agentic); why where agency is located decides between the surveillance future and this one; and the whole technology explained for a non-technical reader, inside counsel's vocabulary. Dark/light with a print-to-PDF that always prints light. The home page now leads with it: "Read the nightpaper" sits under the Kit download, and the first-read set is the Nightpaper, the Kit, the Technical Specification, and the Technical White Paper. The Lightbrush agreement was sent to Moe the same day (L-16 → awaiting signature).

The Nightpaper The front door
Sixteen decisions · 2026-07-12

## The whole design queue, cleared

All sixteen open design questions from Rounds 6 and 7 decided in one pass — rulings appended verbatim to R7's and R6's files and summarized on Open Questions. The ones that change builders' plans: Projects always get a stable Scene identity and Field address, but a materialized room is earned by scale; gold marks only work entering or changing the Organization's authoritative Record; Package manifests are enforced with quarantine, not draft-entry, for violating returns; the Docket exists only as a projection of standing ACTIONS; profile and Code redemption take two signatures with separate Records; Ki's public door runs on a capped guest allowance funded as acquisition-and-education; one store listing (Kiduna, with Live as the mobile experience); the graph Relationship Record is the single source of truth; the practice currency is Practice Credits; and identity sameness is never claimed without registered proof. The product queue is empty.

Open Questions R7 rulings R6 rulings
White Paper v0.1 · 2026-07-12

## The technical white paper, published as-is

Kiduna: A New Architecture for the Agentic Internet (Technical White Paper v0.1) joins the Technical Specification v0.1 under Architecture, added whole and untouched. The home page now names the three assets to review first — the Kiduna Kit, the Technical Specification, and the Technical White Paper — in the top box; everything else on the site backs them up.

The White Paper The Specification Architecture Prototype
Architecture v0.1 · 2026-07-11

## The complete architecture, installed as-is

Kiduna: A New Architecture for the Agentic Internet — Product & Engineering Specification v0.1 is now the spec of record on the Architecture Prototype page, added whole and untouched: executive decisions · products and surfaces · the domain model · creating the first Ecosystem · Allies, Actors, and the first cast · the creation system · the Field and contextual HUD · Studio · Live · protocol and system architecture · trust, privacy, safety, and custody · the development plan · acceptance, quality, and operations · the canon objections and owner decisions · the canon source map. The Architecture page now opens with it; the earlier Protocol + Stack v1.0 PDF and Kiduna-Architecture draft remain as references.

The Specification v0.1 Architecture Prototype
Design R7 · 2026-07-11

## 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 Prototype 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 Prototype 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)