# Kiduna Kit · v1.4 (canon v5.4 + Design R7) · 2026-07-10

**You are (most likely) an AI — Claude, ChatGPT, or another model — handed this archive by someone who wants to participate in building the Kidunaverse: a Builder, a Creator, a core dev, a partner, or someone just curious enough to start. The Kiduna Kit is the real archive of the entire effort — everything anyone needs to understand, question, and extend the Kidunaverse without visiting the website. We build by Creating from Within (`create-from-within.md`); on August 10 the whole stack ships open source (Apache 2.0). Current as of the build stamp in `MANIFEST.md`.**

## What this is

The complete working specification of the Kidunaverse — the agentic internet being built by Kinship Duna (WV Org 628407) — as a self-contained offline copy of the team site (live at https://kiduna.team). Inside: all eleven spec tracks (`.md` source + rendered `.html`), the narrative canon, the engineering architecture, the complete UI design across all four rounds (viewable offline), the interface-paradigm concepts, the early prototype, the full versions record, the open product and legal queues, and the current canon deltas for Moto's Claude skills.

## How to load me — pick your tool

- **Claude chat / Claude Projects** — upload `KIDUNAVERSE-COMPLETE.md` (the whole spec as one file) to the conversation or Project knowledge, and paste the block inside `LLM-INSTRUCTIONS.md` as the Project instructions. For deep design work, also upload the `design-r4/*.md` files.
- **ChatGPT (chat, Projects, or a custom GPT)** — the same two files: `LLM-INSTRUCTIONS.md` block into Instructions, `KIDUNAVERSE-COMPLETE.md` into Files/Knowledge. ChatGPT can also unpack this whole zip in a data-analysis session and browse it directly.
- **Cowork** — connect the unzipped folder as the working folder; Claude reads this file and `CLAUDE.md` and orients itself.
- **Claude Code** — run it inside the unzipped folder; `CLAUDE.md` loads automatically.
- **Codex** — run it inside the unzipped folder; `AGENTS.md` loads automatically.
- **A human with a browser** — open `index.html`. Every page works offline, including the full design canvases.

## What to do (any tool)

1. Ask your human their name and what they're building this week (back end/graph · middle tier/agents · mobile/Flutter · web money surface · design · content · legal).
2. Read `index.html`'s narrative (or `KIDUNAVERSE-COMPLETE.md` front to back) — then go deep on their track:
   - Back end / graph / permissions → `foundation.md`, then `protocol.md`, then `kiduna-architecture.html`
   - Middle tier / agents / channels → `orchestration.md`, then `actions.md` and `sentinel.md` (the interaction-health regulator lives in this layer)
   - Mobile / Flutter / UI → `experience.md` (§7 links every design deliverable), then `design-r4/UX-SPEC-R4.md` and the canvases, then `actions.md`
   - Web money surface → `design-r4/Web Money Surface R4.dc.html` + `experience.md` §4 + `protocol.md`
   - Public copy / content → `real-work-real-money.md`, `legal.md` (its securities vocabulary is BINDING), `organizations.md`
   - Legal → `legal.md` (rules in force), `legal-items-for-review.md` (the open queue, L-8..L-15)
3. Answer questions from these documents only, always citing file and section. If the docs don't answer something, say so plainly — don't invent; flag it as a question for Moto.
4. When your human has output — questions, designs, code notes, proposals — package it as a zip and have them send it to Moto (david.levine@kinship.systems). His Claude unpacks and responds. This zip exchange is deliberate practice for member → ally → ally → member collaboration.

## The terminology that is law

Compute (never "compute currencies") · Forums (never markets) · Chat and Reality (the two surfaces) · Guilds (no wallet) vs Alliances (Squads wallet) vs Organizations (registered DUNAs) vs Institutions (outside entities, no vote) · Allies and Actors (the only two agent families) · four access levels: public, private, secret, personal · members, never users · registered / unregistered (never "trusted" or "accountable") for anything bound to the protocol · examples only from the 31 real DUNAs (`organizations.md` §2) · organizer commissions attach only to Clan Compute purchases — default 20/5/3/2 by generation, four deep, Catalyst-set, Forum-changeable, optional per duna · nothing in Kidunaversity affects the Kidunaverse · deciding is never fundraising · Compute is "prepaid usage credits that power intelligent agents" — never investment/ROI/passive-income language anywhere · members never see HEARTS meters; the member-facing word is "vibe."

## Current state of the spec

**Canon v5.3 (2026-07-11) is in force: read `skill-updates/cofounder-canon-2026-07-11.md` FIRST — it supersedes conflicting track text (Kiduna Server/mesh, Kiduna Protocol on Solana, the Network, Kiduna Live with the Field + Scenes + ACTIONS, Studio Projects, the trust matrix).** The spec is at **v5.2** — eleven tracks plus the method page (`create-from-within.md`). New at v5.2: the modes are **Chat and Live** (Moves are the authored Live experiences); six surfaces (kiduna.app · kiduna.live · kiduna.one · kiduna.studio · kiduna.express · kidunaverse.com); **KAP** formalized (Agency Servers/Clients; ecosystems; the Genesis Ecosystem Kiduna; Apache 2.0 on Aug 10; Kinship Agents DAO steward); the hierarchy founded on Ecosystems; Sources, handles, and Ki (the Genesis Ally); the Profiler as the first Program; Lightbrush LLC as the first Institution integration. Design Round 5's first delivery is installed: `design-r5/Cohort Journey R5.dc.html` (the cohort journey — invitation, onboarding, the three-path $100 step, first Chat and the relationship card); the round's remaining deliverables (Move, Studio redesign, kidunaverse.com/protocol browser, MVP cut) are pending — the brief is `design-r5/R5-PROMPT.md`. New at v5.0: Track 1 is **The Surfaces** (the four products: Kiduna — the app, with Chat and **Move** (supersedes "Reality"); Kiduna Express — the browser; Kidunaverse — the account and protocol browser, with the three-option USDC onboarding; Kiduna Studio — the building surface, being redesigned agentic); **Institutions** (Track 10) and **Integrations** (Track 11); between two people it is a **relationship**, never a "connection"; the launch cohort of Catalysts and Luminaries is seated (`roles.md` §1) and starts within Kiduna Club. The product Open Questions queue is empty. The legal queue is open (`legal-items-for-review.md`, L-8..L-15: ToS, Privacy, Kiduna Club IP licensing, KII fiscal sponsorship, patent provisionals, COI policy, initial-purchase mitigation, final counsel review). Recent rules in force: counsel's seven resolutions (Track 9, priority-ordered); the Sentinel's bipolar meters where zero is health (Track 8); organizer economics (`real-work-real-money.md` §3); the gold ceremony marks signed acts only; receipt sentences are machine-generated from command parameters, never hand-written; the decentralized registry with registered/unregistered vocabulary (`protocol.md` §4). Full history: `versions/index.html`.
