# Kidunaverse cofounder skill — canon delta · 2026-07-20 · Dunaversity first; one token

**Apply via Settings. Launch-plan change from the 7/20 Techneural sync + Moto's whiteboard/notes. Planning in progress — the Dunaversity spec is being developed step-by-step with Moto; artifacts will land in a dunaversity/ section.**

## The new launch plan

- **Dunaversity is the first Organization launched on the platform** — the first duna, the bounded proof of concept, target release **end of week (July 25–27)**. Everyone joins Dunaversity; everything else you sign up for and get entry when it launches.
- **One token at launch: $KIDUNA — one launchpad.** All organizations use it; the launchpad sells $KIDUNA and creates more at the current market price when it launches. Rationale: prevent liquidity fragmentation. ⚠ This DEFERS per-Realm Compute issuance (Taxonomy §20) — record as launch simplification, not taxonomy change. ⚠ Counsel watch: a single cross-org token strengthens the "general currency" reading vs org-scoped prepaid usage credits; fold into L-15/L-18 review.
- **Governance at launch**: for any forum/proposal/vote, everyone gets 1,000 tokens to trade when the market opens, and at the end there's no real value — nobody needs to buy or sell. (Whether these are $KIDUNA or a separate valueless voting credit: OPEN, being decided with Moto now.)
- **Studio is for creating Courses; Live is for Learning** — the two-surface launch story, PC/Mac/Chromebook + mobile, all Flutter/Flame.
- **A Course is a Realm** — Moto's direction: the "Program" Realm type (v1.3.3 lists Program under Other Realm Types and flags first-class promotion as unresolved — Dunaversity likely forces v1.3.4: Taxonomy updated, pending Moto's confirmation). Within a Course: Projects, Communities (cohorts). Everyone is a Creator; must NOT devolve into the western/industrial-age educational framework.
- **Three pathway courses**: David — "Mastering Agency: How to free yourself from time, space, and the death-grip of global civilization" (technology, governance, culture, finance) · Aashik — Cricket ("How to be a fan" — the engineering pilot content) · Matt — Military History (contribution-heavy: lived testimony, e.g. the last major tank battle of the Gulf War).
- **Genesis needs**: genesis vector namespace/Wisdom (public metadata so people can find things; public/private distinction), genesis system prompt, course-running agents, badges (completion records), payment on tokens consumed in courses, **Sentinels** checking emotion, content quality, technology quality, safety.
- Roles at launch: Creators, Catalysts, Luminaries — "very specific in function."
- 7/20 action items: Aashik+Jeya release plan; David Design Lab screens + cricket sample courses; kits/Design Lab remain the design-communication channel.

## Working method (agreed with Moto)

Step-by-step co-founder sessions: process → decide gating questions → spine doc → three creation pathways → consumption flow + economics walk → themes/epics/stories with engineering notes → agent roster + genesis package → marketing/tagline → assembled Dunaversity Launch Kit. One artifact per sitting, nothing proceeds unapproved.

## Step-0 rulings (Moto, 2026-07-20, in session)

