# Kiduna Kit · v4.3 — the complete August 1 canon (2026-08-01)

**The name is Kiduna.** One word for the system, the application, and the world. "Kidunaverse" is retired (Taxonomy v1.3.8 §14); historical documents in this archive keep their original wording and are read with the substitution, and addresses like kidunaverse.com keep their spellings.

**You are (most likely) an AI — Claude, ChatGPT, or another model — handed this archive by someone who wants to participate in building Kiduna: 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 Kiduna 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`.**

## Read these three first, in this order

1. **`the-kiduna-canon.md`** — the whole canon in one standalone document: the eight Scenes, the four Surfaces, the six Capacities, the seven Elements, the ten Realm types, the twenty-six Themes, and the rules that bind them. Fifteen minutes, no links, nothing else assumed. Read it end to end and you know what Kiduna is.
2. **`initial-release-functional-spec.md` (v2.0)** — what the first release must actually do, Scene by Scene and Surface by Surface. Also standalone.
3. **`taxonomy.md`** — the Core Taxonomy v1.3.8. This is the **law**: where any other document disagrees with it about the shape of the product, it wins. `taxonomy-summary.md` is its one-page reading.

## What this is

The complete working specification of Kiduna — 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: the Canon, the functional specification, the Core Taxonomy and its summary, all eleven spec tracks (`.md` source + rendered `.html`), the Studio + Live Working Design Brief, the Genesis Nightpaper v0.3, the narrative canon, the engineering architecture, the UI design (viewable offline), the full versions record, the open legal queue, and the current canon deltas for Moto's Claude skills.

**The product decision queue is empty.** As of 2026-08-01 every open canon question has been ruled or retired (`open-questions.md`). What remains unspecified is design detail, not canon.

## How to load me — pick your tool

- **Claude chat / Claude Projects** — upload `KIDUNA-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-r8/*.md` files.
- **ChatGPT (chat, Projects, or a custom GPT)** — the same two files: `LLM-INSTRUCTIONS.md` block into Instructions, `KIDUNA-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 · desktop web/Field · CTV · design · content · legal).
2. Read `the-kiduna-canon.md`, then go deep on their track:
   - **Scoping or building the release** → `initial-release-functional-spec.md` front to back
   - Back end / graph / permissions → `foundation.md`, then `protocol.md`, then `kinship-graph-architecture-v1.1.md`
   - Middle tier / agents / channels → `orchestration.md`, then `actions.md` and `sentinel.md` (the interaction-health regulator lives in this layer)
   - Surfaces / Flutter / UI → `surfaces.md` (§8 links every design deliverable), the design canvases, then `actions.md`
   - The Garden and its apps → the composition grammar in `taxonomy.md` §1 and the functional spec §3.7
   - The Workbench and member-built capability → the Workbench trust model in `taxonomy.md` §1 and the functional spec §3.4
   - 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)
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

**Kiduna**, never "Kidunaverse" · the eight **Scenes** — Atlas (discover) · Studio (create) · Commons (organize) · Workbench (build) · Forum (govern) · Exchange (**settle**) · Garden (enjoy) · Vault (store) · a **Scene** is a unique place rendered in Flutter/Flame, a cohesive set of Media connected to the full stack, and Scenes connect through **Portals** · a **Surface** is a form factor (Desktop web · Mobile · Chrome Sidebar · CTV), never a product · the seven **Elements** (Realms · Actors · Media · Allies · Resources · Actions · Offers) · the ten **Realm types** (Ecosystem · Organization · Alliance · Program · Project · Relationship · Community · Institution · Concept · Cell — a closed set) · the six **Capacities** (Inform with Wisdom · Instruct for Presence · Empower with Connections · Enable with Automations · Impart Abilities · Align for Coherence) · **Themes** are what a thing is about, never an Element · Compute (never "compute currencies") · Forums (never markets) · the modes are Chat and Live · 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 — members are **Sources**, and their visible identity is their **Ally** · registered / unregistered (never "trusted" or "accountable") · handles, never usernames · between two people it is a **relationship**, never a "connection" · 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 Kiduna · deciding is never fundraising · **votes are never weighted by money** — futarchy and every pay-for-voice scheme are rejected · 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" · Ki always speaks in the third person, never "I."

## Current state of the spec

**Taxonomy v1.3.8 is the final canon taxonomy, and the whole of August 1 is in it.**

**The eight Scenes.** Atlas (discover; read-only; the Gravity orbits where distance means current relevance, pan and zoom always overriding) · Studio (create; Wisdom, Presence, names, original SVG icons — and Scenes are built here) · Commons (organize; people; scoped to Realms) · Workbench (build; the maker's sandbox and the Claude Code / Codex package seam) · Forum (govern; equal-weight voting, never money-weighted) · Exchange (**settle**; Compute, and moving between $KIDUNA and USDC) · Garden (enjoy; where everything the members build gets used) · Vault (store; on/off-ramp; web-only).

**A Scene is a place, and Portals are back.** A Scene is a unique area — a room, a scenario, a place — rendered in Flutter/Flame with its sprites, tiles, and interface elements: a cohesive set of Media connected to the full Kiduna stack. The v1.3.4 "Media system attached to a Realm" reading is superseded, and the v1.3.4 elimination of Portals is reversed: **Scenes connect through Portals** (tap to enter, abortable crossing, press-and-hold reserved for signatures). The eight canonical Scenes are the launch set; **Builders create their own** and deploy them into the Garden.

**The Garden interface model is the composition grammar.** ~15 interface primitives (cards, panels, lists, maps, schedules, tiles, chips, action cards) with combination rules, authored in Studio and by Ki, drawn by a deterministic renderer. Archetypes are its starter content — the launch apps ship as authored compositions; generative is its ceiling — Ki arranges primitives, never invents them, and Actions always render as deterministic chips and action cards.

**The Workbench trust model.** What members build are **Abilities** (the platform's own Impart Abilities Capacity, member-implemented) plus the Automations composed from them. Safety is **Realm containment + the Builder role + inspection**: an Ability operates only where explicitly deployed; deployment requires the Builder role and is a named Action; author, history, provenance, and reach are inspectable; the plugin checks credentials at hand-off and return; public Abilities carry their history wherever they travel; and **Sentinels run an acceptance protocol** (prompt injection, malicious code, bugs), handshaking with the coding-agent plugin — a returning package is a draft until acceptance passes, and violating packages quarantine as evidence.

**All four Surfaces ship in the first release** — CTV included. Depth varies, presence does not. **Allies are in every view**: the people render in every Scene on every Surface, and selecting an Ally opens it (who it represents, its Presence, how to engage).

**The economic rails.** The economy is on the blockchain from day one and the intelligence runs it: a **FROST wallet** for every Source; **Squads wallets** for Organizations, Alliances, and Institutions; none for Communities and Relationships. Everything moves wallet to wallet, orchestrated by agentic AI behind the command boundary. The **external token platform is dropped whole** — launchpads, futarchy (rejected: it contradicts equal voting), automatic percent-to-DEX mechanics, founder treasury draws, per-project tokens — and every function it performed is performed by the orchestration and database layers over the real wallets; no new blockchain code is needed to launch. **Liquidity never fragments: all $KIDUNA at launch**, duna tokens when ready. The **Agency Premium** is the engine — each duna sets what its intelligence costs, part flows to its treasury, the waterfall distributes the rest. A full economy document and an economy nightpaper are commissioned.

**The close-out rulings.** Realm types final at ten (Offering and Member Realm retired as types). The **privacy hierarchy** — an item may carry more privacy than its context, never less; public is only really public in a public Realm. **No offline mode** — not connected means not present; downloads are just downloads. **The adoption rule** — any Realm adopts what is public or offered to it; Ecosystem adoption through governance makes a thing universal (this is also how sub-themes join the spine). **Platform floors** — desktop designed for 1280 and functional to 1024, iOS 16+ / Android 10+, CTV on Android TV at 1080p, **WCAG 2.2 AA** as the formal baseline. **The design repository** — all icons, symbols, and graphics as one growing library. And the brief's "Studio the desktop surface / Live the mobile surface" framing is **historical**: Studio is a Scene, not a Surface.

**Still in force beneath the amendments:** the command boundary (the graph service is the sole policy and command boundary; intelligence proposes, deterministic code authorizes and commits; receipts generated from executing parameters so they cannot lie); person-vouched identity (a Kinship Code plus a Handshake; one hundred dollars once, for life, as the initial Compute purchase); the Studio + Live brief's product rulings, read through v1.3.8; counsel's seven resolutions (`legal.md`, priority-ordered); the Sentinel's bipolar meters where zero is health; organizer economics (`real-work-real-money.md` §3); the decentralized registry and its registered/unregistered vocabulary (`protocol.md` §4). Canon v5.3 (`skill-updates/cofounder-canon-2026-07-11.md`) still supersedes conflicting older track text. Full history: `versions/index.html`.
