# Canon delta — 2026-08-01 (the Final Canon Taxonomy)

For the kidunaverse-cofounder skill and any collaborator syncing canon. Source of authority: Taxonomy v1.3.8 (owner-ruled). Everything below is now settled canon.

## Settled today

1. **The eight Scenes** — the application's working contexts, one verb each: **Atlas** (discover; read-only; Gravity orbits, pan/zoom override) · **Studio** (create; Wisdom, Presence, names, original SVG icons/interface elements) · **Commons** (organize; people; scoped to Realms) · **Workbench** (build; agent/automation sandbox; Claude Code/Codex plugin seam) · **Forum** (govern; proposals, equal voting, duna token release) · **Exchange** (trade; buy Compute, tokens ↔ USDC ↔ $KIDUNA) · **Garden** (enjoy; where built apps get used) · **Vault** (store; on/off-ramp; **web only**).
2. **Surfaces are form factors**: Desktop web (Field + Ki) · Mobile · Chrome Sidebar · CTV (shared screen, mobile-driven, multi-person). The six official homes remain entry points; Chat/Live remain the modes.
3. **The Seven Elements**: Realms · Actors · Media · Allies · Resources · Actions · Offers. **Offers admitted as seventh** (supersedes "Offerings are Realms").
4. **The Six Capacities, final** (closes the old capacity-verb question — both Enable and Impart exist, Coherence is sixth): Inform with Wisdom (vector DB) · Instruct for Presence (system prompt) · Empower with Connections (integrations) · Enable with Automations (deep agents, triggers) · Impart Abilities (skills, markdown) · Align for Coherence (sentinels, values).
5. **The economic rails** (SUPERSEDED same day by the OQ-C5 ruling below — the "internal ledger / tokens as database entries / 20-20 pools" reading no longer governs).
6. **Voting is equal** — never weighted by money or holdings, in any Realm.
7. **Themes — the intention layer**: not an eighth Element; `hasTheme` edges on Realms/Allies/Offers; 26-theme spine in 6 clusters; ≤3 per Realm; folksonomy sub-themes; aggregation up the nesting; theme-affinity matching; cluster names internal; never a theme named "Media."
8. **AI-native + done-means-done** are canon: no fixed menus/navigation; the release standard is complete across Scenes and Surfaces, not MVP.

## New pages

- `taxonomy-summary.md/.html` — the one-page reading of the final taxonomy.
- `initial-release-functional-spec.md/.html` — the complete non-technical functional spec of the initial release; asks engineering for (1) a ranged weeks-to-completion estimate on the §8 grid and (2) the complete-stack architecture document (front end / middle tier & orchestration / back end, per Surface and Scene).

## New open questions

~~OQ-C1 Garden per-app interface model~~ · ~~OQ-C2 Workbench plugin contract~~ · ~~OQ-C3 CTV in/out~~ · ~~OQ-C4 the two senses of "Scene"~~ · ~~OQ-C5 ledger↔rails~~ (**all five RULED same day — see below**) · OQ-C6 theme icon production · OQ-C7 sub-theme promotion mechanics.

## OQ-C5 ruled (2026-08-01, owner): the economic rails

**The economy is on the blockchain from day one.** Wallets: every Source has a **FROST wallet**; every Organization (DUNA), Alliance, and Institution has a **Squads wallet**; Communities and Relationships hold no wallets. Everything wallet to wallet, **orchestrated by agentic AI** behind the command boundary. **Dropped: the external token platform whole** (MetaDAO-style launchpads; futarchy — pay-for-voice pass/fail markets, rejected as contradicting equal voting; automatic 20%-to-DEX mechanics; founder monthly treasury draws; per-project tokens; the Solana programs enforcing them) — every function performed instead by orchestration + database layers over the real wallets. **No new blockchain code needed to launch; decentralize enforcement over time.** **Liquidity never fragments: all $KIDUNA at launch**; duna tokens when ready (release mechanics TBD with the economy). Utility model is the engine: $KIDUNA pays for intelligence; **Agency Premium** — each duna sets its LLM price, part of the premium to its treasury, waterfall distributes. **Commissioned: the full economy document + an economy nightpaper.**

## OQ-C4 ruled (2026-08-01, owner): Scene has one sense — and Portals return

**A Scene is a unique area — a room, a scenario, a place — rendered in Flutter/Flame with sprites, tiles, and interface elements: a cohesive set of Media connected to the full Kiduna stack.** NOT "a Media system attached to a Realm" (v1.3.4 reading superseded). The eight canonical Scenes are the launch set; **Builders create their own Scenes** in Studio and the Workbench, deployed as unique ways to Enjoy or otherwise use Realms (under the Workbench trust model). A Garden app is exactly a deployed Scene; the composition grammar is its interface vocabulary. **Scenes connect through Portals — the navigation from Scene to Scene** — reinstating Portals (supersedes the v1.3.4 Portal elimination); the design portal grammar stands (tap to enter, abortable crossing, press-and-hold only for signatures).

## OQ-C2 ruled (2026-08-01, owner): the Workbench trust model

Member-built things ARE **Abilities** (the Impart Abilities Capacity, member-implemented) plus the Automations composed from them. Safety = **Realm containment + role + inspection**: custom Abilities operate only in Realms where explicitly deployed (no global deployment); deployment requires the **Builder role** in that Realm and is a named deterministic Action; Builder and Ability are **inspectable** (author, history, provenance, reach — trust the Realm, trust the Ability); the **plugin checks credentials** at hand-off and return; public Abilities carry their full history into adopting Realms; **Sentinels run the acceptance protocol** (prompt injection, malicious code, bugs), handshaking with the Claude Code/Codex plugin on flagged items — returning packages land as drafts, nothing deploys until acceptance passes, violations quarantine as evidence. Remaining: wire-level package format + sandbox runtime = engineering spec (architecture doc), not owner decisions.

