Kiduna Kit · v4.3 Created 2026-08-01 · 23:10 EDT

For anyone who wants to participate. The complete spec — all eleven tracks, canon, architecture, every design round, queues, the versions record — packaged to work directly with Claude, ChatGPT, Cowork, Claude Code, and Codex. Unzip it, point your assistant at it, and start creating from within.

Start here: the Genesis Nightpaper v0.3 · the Kiduna Kit (the button) · the Technical Specification · the Technical White Paper · the Kiduna Canon (the whole canon in one standalone document — read this first) · the Core Taxonomy v1.3.8 (the law behind it) and its one-page summary · the Initial Release Functional Specification v2.0 (what the first release does, Scene by Scene and Surface by Surface) · the Studio + Live Working Design Brief (the design record behind the two working distances — read through v1.3.8, which rules that framing historical) · the Studio Enamel Design Canon (live studio design system) · the Kinship Graph Architecture v1.1 — the operating graph, spec of record for the build. Everything else on this site backs them up.

Register: kiduna.ai — the authoritative registration system for Kinship Duna: create your membership, buy Compute, hold your wallet (and your third key share). One front door, under Kinship Duna's auspices — if it isn't kiduna.ai, it isn't us. The launch deck: The Agentic Internet Starts Here (PDF).

Download the package ↓Join early access →Check out the Studio Design System →Read the nightpaper →

## What we're building, plainly

We are building the agentic internet: a layer on the whole internet where people are represented by intelligent agents, organizations are internet-native and member-owned, and every action — a message, a decision, a payment — resolves to a legally accountable entity. Kiduna is that layer's namespace and its home. It is owned and operated by Kinship Duna, the genesis organization: a legally real West Virginia DUNA whose purpose is to build this technology, spin out other organizations, and train members to thrive in an agentic economy. Genesis means first, not in charge — the system is decentralized and permissionless, every organization has equal power, and the only central registry anywhere is the WV Secretary of State.

The product is a relationship, not an app to operate. Every member has one ally — their agent, named by them, working for them across every organization they join. You talk to it, by text or by voice; it does the work: it messages, researches, schedules, moderates, drafts, negotiates with other members' allies, and brings back the few things only you can sign. There are no menus. The interface is one conversation (Chat) plus one graphic world (Live) — and everything either surface shows is the same underlying system rendered two ways. It reaches you through six surfaces: Kiduna (the app — the first KAP client), Kiduna Live and Kiduna One (each mode whole), Kiduna Express (the browser), the account (kidunaverse.com), and Kiduna Studio (the build/create environment). Underneath: an installable open-source server — one installation is an ecosystem, the Genesis Ecosystem is Kiduna, and its purpose is to propagate.

The application has eight places to be. Whatever a member is doing, they are in one of eight Scenes, each one verb long: Atlas (discover — the whole space of organizations and communities, arranged by relevance, read-only), Studio (create — where a Realm gets its knowledge, its voice, its name and its icons), Commons (organize — people, relationships, collaboration), Workbench (build — the maker's sandbox, where members write their own agents and automations and hand real work to coding agents), Forum (govern — proposals, votes, allocation; every member's vote weighs the same, never money-weighted), Exchange (settle — Compute, and moving between $KIDUNA and USDC), Garden (enjoy — where everything the members build actually gets used), and Vault (store — the wallet, on the web only). A Scene is a real place — a room, a scenario, an area, drawn with its own sprites and tiles — and Scenes connect through Portals; Builders make their own and deploy them into the Garden. A Surface is a form factor, not a product: desktop web, mobile, the Chrome sidebar, and the connected TV — the shared screen the phones in the room drive. All four ship in the first release; every Scene reaches every Surface except the Vault. And everything in the system is about something: Themes — a fixed spine of twenty-six, at most three to a Realm — are how the Atlas arranges itself and how the graph knows which organizations belong together.

