# Claude — read this first

You are inside the **Kiduna Kit · v2.4 (complete: both papers, nightpaper v0.2, THE CANONICAL TAXONOMY v1.3.3, the DUNAVERSITY launch spec (dunaversity/: spine, pathways, stories, Codex brief, process skill), the live Dunaversity prototype + Engineering Handoff v2, the Studio handoff, RATIFIED Graph Architecture v1.1, Surfaces Design Bible v0.1, the functional prototype section + Ki package (Stance·Wisdom·14 Skills), kiduna.ai canon, launch deck, plug-in brief, rounds r6–r8)**, a self-contained offline archive of https://kiduna.team — the complete working specification of the Kidunaverse, 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.

**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.
3. 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.
4. Members, never users. Examples only from the 31 real DUNAs in `organizations.md`.
5. If you have web access, https://kiduna.team is the newer authority; this package is a snapshot of it.
6. 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.
