# Kidunaverse cofounder skill — canon delta · 2026-07-14 · kiduna.ai, the Genesis bootstrap, trust levels, and the outward stack

**Apply via Settings. Wins with the 2026-07-13 deltas until the fold lands.** Sources: the 7/14 Techneural architecture sync, the Agentic Internet whiteboard, the plug-in architecture brief, and the kiduna.ai launch deck.

## kiduna.ai — the authoritative front door (NEW, supersedes kiduna.cash)

- **kiduna.ai is the authoritative registration site and system for Kinship Duna** — register, create membership, buy Compute. Super simple, deliberately tight. It is also the **launchpad**, the **wallet home**, where all financial stuff lives, and where the member's **third key share** (FROST) is held. One place to manage your wallet — so nobody puts up fake sites and takes people's money.
- Operated **under the auspices of Kinship Duna** — not another company. The IP/stack remains with Kiduna Club (Delaware C Corp).
- Buy Compute for Kinship Duna or for other dunas (Service Alliance, etc.). Accounts can stay anonymous.
- **api.kiduna.ai** is the API home (moving from api.kiduna.club). **mcp.kiduna.ai/mcp** is the MCP server.
- Any website can embed the onboarding flow; it all lands on the same backend.
- Moto's email is now **david@kiduna.ai**.
- *(This absorbs the kiduna.cash concept from 7/13 — the wallet home is kiduna.ai.)*

## The Genesis bootstrap (the canonical order)

1. **Genesis Ecosystem** — "Kiduna," with handle/DID. An ecosystem's genesis sets defaults: lineage payments, the **Agency Multiple** (how much an organization adds in agency over raw intelligence cost — default **7x**), and default Compute. Configurable only on NEW ecosystems, not on the Genesis Ecosystem itself.
2. **Genesis Ally — "Ki"** (handle Ki; display name **Kinship Intelligence**). Holds all system information, Wisdom, connections, databases, interface. Everyone talks to Ki first; Ki greets before you speak. Everything the system can do should be reachable through Ki — **Ki is effectively the initial user interface.** Time to First Value: extremely low. New ecosystems get their own new ally; there can be only one Genesis of everything.
3. **Genesis Account — the "Mage"** (Kiduna_Mage; handle pattern `ecosystem_mage`; admin@kiduna.club). Limited, basic administration. Every future ecosystem has a mage account.
4. **The Mage invites the first member with a Genesis Code.** Order matters — blockchain and protocol require certain things to exist first.
5. Member onboards on any surface (Live, Studio, Express, TV, website) → talks to Ki → may **rename their ally** (example: "Psy") — still the one ally, same agent, with the member's stuff segregated (public/private/secret/personal). The ally takes orders **only from its Source**; all else is context.

## Invitations, codes, and zero spam

- Member says "invite Jeya" → the ally invokes the **Profiler** (an Actor kind) → asks about the relationship, trust level, background → builds the invitee's profile IN ADVANCE so their environment is as well set up as possible on arrival (communities they'd like, the Relationship pre-formed).
- **Person-specific codes: single-use, expire in 15 minutes** (create another later); tell the inviter whether it was accepted. **Generalized codes**: for anyone — no profile, no greeting, **default untrusted**; settable expiration; settable target (invite to a project, an organization, an alliance, or the system).
- **Zero spam is a law: unless someone has a registered account, the system cannot reach out to them.** The inviter sends the invitation out of band (email, text, Telegram) themselves.
- If the invitee already has an account, the invitation **forms a Relationship** (say "form a relationship," never "connect" — connections are a different thing). Verify identity by questions, or an optional **secret passphrase**.
- Code generation moves to agents: a **Code Manager** Actor generates the right code for the right reason for the right person.

## Trust, authority, privacy — the three axes (member-facing)