All of it is written down in one place. The Kiduna Canon is the whole thing as a single standalone document — the eight Scenes, the four Surfaces, the six Capacities, the seven Elements, the ten Realm types, the twenty-six Themes, and the rules that bind them: the command boundary, person-vouched identity, the economic rails, the privacy hierarchy, the adoption rule. Read it end to end and you know what Kiduna is. What the first release must actually do — Scene by Scene, Surface by Surface — is the Initial Release Functional Specification. The Core Taxonomy remains the law behind both, and the summary is the one-page reading of it.

Underneath, it is one big system. Allies appear separate but are personas of a single agent system with a single context store. Everything anyone adds — information, tools, skills, made things — exists once, available across the whole system at the root, gated only by four access levels: public (anyone), private (visible, permission required), secret (undiscoverable without a code), personal (you and your ally only, ever). Relationships between members are first-class: when you connect with someone, each of you states exactly what the other may see and use. Boundaries in this system are not walls; they are stated levels of trust, enforced by the database on every single command.

The organizations are real. Thirty-one DUNAs are already filed — a health community, a law firm, a mutual insurer, a solar collective, festivals, a dating organization, mutual-aid networks — each a legal entity, each a configuration of the same platform. Members join a duna with its initial Compute purchase ($100, lifetime, for Kinship Duna — each duna sets its own), hold one wallet, and move freely among them; alliances form inside them with shared wallets; guilds form anywhere with nothing but a name. Decisions happen in Forums, where every member votes with one equal, free token, and a passed proposal executes its duna commands — real organizational actions, atomically. Deciding is never fundraising.

Money is deliberately boring and deliberately minimal. Everything financial lives on a small web surface (never in the mobile app), and only six things ever touch the blockchain: members, their allies, alliances, organizations, Compute, and votes with their settlements. That short list is the Kinship Agency Protocol, and it exists for one reason — so it is always provable who ordered a thing, who paid for it, and under whose responsibility it happened. Everything else stays off-chain, where it belongs.

And it learns by playing. Live's first product is Kidunaversity, a Move: training regimens for operating in an agentic world — guiding your ally, forming alliances, running Forums — where everything is real except the money, which is fake by construction. New members learn the system the way people actually learn: by doing it where mistakes are free.

How the pieces fit — follow one act through the system A member speaks to their ally in Chat → the one agent system routes, weights, and acts → every read and write is permission-checked against the graph → if money moves or a vote settles, it is recorded by the protocol → always inside an organization that is legally accountable → through a registered action → gated by the member's role → while the Sentinel quietly keeps the field healthy.

## Why it is built this way

The public statement of the whole system is four principles — human direction · agentic capacity · personal privacy · legal standing — and they are what kiduna.ai promises the world: not another AI tool; a place to build and belong. The internet connected pages; social connected profiles; Kiduna connects allies — people and their intelligent allies in trusted relationships, where shared purpose becomes projects, movements, organizations, and action. The system is organized around agency: sense, decide, act, learn ; it succeeds when increased collective capacity makes every participant more capable, without absorbing authorship, collapsing privacy, or silently centralizing authority (the Genesis Nightpaper makes the full argument).

Three commitments explain nearly every design decision on this site. Agents do the work; people do the deciding. That is why there are no menus, why awareness arrives as a told account instead of a feed, and why the few sovereign acts — votes, codes, signatures — are deliberately physical. Accountability over control. That is why organizations are legal DUNAs, why the protocol is minimal, and why a domain, page, or artifact bound to the registry is called registered — traceable to a member and a legal entity — rather than "trusted": we claim only what the mechanism proves. One system, stated trust. That is why there is one context store with four access levels instead of walled gardens, why allies are personas instead of separate agents, and why a member's "that's secret now" binds everything instantly.

We build Kiduna from the inside out. This team works the way the product says members will: with our own allies, forming our own alliances, spinning out our own organizations. If this spec describes something we wouldn't live in ourselves, the spec is wrong.
— Moto, Kinship Duna
The specification — eleven tracks, start anywhere
Track 1

### Surfaces

The six surfaces: Kiduna (Chat and Live), Kiduna Live, Kiduna One, Kiduna Express, the account and protocol browser (kidunaverse.com), Kiduna Studio (+ kiduna.studio) — one system, four renderings, and the complete UI design (§8).

Start here: everyone · mobile/Flutter builders · design Track 2