## OQ-C3 ruled (2026-08-01, owner): CTV ships in the first release

**A basic version of all four Surfaces — Desktop web, Mobile, Chrome Sidebar, CTV — is in the initial release.** Depth varies, presence does not. CTV: Flutter/Flame on Android TV, driven by the room's mobile devices, Garden first.

## OQ-C1 ruled (2026-08-01, owner): the Garden interface model is the composition grammar

A small vocabulary of interface primitives (~15, ruthlessly held: cards, panels, lists, maps, schedules, tiles, chips, action cards) with combination rules; Studio (and Ki) authors app experiences by composing; a **deterministic renderer** draws them. Why: it's the v1.3.4 law (stable Media, dynamic composition) applied to the Garden; the command boundary is preserved by construction (a grammar can't invent an action); and the next app is free — what a duna factory needs. **Archetypes are starter content, generative is the ceiling**: launch apps (veterans, course, tourism, store) ship as authored compositions in the grammar; post-launch Ki composes generatively *within* it — arranging primitives, never inventing them; Actions always render as deterministic chips/action cards. Fallback discipline: any hard-coded app is a composition-in-waiting (same data shapes), never bespoke screens. Estimation consequence: Garden = primitive set + renderer + N authored apps (countable).

## The evening close-out (2026-08-01, owner): the queue emptied — OQ-C6, C7, B1..B10

- **Realm types FINAL at ten (was OQ-B10):** Ecosystem · Organization · Alliance · Program · Project · Relationship · Community · Institution · Concept · Cell. Offering retired as a type (Offers is an Element); Member Realm retired as a type. → Taxonomy v1.3.8 §9
- **The privacy hierarchy (was OQ-B5):** an item may carry MORE privacy than its context, never less; public is only really public in a public Realm. → §10
- **No offline mode (was OQ-B6):** not connected = not present; downloads are just downloads; the brief's offline-preparation language superseded. → §11
- **The adoption rule (was OQ-C7):** any Realm adopts anything public or offered to it — its choice; Ecosystem (Kinship Duna) adoption through regular governance makes a thing available everywhere. General across Abilities, Scenes, sub-themes, vocabulary. → §12
- **Platform floors adopted (was OQ-B8, co-founder recommendation accepted):** desktop designed 1280px / functional 1024px (Ki collapsible; mobile rendering below); iOS 16+ / Android 10 (API 29)+, 360×640 min; CTV Android TV/Google TV 1080p; **WCAG 2.2 AA formal baseline**, nothing formally exceeding it at launch. Owner-adjustable. → §13
- **Iconography = the design repository (was OQ-C6):** one consistent, growing library of icons/symbols/graphics across the eight Scenes; production track, not canon. → §13
- **OQ-B1 OBE:** the brief's Studio-desktop/Live-mobile two-distances framing is historical — Studio is a Scene, not a Surface; journeys/starting points are design work. → §2
- **Retired to design (no canon ruling wanted):** OQ-B2 field return · OQ-B3 focus (Ki + Source figure it out; prompts/wisdom set baselines; no generic solution) · OQ-B4 action-state vocabulary · OQ-B7 money-movement UX.
- **OQ-B9:** no external validation or expert panels at this stage; particular Realms decide their own.
- **The standing decision queue is EMPTY.**

## The name (2026-08-01, owner, night): "Kidunaverse" is retired — it is Kiduna

Everywhere, permanently: the system, the application, the world — **Kiduna**, one word. Applied across every living track (md + html, ~37 files). Rules: historical documents, ratified specs, and the taxonomy's verbatim v1.3.3 base keep their original wording and are READ with the substitution; addresses and filenames keep spellings until re-homed (kidunaverse.com is an address, not a name; the home there is called simply **the account**); no new writing uses the old word; where the app and another home would both read "Kiduna," use the plain role (the app, the account, the extension). NOT yet updated: historical pages (nightpaper v0.1, white papers, ratified graph architecture, versions history, design rounds, archives), the kit harness files (KIDUNAVERSE-COMPLETE.md → rename at next kit rebuild), the kidunaverse.com public site itself, and the dispatch folder name / project folder name ("Kidunaverse") on disk. → Taxonomy v1.3.8 §14

## Late rulings (2026-08-01, night): Settle · Allies in every view · the Canon document

- **Settle replaces Trade** as the Exchange Scene's verb: Discover-Atlas · Organize-Commons · Create-Studio · Build-Workbench · Govern-Forum · **Settle-Exchange** · Enjoy-Garden · Store-Vault.
- **Allies are in every view**: the people render in every Scene on every Surface; selecting an Ally opens it (who it represents, its Presence, how to engage). Moto's fuller selection-behavior sentence was cut off — awaiting completion.
- **New standing document: `the-kiduna-canon.md/.html`** — the whole canon in one standalone page.

## Supersessions to watch in older text

- Five-capability lists (Wisdom/Presence/Abilities/Automations/Connections) → six Capacities.
- "Offerings are Realms" → Offers, first-class Element.
- Surfaces-as-products readings → Surfaces are form factors; Scenes are the working contexts.
- Any on-chain-at-launch implication → internal ledger at launch.
- "Kai" anywhere → **Ki**.
