# Kidunaverse cofounder skill — canon delta · 2026-07-11 (SUPERSEDES conflicting earlier canon)

**Apply via Settings. This is the "getting serious about building from within" restatement — the product lineup, hierarchy, and vocabulary below win over anything earlier that conflicts.**

## The products (the lineup)

1. **Kiduna Server** — anyone installs one and connects it to the network. Contains the foundation layer, orchestration layer, and the protocol. Any client connects to any server; all servers join the network through the protocol. Accounts live on the network, never on one server; resources are always protected by the four levels (public/private/secret/personal). **It's a mesh** — you install a server to *contribute*, not to separate, and you can be paid for hosting a duna's resources through a duna agreement. A server is an **ecosystem**.
2. **Kiduna Protocol** — keeps the primitives on the blockchain via **Solana programs**: addresses + the decentralized registry; permissionless, composable, decentralized. Bridges the blockchain and agentic worlds (accountability, identity). **Bridges AT Protocol ↔ Kiduna ↔ blockchain using DIDs.** **Extends MetaDAO** — more voting types recorded on-chain. Should be **a single Solana program** interoperating with the others (MetaDAO, Token-22). **NFTs are not necessarily needed** — what's needed is a registry and clarity about relationships.
3. **The Network** — the instantiation of the Kiduna Protocol; where everything composes; it connects ecosystems.
4. **Kiduna Live** — THE end-user app: **mobile first, then CTV, then MR/VR/XR**. Always a single surface: **the Field** with **chat overlaid as part of the HUD** (very flexible, contextual HUD). Live allows Field-only, Chat-only, or blends (overlay or side-by-side).
5. **Kiduna Studio** — has both Field and Chat. Upload things, work on **Projects**, connect to Claude Code/Codex, pass work with trusted others — collaborate on each other's computers, send files, sync — all through the server.
6. **Kiduna Express** — the Chrome plugin.

## New canon vocabulary

- **The Field** — the entire range of play: the whole isometric environment (supersedes "Live" as the environment name; "Live" is now the app's name). The Field can be metaphorical space (containers of artifacts and actions) or real space (AR).
- **Scenes** — discrete, bounded environments inside the Field. Three production grades: nicely designed and uploaded via Studio · rapidly designed with generative multimodal AI · designed on the fly (words/pixels, low fidelity but representative).
- **ACTIONS** — a first-class concept: they appear in the Field or in Chat whenever action is required.
- **Projects** — NEW primitive, within Organizations, living in Studio: they connect tools, agents, software systems; they interact with Claude Code and Codex; **the central organizing principle of Studio.**
- **Mage** — an ecosystem's **genesis account**, which admins all accounts below it. The **genesis Ally** (Ki) provides all initial configuration.
- **Ecosystems spawn ecosystems:** a new genesis account requires a code sent from another genesis account — that's what keeps the network coherent. Ecosystems can also exchange/relate.
- **The trust matrix:** ecosystem relationships are **trusted or untrusted**; resources/entities are **registered or unregistered** → four quadrants (trusted/registered · untrusted/registered · trusted/unregistered · untrusted/unregistered). ("Trusted" returns as a *relationship* property between ecosystems/parties — the old rule stands that registration alone is never rendered as "trusted.")

## The hierarchy (restated)

Network → **Ecosystem** (a server; Mage + genesis Ally) → **Organization** (always a registered DUNA with a WV SoS Org ID; an agent checks/updates registration daily and connects with the registered agent) → within Orgs: **Policies** (enacted proposals), **Forums** (markets), **Compute** (issued by the org) — all recorded/discoverable on-chain — and **Projects** (in Studio). Then: **Alliance** (Squads wallet; each connection is the member's FROST wallet) · **Guild** (informal group) · **Relationship** (between 2 people; the trust matrix applies) · **Ally** (the personal agentic space of a Member) · **Member — the real central organizing principle.**

## Membership and roles

Everyone with an account is always a member of the network as a whole — **always a member of the Genesis Duna (Kinship Duna)**, which provides their overall registration on the network: how they can be reached, how they're accountable, how they can complain. Roles (within specific kidunas): **visitor** (browsing, no account — NEW) · **guest** (no ally of their own; the basic **Host** ally guides all guests) · member · founder · organizer · creator · builder · **catalyst** (Matt Simon — Service Alliance; **Mama Ayo — Black Love**, restored to Catalyst) · luminary (Teich — Cosmic Humanity; Four Arrows; Renée Smith; Thatcher; Narvaez) · **institution** (brought in by a member; a special case of Alliance because it's "real" — **can have KYB**).

## Evening additions (2026-07-11, later — these win over the morning entries where they conflict)

- **THE FIELD IS THE ONLY INTERFACE.** There is no "Field and Chat" split — chat lives inside the Field's **contextual HUD**, which can become **opaque** when the user wants to focus on an action or a chat. This supersedes "Field-only / Chat-only / blend" and the old Chat/Live mode pair entirely: one interface, the Field, everywhere.
- **Everything the end-user needs is represented in the Field.** Information, tools, feeds, artifacts — all of it has a place: a box full of Bluesky posts is a box in the Field.
- **Studio has the same UX as Live — the Field.** Studio is where everything gets entered, uploaded, and defined; it runs on your computer with access to your files and to other tools and systems — Claude Code, Codex, Google Docs, Meet, and anything else you connect.
- **Two agent types, refined:** **Allies** represent members, are guided by members, and support members. **Actors** don't represent members and aren't controlled by members — they have functions. There can be many kinds of Actors, with all kinds of purposes, and **Builders and Creators can name their own Actor types.**

## Status

Recorded 2026-07-11 from Moto's restatement + Techneural call + "Building from the Inside Out" deck (on file). The full track-by-track fold into the spec (Surfaces, Protocol, Foundation, Orchestration, Roles) is queued — this file wins over the tracks until that fold lands.