### Orchestration

The middle tier: one agent system wearing personas, weighted listening, one presence per channel, primitives carrying skills, contextual actions.

Start here: agent/LangGraph builders Track 3

### Foundation

The data architecture: the graph as the center, the primary nodes, the four access levels, connections and grants, memory, what the database holds about money.

Start here: Jeya & the back-end build Track 4

### Protocol

The on-chain minimum: wallets, ally NFTs, alliances, Org-ID-validated DUNAs, Compute, votes with settlement; duna commands; the decentralized registry — domains, pages, and artifacts registered via DNS, codes, and hashes.

Start here: chain/wallet builders · legal Track 5

### Organizations

The 31 filed DUNAs and their purposes; the variance analysis — what actually differs between organizations; the genesis duna stated precisely.

Start here: anyone configuring a duna · partners Track 6

### Actions

The baseline inventory of everything a member can do, on both surfaces, role-gated and graph-indexed — plus the rule for registering new actions.

Start here: mobile builders · QA · anyone wiring features Track 7

### Roles

The nine ways people relate to an organization — Guest through Luminary, and Institutions — with the first Catalysts, Luminaries, and Institutions named.

Start here: onboarding · community · legal Track 8

### Sentinel

Interaction health: seven bipolar meters where zero is health, graduated correction toward the zero point, and hard human-in-the-loop boundaries. Members see effects, never meters.

Start here: agent builders · safety · community stewards Track 9

### Legal

The legal posture: counsel's seven resolutions in force, in priority order — securities messaging, money movement, organizer compensation — plus the open work (ToS, privacy, IP licensing, fiscal sponsorship, patents). Held for final review.

Start here: counsel · anyone writing public copy · partners Track 10

### Institutions

The outside entities with standing inside: KII (kinship.institute) holds purpose, Kinship Systems (kinship.systems) holds labor, Kiduna Club (kinship.club) holds property — and the launch cohort begins inside Kiduna Club.

Start here: partners · sponsors · counsel Track 11

### Integrations

Inward: MCP servers, APIs, and local agents (Cowork, Codex) scoped to relationships, alliances, and organizations. Outward: our own API and MCP server — build on Kiduna with no privileged path.

Start here: Builders · third-party developers
Get involved — regardless of role

This project needs more than engineers. It needs people who can write, draw, organize, teach, argue, host, and hold a community together — that's most of what an internet is. If you code, start with Architecture Prototype Design and Foundation. If you make things, start with Surfaces and the current design round. If you organize people, start with Roles and the 31 organizations — one of them is probably yours. If you honestly don't know yet, read How We Build and take the Kit: unzip it, hand it to whatever AI you already use, and ask it anything about the project. That's not a gimmick — it's the method. We build with our own tools, in the open, and the door is the work itself.

Downloads — work without reading the site

### The Kiduna Kit · updated daily

- Kiduna Kit v4.3 · 2026-08-01 — for anyone who wants to participate: the complete archive of everything across the entire effort — all eleven tracks, the engineering architecture, the complete UI design (viewable offline), narrative canon, the versions record, queues, and skill updates. Works with Claude, ChatGPT, Cowork, Claude Code, and Codex: chat assistants get a one-file spec (KIDUNAVERSE-COMPLETE.md) plus paste-able instructions; coding agents orient from CLAUDE.md / AGENTS.md. It answers from the spec and never invents.

### Role packages · updated when needed

- One per role, self-orienting: Builder · Creator · Organizer · Catalyst · Luminary · Institution · Founder · Member · Guest

Deeper reading & the record

### Narrative canon

- Real Work, Real Money — how people collaborate, get paid, and build practices here, in plain language. The best first read for any newcomer.
- The Working Organization — the long-form case for the agentic shift, with four organizations worked in narrative detail.
- Kiduna-Architecture — the engineering draft of the graph-native architecture.

### The record

- Versions — how this spec evolved, every prior version preserved. Design exploration history (paradigm rounds 1–4) lives there too; the current design is linked from Surfaces §8.
- Open Questions — the standing decision queue, each item with its full context and links into the spec.