# Kidunaverse cofounder skill — canon delta · 2026-07-17 · THE CORE TAXONOMY REBUILD

**Apply via Settings. This is the major refinement — it wins over ALL earlier deltas and tracks where they conflict. Site page: taxonomy.html.**

## The frame

Moto rebuilt the taxonomy because "it wasn't working." The primary elements: **Principals · Privacy · Media · Attributes · Status · Agents · Trust · Actions · Roles · Offerings · Compute.** "If we get these right, we've won."

## Principals (replaces "containers"; the first-class nodes)

Member · Organization (DUNA, must have an Org ID) · Alliance · Community · Institution · Relationship · Forum · Ecosystem.
**Containment rules:** Alliances and Communities are ALWAYS inside a duna (they derive legal standing from it). Institutions and Members are NEVER inside a duna — own legal standing; they move between and join/sponsor. Relationships are only between members. Forums are principals within dunas.
**Institution specifics:** offline entity; special case of Alliance; Squads wallet; **standing** (bylaws/documentation linked to the registering government agency) + a **designate** (accountable human) + address; **sponsor is the canonical verb** (sponsors members, alliances, dunas; pays Compute and memberships; contracts); cannot vote.
**Relationship:** node AND primary edge; holds its own Wisdom, Stance, agents, media ("a marriage is a relationship that's basically an institution").

## Privacy — ALWAYS for a principal

Public / Private / Secret / Personal. A privacy level must name its principal(s); one item can be private for several at once. Private = discoverable metadata, gated access. Secret = unindexed, no metadata, ally won't reveal existence. Personal = one member's vault forever, scriptable release (dead-man switch). Container privacy and content privacy are independent. **Codes (JWT) are the infrastructure that implements this** — claims unlock principals; invitation codes = cryptographic membership of the privacy system.

## Media

Everything is media. **Engines (active): Wisdom (vector DB — never "knowledge base") · Stances (system prompts) · Abilities (= the world's "skills"; our word is Abilities).** **Artifacts (passive):** audio/video/documents/images/files. **Origins: generated · imported · verified (hash provenance; institutions should register domains) · external.**

## Attributes + verbs (updates the 7/13 mapping)

Every principal: name · handle · description · **Wisdom informs · Stance instructs · Abilities enable · Automations trigger · Connections empower.** (Connections = outside accounts, MCP servers, APIs.)

## Status

Draft · Published · Registered (registered = formal only). DUNA lifecycle: **draft → registered → launched → active.** Status ≠ privacy; non-sequential states.

## Agents

Two families, asymmetric strictness: **Allies strictly defined** (one per person, Source-only instruction — the anti-prompt-injection core). **Actors deliberately open**: envoys, operators, sentinels, workers, supervisors, integration/research/payment agents, anything people build — governed by permissions and trust, not taxonomy.

## Trust

**High / Medium / Low, DEFAULT LOW.** Attaches to anything (agents, accounts, wisdom, institutions, media). Calibrates inspection intensity. Never a permanent unified reputation score. Misinformation strategy: provenance + circles of trust, not moderation — every element traces to its poster; "it's not for us to determine"; your ally answers from what you trust and belong to.

## Actions

First-class, deterministic, typed, enumerated per agent, permission embedded in the action (permissionless / tap / slider / press-and-hold; defaults; overrides). Verb list being extracted from the Studio codebase; **"seeking" not "searching."**

## Roles (not principals; exist so proposals can name and pay)

Visitor · Guest (Agency Premium can differ by role) · Member · Creator (adds media) · Builder (writes code, modifies agents) · **Founders = first 100 members of a duna, automatic (WV rule)** · Catalyst (created the principal) · Luminary (named for contributed body of work).

## Offerings + Compute economics (REVISES earlier defaults)

Offerings: digital/physical · one-time / subscription / held-Compute eligibility.
Compute: every duna's own; duna sets membership amount (one-time / subscription / balance), launchpad min/max, activation threshold, and the **Agency Premium** (renames "agency multiple"/7x-markup; multiple OR additive; per-role).
**Compute-purchase distribution default: 30% lineage (20/5/3/2) + 1% to Kinship Duna + remainder (~69%) to the duna's treasury** — overridable at setup, changeable by vote. Lineage is per-duna (restarts per duna's invites). Treasury sets a monthly catalyst amount. *(Note: this is the per-purchase rule; the founding-round close waterfall 20/30/50 is a separate, earlier structure. The 1%-to-Kinship-Duna vs the Kiduna Club 20%-of-treasury-inflows licensing needs reconciliation — open item.)*

## Governance ruling (resolves the tension for now)

Launch **as-is on the futarchy machinery**: members CAN create proposals by staking Compute (anti-spam stake, returned at market open); pass/fail positions trade in USDC; renamed **Forums** everywhere; set limits. Long-term explicitly unsettled: BonkDAO's ~$20M governance attack is the cautionary case; the owner's principle is equal member say; post-launch, rework or replace (possibly fork), decision markets optional. This supersedes nothing in v1.1's one-Member-one-ballot *principle* — it is the pragmatic launch posture.

