# Claude — read this first

You are inside the **Kiduna Kit · v4.3 (2026-08-01 — the complete August 1 canon: Taxonomy v1.3.8 final, the eight Scenes with Exchange ruled to **Settle**, Scenes as places with **Portals** reinstated, the **composition grammar** for the Garden, the **Workbench trust model**, all four Surfaces in the first release, **Allies in every view**, the **economic rails** (real FROST and Squads wallets, orchestration in place of an external token platform, all-$KIDUNA liquidity at launch), the ten Realm types, the privacy hierarchy, no offline mode, the adoption rule, the platform floors, the design repository — and §14, the name: **it is Kiduna**. Plus THE KIDUNA CANON in one standalone document, the INITIAL RELEASE FUNCTIONAL SPECIFICATION v2.0, an EMPTY decision queue, both papers, the Enamel Studio UI canon, the Design Method and round prompts, the Dunaversity launch spec and Engineering Handoff v2, the Studio handoff, RATIFIED Graph Architecture v1.1, Surfaces Design Bible v0.1, the Ki package, launch deck, plug-in brief, round r8)**, a self-contained offline archive of https://kiduna.team — the complete working specification of Kiduna, built by Kinship Duna (WV Org 628407). Someone participating in the build — a Builder, a Creator, a dev, a partner — has handed you this folder so they can work without the website.

**Orient:** read `START-HERE.md` now. It routes you by tool and by what your human is building, and it carries the terminology that is law. Read `the-kiduna-canon.md` before anything else in the archive — it is the whole canon in one standalone document; `initial-release-functional-spec.md` (v2.0) is what the first release must do; `taxonomy.md` (v1.3.8) is the law behind both.

**Ground rules for working in this archive:**

1. This archive is reference, not a working repo. Do not edit the archived files. Put new work — drafts, code, designs, proposals, questions — in a fresh `work/YYYY-MM-DD-topic/` folder beside them.
2. Answer only from these documents, citing file and section (e.g., `protocol.md §4`). If the archive doesn't answer something, say so plainly and flag it as a question for Moto — never invent. As of 2026-08-01 the product decision queue is **empty**: what is unspecified is design detail, not canon.
3. **The name is Kiduna, never "Kidunaverse"** (Taxonomy v1.3.8 §14). Historical documents here keep their original wording and are read with the substitution; addresses and filenames keep their spellings. No new writing uses the old word.
4. The securities vocabulary in `legal.md` is binding on anything public-facing you draft: Compute is "prepaid usage credits that power intelligent agents"; never investment/ROI/passive-income language; deciding is never fundraising; votes are never weighted by money.
5. Members, never users — and members are Sources; their visible identity is their Ally. Examples only from the 31 real DUNAs in `organizations.md`. For any design or build work, `taxonomy.md` v1.3.8 governs the shape of the product; Ki speaks in the third person, never "I."
6. If you have web access, https://kiduna.team is the newer authority; this package is a snapshot of it.
7. When your human has output, zip the `work/` folder and have them send it to Moto (david.levine@kinship.systems). His Claude unpacks and responds.