- **Trust levels: High / Medium / Low**, set per side of a Relationship, stored, and visible between the two. (Low: heard of them, stranger on the internet. Medium: met once or twice. High: I'd let them babysit my kids.) Trust can chain: "I trust them because Jeya trusts them."
- **Authority: registered / unregistered — and registered WITH WHOM**: a DUNA (SoS registry), an Institution through KYC, a **DNS TXT record** for a domain, an **AT Protocol DID**. Who vouches, where it's vouched.
- **Privacy: public / private / secret / personal** (personal never grantable). Wisdom follows the same four levels; private/secret Wisdom needs a code — and members automatically hold the code for what they belong to. Nobody manages keys by hand.
- Plus identity and accountability underneath. These axes are the member-facing trust grammar of the whole system.

## Permissions grammar (HITL)

Human-in-the-loop actions ask the first time, in dialogue: "I'm asking your permission this time — in the future, ask, or just do it?" Then an **Action button** appears in the Field: **Allow once / Allow every time.** Every action type gets this treatment; the member can set don't-ask per action. The **Sentinel** keeps the field clean — if something is awry it always comes in and asks explicit permission ("do you want to be abused and manipulated?"); asking never completely stops an action; it can escalate to a specific human or type of human.

## Agents (confirmed + refined)

Two families reaffirmed: **Allies** (one per member, Source-directed) and **Actors** (everything else — "actors, not performers"). The ally is the **supervisor**: when you say what you want, your ally invokes Actor agents to get the work done. First named Actor kinds: **Profiler**, **Project Creator**, **Code Manager**. Inside every organization/community/alliance there are agents that know what's possible there — each has its **list of actions** (the graph's strongly typed actions registry: what's possible, who took what).

## Guest tier (economics)

- Membership stays $100. **Guests: minimum $10**, compute at **2x the member price**. Buy more than $100 if you want; volume tiers possible (buy a real lot, pay less). All under counsel's consumption vocabulary.

## The kiduna.md loop + outward stack

- **kiduna.md** joins CLAUDE.md / AGENTS.md as a first-class convention: the system looks for kiduna.md files first; they can carry codes that OpenAI/Claude validate over the network — a trusted loop. Ask Gemini and other major systems to support the protocol.
- The outward stack (API api.kiduna.ai · MCP mcp.kiduna.ai · two-platform plug-in monorepo · eight skills · four specialists) is specified on the Integrations track §8. **The MCP server is a client of the Graph Command Service, never a second boundary.**

## Launch posture

- The launch deck "The Agentic Internet Starts Here" (kiduna.ai) is published on the team site. Featured spin-outs: The Fellowship of Play (Dave & Susan Thompson, Morgantown — tabletop games, played together) · Service Alliance (Matt Simon, Shepherdstown — veterans, serving veterans) · Mountain River Trail (Rob Dobson & Crystal Stone, statewide — concierge travel across West Virginia). **August 10–11, Charleston, WV.**
- Front end: **100% rewrite** around the Ki-first conversational flow; Sucil drafting flows from the 7/14 conversation; David sending the new design.
- ⚠ Legal watch (L-18): the deck line "Compute can passively gain in value" and "launchpad" vocabulary need a counsel pass before wide distribution.

## Addendum, same day · Graph Architecture v1.1 RATIFIED (replaces v1.0)

**The human-state vocabulary changes** (supersedes v1.0's "Member everywhere"): **Persona** = the durable human identity behind an Account, the Source of an Ally — the generic term. **Visitor** = unauthenticated/unidentified. **Guest** = authenticated Persona not admitted as a Member of the Organization in context. **Member** = a Persona with an active, LEGALLY EFFECTIVE Membership in that Organization — `Membership` is the authority-bearing object; account creation or payment alone never creates it. A Persona can be a Member of one Organization and a Guest of another. (Public copy still never says "user.")

**The twelve owner ratifications, in force:** 1 the human states above · 2 restrictive Guest/Public allowlist at launch, expanded only via versioned command-registry change · 3 Institution = first-class OUTSIDE legal principal (agreements, delegates, wallets, verification, authority chain, optional lineage) — never pretend it's a Persona or Organization · 4 one eligible Member, one equal ballot; decision-market positions are information only · 5 every DomainCommand declares exactly one authority class from the machine-readable registry · 6 transferable/DEX Compute, market positions, lineage payouts, Curator allocation, Sponsor distribution each independently gated until legal/accounting/tax/custody/rails review · 7 missing lineage skips up to the next qualified ancestor, then the named treasury/reserve — never fabricate an ancestor · 8 the 20% liquidity share is a default minimum in versioned Organization policy, not a protocol invariant · 9 agency pricing: simple disclosed schedule, maximum markup, line-item receipt — Kinship defaults 7x for Members, 2x the Member charge for Guests · 10 the legal adapter continuously verifies ID/jurisdiction/standing/100-member requirement/next review · 11 every portable identity has one authoritative Home Ecosystem; migration preserves permanent ID and history · 12 the August 10 packages freeze: regulated finance, securities, lending, custody, payroll, investment advice, insurance, clinical, and autonomous legal effects stay Preview or Disabled.

Profiler and CodeManager are now typed Actor kinds in the spec. Minimum Action catalog published (Appendix A). Site page, PDF, figures, and kit updated to v1.1; v1.0 removed.

## Status

Recorded 2026-07-14 (v1.1 addendum same day). Wins over the tracks until the fold.