## Directives to Techneural (working state)

Graph DB must be rebuilt around the principals + privacy-for-a-principal model (not per-user "what do I have"); conversation memory moving to graph; demo = talk to Genesis ally Ki (wisdom + stance + abilities loaded), full action list extracted from the codebase; market→forum rename now; Aashik to hand over the HTML screens in Git so David can rework them in kiduna.design.

## Open conflicts recorded (for Moto)

1. Relationship: exactly-2-members (spoken ruling, prior canon) vs "two or more principals" (whiteboard/structured doc). Recorded as exactly two.
2. Community: always-inside-a-duna (spoken) vs "within or across organizations" (structured doc). Recorded as inside.
3. "Principals" spelling adopted (structured doc) over transcript's "principles."
4. 1% Kinship Duna vs Kiduna Club 20% licensing — reconcile.
5. Founders "first 100" (7/17) vs "first 1,000 recognition cap" (earlier founding-round canon) — reconcile.

## EVENING · Core Taxonomy v2.0 (revised edition) — RESOLVES the morning's conflicts

Moto's revised document (downloads/canonical-taxonomy-v1.3.3.md, included as-is) is the document of record and settles the recorded conflicts:

1. **Relationship = a persistent connection between TWO OR MORE Principals** (supersedes exactly-two) — may exist within, across, or OUTSIDE Organizations/Alliances/Communities/Projects; may itself be the context for Agents, Artifacts, Actions.
2. **Alliance and Community: inside an Organization "in the current model"** — confirmed, with the hedge recorded.
3. **Projects ARE Principals** — goal-oriented, durable identity, delegated authority, may hold Agents/Resources/members/budgets/subprojects; no separate legal standing; may begin without a Wallet. (Closes the "Projects under-specified as a node" issue at the taxonomy level.)
4. **Resources are a core category; Wallets are Resources** — owner/beneficiary/controller/custodian distinguished; three wallet types (external single-sig · FROST personal, shares split server/client/recovery · Squad multisig for DUNA treasuries, Alliances, Institutions); security invariant: possession of a connection/address/device/session/key share never establishes authority.
5. **Personal is a rights DIMENSION, not a fourth exclusive level** — personal information may itself be public, private, or secret; separate fields (classification · owner/subject · access policy · permitted uses · retention · disclosure). Secret is redefined toward elevated-protection material (keys, FROST shares, credentials).
6. **Verified is a verification state, not an artifact origin** (origins: Generated · Imported · External).
7. **Five action authorization levels are canon: Autonomous · Confirmed · Deliberate · Governed · Prohibited.** Permission attaches to the full combination; press-and-hold is an interface, not the permission.
8. **Ally delegation nuance**: others cannot direct an Ally "unless the Member has explicitly delegated limited authority" — the Source rule with an explicit, bounded delegation door.
9. **Institution nuance**: may operate inside an Organization and may be OWNED by one, but never owns an Organization as institutional parent.
10. **Protocol licensing = two distinct rules paid to Kiduna Club**: a defined portion of Agency Premium (stack use) + a defined portion of Compute purchases (protocol/infrastructure licensing). Purchase-distribution recipients: lineage, Kiduna Club licensing, treasury, Project budgets, liquidity, contributors, sponsors — protocol default supplied, org-changeable. (The transcript's "1% to Kinship Duna" is recorded as the current commons default; the licensing recipient per the document is Kiduna Club — confirm the entity in one line when convenient.)
11. **Lineage is per-Organization** — no universal relationship across the Kidunaverse. Catalyst/Luminary/Builder/Creator/Operator are compensation classifications.
12. **Nesting = typed containment, never implied ownership/custody/governance.** Core modeling rules adopted verbatim (see the page).

Still open after v2.0: Founders first-100 vs first-1,000 recognition; trust-level visibility; R8's five rulings; long-term governance mechanism; the action verb inventory extraction; Graph Architecture v1.2 fold; member-state vocabulary (Persona/Visitor/Guest from v1.1) vs v2.0's simple "Member" — v1.1 still governs the schema until the fold.

## 2026-07-18 · Programs join the Principals

**Program** — a large-scale, sustained initiative of an Organization; a Principal containing multiple Projects, Alliances, Communities, Relationships, Agents, Resources, Artifacts. Project delivers a defined outcome; Program carries a mission across many outcomes. Authority originates from the Organization and delegates onward; own governance/budgets/policies/Squad wallet permitted under the Organization's rules. Programs live inside Organizations; Projects may nest inside Programs or directly under any authorizing Principal. (Owner addition, 2026-07-18; extends v2.0 — the v2.0 PDF remains as-is, this delta and taxonomy.html carry the extension.)