1. **Governance voting tokens are a SEPARATE VALUELESS CREDIT**, never $KIDUNA (the ratified "Practice Credits" name is available). 1,000 per Presence per forum/proposal; no value at close.
2. **THE ECONOMIC FUNDAMENTALS (say it exactly this way):** $KIDUNA is used for Compute, period — nobody "spends $KIDUNA in a course"; Compute feeds the LLMs (some in learning, some in course development, some elsewhere). **USDC paid for Compute goes to the Duna treasury.** Fixed and unchangeable: **30% of initial purchases to organizers (18% on ongoing purchases)** · **1% to Kiduna Club** [⚠ Moto's same answer later says "5% to kiduna can't be changed" — CONFIRM 1% vs 5% and the recipient entity] · **a Catalyst-set monthly admin minimum to the Duna** (set without vote, unchangeable by vote). Everything else: member-governed treasury.
3. **Default treasury distribution (until voted otherwise): to Programs (courses) pro-rata by Compute consumed in them** — counting both the Catalyst's development Compute and learners' Compute. The Program Catalyst is first PAID BACK development spend, then chooses distribution: FROST personal wallet, or a Squad wallet with rules and votes. (David's Mastering Agency: keep some, distribute to the Luminaries whose materials he uses.) Votes can change the default and can issue $KIDUNA for specific purposes.
4. **Launch reality: everything REAL, all USDC — $KIDUNA is not yet issued.** Membership = **100 USDC**, distributed and used per the rules above; the system runs on USDC until the launchpad raise issues $KIDUNA. **Raise range stated: $100,000 minimum to $10M** [⚠ earlier canon capped the founding round at $1M — the $10M ceiling is back; flag for one-line confirmation and for counsel].
5. **Contribution validation: acceptance + provenance.** No credential gates; contributions are attributed Wisdom, private-for-the-Program by default; the Catalyst (or delegated role) accepts into the course's authoritative record; trust evidence rides along; wider sharing requires contributor consent (personal is a rights dimension).
6. **Program Realm promotion to first-class**: implied by "the Course is a Program Realm" — taxonomy v1.3.4 one-liner pending Moto's explicit confirmation (taxonomy impact rule).

## Step-0 flags RESOLVED (Moto, 2026-07-20, second pass) — NETWORK CANON, not Dunaversity-only

1. **Kiduna Club license = 3% of Compute purchases, unchangeable.** Recipient: **Kiduna Club, the Delaware C Corp** — it owns the IP and licenses it to all Dunas. (Replaces both the "1%" and "5%" figures from the earlier answer, and supersedes the old 20%-of-monthly-treasury-inflows framing as the launch rule; the two-rule structure from Taxonomy §20.4 — premium portion + purchase portion — remains available, with 3%-of-purchases the number in force.)
2. **The launchpad raise: $100K minimum, $1M maximum.** ($10M was a slip; the July 4 cap stands.)
3. **LINEAGE, THE PERMANENT NETWORK RULE (applies to every Duna):**
   - **Initial membership purchase: 30% lineage distribution** — Gen 1 20% · Gen 2 5% · Gen 3 3% · Gen 4 2%. [Moto's note wrote "4% gen 4," which sums to 32%; recorded as 2% to match the stated 30% total and all prior canon — flag if 4% was intended.]
   - **All future Compute purchases: 18% lifetime lineage distribution** — Gen 1 12% · Gen 2 3% · Gen 3 2% · Gen 4 1%. Rationale (Moto): high enough to keep organizers meaningfully invested; clearly distinct from the 30% membership reward; the first-line organizer earns a meaningful 12% for the member's lifetime.
   - Both unchangeable by Duna vote (like the 3% Kiduna Club license and the Catalyst-set admin minimum).
4. **Distribution stack on any Compute purchase, in force:** lineage (30% initial / 18% ongoing) → 3% Kiduna Club → Catalyst-set monthly admin minimum → remainder to the member-governed treasury (default: to Programs pro-rata by Compute consumed, Catalyst payback first). This feeds Taxonomy §20.5/§20.6 at the next revision (v1.3.4, with the Program Realm promotion).

## Spine markup rulings (Moto, 2026-07-20, third pass) — several are NETWORK CANON

1. **NAMING: "Kidunaverse" is RETIRED** except as the name of the game in development. The environment is **Kiduna** / **the Kiduna Field**. (Ripples everywhere: taxonomy v1.3.3 says "Kidunaverse" throughout → v1.3.4; site copy; nightpaper; kit harness files. Fold carefully, not blindly — the company-name uses and the game keep it.)
2. **Creator is a designated, TIERED role** (network canon): everyone can always contribute, but Public-contribution rights are appointed — Dunaversity-wide by the Organization's Wizard, per-Program by its Catalyst, per-Community by its catalyst (who may make everyone a creator, or none). Needs full definition.
3. **Every Realm can have a Wizard**; a Catalyst can elevate a member to Wizard for their Program.
4. **BADGES ARE NFTs — network canon**: multiple per Program; may denote certification; may confer acceptance into Communities/Alliances/Realms; issuable by games, organizations, Institutions; after KYC/KYB as verification (Service Alliance → real vets); member-to-member verification badges; on-chain, durable, public.
5. **Promotion/acceptance is one model across ALL Realms** (not course-specific). Public material is always available to anyone and addable/remixable into any Realm.
6. **THE WISDOM-ON-THE-FIELD MODEL (canon)**: all Wisdom is added TO THE FIELD, never contained by a Realm; the Creator classifies at add-time — private-to-a-Realm, secret-to-a-Realm, personal, or public. What enters a Program is Catalyst/Creator/Wizard curation. **Private-material metadata discoverability is fundamental to the entire Kiduna Field** (discover that it exists → decide to enter the Realm). Ki's collective-Wisdom safeguards apply to ANY Wisdom on the Field.
7. **ECONOMIC CONSOLIDATION AT LAUNCH**: USDC flows to the **Kinship Duna treasury** — Dunaversity is not economically separate; no fragmented liquidity/administration/governance. Kinship Duna ↔ subsidiary-duna agreements, modifiable until spin-out; independence (even own Compute currency) allowed but not default. **The elevation → incubation → acceleration → graduation model needs canon/taxonomy/design treatment** (relationships → communities → alliances → dunas). Governance at the Kinship Duna level; members can propose policy for Dunaversity.
8. **Admin minimum defined: 20% of monthly revenue with a $50K/month floor**, Catalyst-set, no vote.
9. Governance timing: $KIDUNA issuance proposals only AFTER token launch. Early proposal type added: paying Luminaries/Catalysts to design/offer courses.
10. **Agent naming**: Program Operator (generic; never "Course Operator" — an Institution's program is the same machinery) · **Researcher** (drop the "Actor" suffix in names generally) · **QA/QC** (not Fact-Check) · Curator added (the Catalyst's real need beyond setup) · distributions are mostly deterministic policy — whether money needs an agent at all (beyond Ki expressing intent) is an open question for the flows.
11. **Catalyst-as-new-expert** (canon flavor): a Catalyst can create a Program about something they don't know — the tools make it a way to learn.
12. **One Scene ships at launch: Mastering Agency** (art/design complete; integration needed). Genesis sits on Kinship Duna.
13. **Fourth pathway: Supporting Research — Catalyst Paul** (researchers ↔ donors ↔ patients; Muscular Dystrophy, IBC-IC, Colon Cancer, Child Neurology, Glioblastoma Foundation; research programs, distribution, fundraising, communications, communities).
14. Needed spec: onramps/offramps + Sphere virtual bank accounts.

## Step-3 handoff rulings (Moto markup, 2026-07-20, fourth pass)

1. **Moto is the Catalyst** of the first Program (rename David→Moto in all Dunaversity project docs; done).
2. **Mastering Agency is the GENESIS PROGRAM** — it exists to let the others build their Programs. Pre-built state before first login: Kinship Duna (Genesis Organization) + Dunaversity (second duna) + Ki with genesis Stance/Wisdom + treasury rules. NOTHING else. All walkthroughs start from first login; never assume a prior session.
3. **Wisdom Drops are the ingestion object**: material is never dropped loosely "onto the Field" — the Catalyst asks Ki to create a named Drop per topic/purpose/Luminary (name, purpose, default classification, attribution), then ingests from desktop, Google Docs/Drive links (snapshot or linked external), or Researcher runs (generated artifacts with provenance). Structure (the movements) is DISCOVERED through Curator interview + proposals from the actual material, never assumed.
4. **Luminary flows, three cases**: on-system living (invite via their Ki, acceptance recorded) · off-system living (Ki asks for a channel; zero-spam — sent by owner or on owner's explicit instruction; "named, unreached" state exists) · **deceased (consent NOT required — notification optional, rights attestation required from the Catalyst, share routable to estate/fund)**.
5. **Creator (Program scope) precise rule — Renee Smith**: she can always publish her own Wisdom public (owner's right; any Realm can carry it); her private-to-Program submissions enter the contribution queue with Creator standing; **nothing is course-official without acceptance, and accepted material still passes the Curator for integration**. Graph holds acceptance-state + placement separately from raw vector content; permission answered by graph BEFORE vector fetch, always.
6. **Program Wizard scope defined**: delegable operations = enrollment ops, queue triage (recommend not accept), badge mechanics, schedule/notifications, Scene housekeeping; NEVER delegable = Stance, treasury/splits, acceptance-into-record, Luminary naming. Time-bound, revocable, all acts Recorded. (Launch Program Wizard: Jeya.)
7. **Scene creation is plain process**: import existing art → define characters/objects with generation help under the Program Stance → wire Portal (permissions carry unchanged unless declared) → test-walk as learner. Only the art exists today; characters etc. to be created.
8. **The handoff artifact is dunaversity/STORIES.md** (themes/epics/stories with acceptance criteria + UI notes + agents/Actions): Themes A–G Moto-as-Catalyst from first login; Themes H–J Matt/Aashik/Paul as learners on Live to the Catalyst threshold (then Studio). PATHWAYS.md demoted to narrative background.
9. **The process itself is documented as a skill**: dunaversity/SPEC-DESIGN-PROCESS-SKILL.md (kiduna-spec-design-process) — the 8-step sitting method, standing rules, ten lessons learned. Install via Settings when desired.

## Evening · the Dunaversity prototype is live

- **https://dunaversity-prototype.motodave.chatgpt.site** — the first working walkthrough of the launch loop (Catalyst creates in Studio, learner takes it in Live), v2 adds the persistent Studio ↔ Live switch in both modes. Web prototype = interaction/visual evidence; production target remains one Flutter codebase per the controlling brief.
- **The Dunaversity Engineering Handoff v2** is published (site downloads + kit): 00_START_HERE with a stated source-of-truth order (controlling Codex brief → implementation checklist → prototype DECISIONS.md → user stories → design system → capability reference → prior handoff) · the Codex brief verbatim as controlling scope · web prototype source with seed fixture · three static Studio prototypes · working design system · capability catalog/coverage/gap register · the prior 07-19 Studio handoff extracted.
- ⚠ Note: the handoff embeds **Kiduna Kit v1.4** as its system reference (06_KIDUNA_KIT) — ten versions stale (current v3.5). Engineers should treat the current kit as authoritative for canon; flag to the team.
- Hero and Prototype section link the Dunaversity prototype; the dunaversity/ spec folder (SPINE · PATHWAYS · STORIES · CODEX brief · process skill) ships in the kit from v3.5.
