A member is always in something (a Realm), always doing something (a Scene), on some device (a Surface), always able to talk to Ki. Everything is made of seven kinds of thing, every agent is built from six kinds of input, and everything is about something.

Kiduna is one application. A member is always in something (a Realm), always doing something (a Scene), on some device (a Surface), always able to talk to Ki. Everything in the system is made of seven kinds of thing (the Elements), every agent is built from six kinds of input (the Capacities), and everything is about something (the Themes). That is the whole taxonomy; the rest is detail.

## The eight Scenes — what you’re doing

A Scene is a unique place — a room, a scenario, an area — rendered in Flutter/Flame with its sprites, tiles, and interface elements: a cohesive set of Media connected to the full Kiduna stack. Scenes connect through Portals — that’s how you navigate Scene to Scene. The eight canonical Scenes below are the launch set, one verb each; Builders create more in Studio and the Workbench.

Scene | Verb | What happens there
--- | --- | ---
Atlas | Discover | Explore the space of Realms, inspect anything, join what admits you. Arranged by Gravity — relevance pulls things forward; pan and zoom override. Read-only.
Studio | Create | Give a Realm its character: Wisdom (knowledge), Presence (system prompt), name, original SVG icons and interface elements. Why a veterans Realm feels different from a cricket Realm.
Commons | Organize | People — who to connect with, whose Wisdom to learn from. Scoped to Realms.
Workbench | Build | The maker’s sandbox: implement your own Abilities (and the agents and automations composed from them); hand real code to Claude Code / Codex through the Workbench plugin; connect MCP servers; design your own loops. Safety is Realm containment + the Builder role + inspection, with Sentinels running the acceptance protocol.
Forum | Govern | Proposals, voting, allocating resources. Votes are never weighted by money. Duna token release is a later Forum capability.
Exchange | Settle | Buy Compute; move between $KIDUNA and USDC, wallet to wallet. Simple; duna tokens join when ready.
Garden | Enjoy | Where built things get used — the veteran’s service, the course, the campaign, the rideshare, the tourism guide, the medical navigator, the store. Each app renders its own experience through the composition grammar: ~15 interface primitives, combination rules, a deterministic renderer; launch apps are authored compositions, Ki composes generatively within the grammar later.
Vault | Store | The wallet-shaped Scene: on-ramp, off-ramp, storage — fiat in, $KIDUNA out. Web only.

## The four Surfaces — where you are

A Surface is a form factor, not a product. Every Scene reaches every Surface except Vault (web only). A basic version of all four ships in the initial release — depth varies, presence does not.

- Desktop web — the Field, with Ki beside it. The working distance: density, inspection, governance, commitment.
- Mobile — the human distance: presence, capture, coordination, bounded decisions; Ki as a bottom sheet.
- Chrome Sidebar — the extension: the agentic internet alongside the ordinary one, filtered through Kinship Codes.
- CTV — the connected television: the shared big screen, driven by the mobile devices in the room, several people at once.

Allies are in every view — the people render in every Scene on every Surface; selecting an Ally opens it. The two modes remain Chat and Live on every surface. The official homes (kiduna.app · kiduna.studio · kiduna.express · kiduna.live · kiduna.one · kidunaverse.com) remain the entry points.

## The seven Elements — what things are

Everything in the system is one of these, a property of one, or a composition of them.

1. Realms — what can be entered. The ten canonical types, final: Ecosystem · Organization · Alliance · Program · Project · Relationship · Community · Institution · Concept · Cell — all nested inside Kinship Duna (the Ecosystem), each with full parity of capability.
2. Actors — all agents that are not Allies: Operators, Envoys, Sentinels, Workers, Supervisors, integration Actors, and kinds not yet named. An open-ended class.
3. Media — stable stored content: files, images, video, documents, structures. Some Media feeds the Wisdom vector stores.
4. Allies — the members’ representatives: the Field-visible identity of a person. The Source (the human) stands behind the Ally in the data and governance model.
5. Resources — what things cost and how they’re paid for: Compute, USDC, treasury balances, capacity.
6. Actions — the deterministic, reserved operations intelligence is never allowed to improvise: moving money, issuing tokens, finalizing votes. Typed, named, executed only through the command boundary.
7. Offers — what is put forward for others to take up: goods, services, one-time or subscription. First-class, not a Realm kind.

## The six Capacities — how an agent is built

Each Capacity is a verb and the thing it builds. Together they are the complete recipe for an Ally or Actor.

1. Inform with Wisdom — the vector database: what it knows.
2. Instruct for Presence — the system prompt: how it carries itself.
3. Empower with Connections — integrations: what third-party systems it can reach.
4. Enable with Automations — deep agents and triggers: what it keeps doing without being asked twice.
5. Impart Abilities — skills (markdown-defined know-how): what it knows how to do.
6. Align for Coherence — Sentinels and values: what watches the work and keeps it true.

## The Themes — what things are about

Not an eighth Element: a cross-cutting layer in the Kinship Graph (`hasTheme` on Realms, Allies, Offers). Elements say what a thing is, Capacities what it can do, Themes what it’s about. A fixed spine of 26 themes in 6 clusters (People & Care · Society & Justice · Culture & Play · Place & Planet · Work & Wealth · Knowledge & Frontier), open folksonomy sub-themes beneath, at most three themes per Realm, aggregation up the Realm nesting, and theme-affinity matching so the Graph can route introductions. The full spine is in Taxonomy v1.3.8 §7.

## The connective tissue

- Ki — the one intelligence behind everything; context follows location; speaks in the third person; the orchestration layer, never a character in the Field.
- The Field — the always-present spatial context the Elements render in; with Ki beside it, the whole desktop grammar.
- Gravity — Atlas’s arrangement: orbits of importance, relevance promotion, member override by pan and zoom.
- Portals — how Scenes connect: the navigation from Scene to Scene. Tap to enter; press-and-hold stays reserved for signatures.
- The economic rails — the economy is on the blockchain from day one: FROST wallets for people, Squads wallets for Organizations, Alliances, and Institutions (Communities and Relationships hold none), everything wallet to wallet, orchestrated by agentic AI. No external token platform, no futarchy, no new smart contracts to launch — the orchestration and database layers run the logic over the real wallets. Liquidity is never fragmented: all $KIDUNA at launch, duna tokens when ready. The Agency Premium (duna-set LLM pricing, premium share to treasury, the waterfall) is the engine.
- Equal voting — governance is never weighted by holdings. One member, one weight, everywhere.
- The privacy hierarchy — an item may carry more privacy than its context, never less. Public is only really public in a public Realm; the Realm sets the floor.
- The adoption rule — any Realm adopts what’s public or offered to it, its own choice; when the Ecosystem adopts something through governance, it’s available everywhere. One rule for Abilities, Scenes, sub-themes, and whatever comes.
- Connected, or not present — there is no offline mode; downloads are just downloads.
- Kinship Codes and the Handshake — person-vouched identity: the inviter is the verification; a single-use out-of-band word seals it.
- Compute — prepaid usage credits that power intelligent agents. The thing the $100 buys; the thing organizations spend.

Installed 2026-08-01 with the v1.3.8 amendment. This page is the one-page reading; the taxonomy is the law; the Initial Release Functional Specification is what it means for the build.