# Dunaversity — The Four Creation Pathways (v0.2 · narrative background — the handoff artifact is STORIES.md)

Four Catalysts, four very different Programs, one machinery. Each narrative is written in taxonomy vocabulary and ends with what it demands from engineering. Together they cover the whole launch surface: full authorship with a Scene (Moto), the fast default path (Aashik), testimony and verification (Matt), and Institutions, money, and sensitive privacy (Paul).

---

## Pathway 1 · Moto — Mastering Agency

*"Mastering Agency: How to free yourself from time, space, and the death-grip of global civilization." Technology, governance, culture, finance. The flagship, with the only Scene at launch.*

Moto opens Studio. Ki greets him — it knows his goal from last session. "Let's build the course." Ki invokes the **Program Operator**: a new **Program Realm** forms inside Dunaversity — name, handle, description, Stance ("this course teaches people to locate their own agency; it never lectures; disagreement is material, not noise"). The Realm exists in draft; nobody can discover it yet.

Moto starts feeding it. He drags twenty years of material onto the Field — essays, talks, the nightpaper, reading lists. **Each drop is Wisdom added to the Field, classified at add-time**: most of it *private to the Program*, two essays *public* (anyone, any Realm), one set of notes *personal* (his alone; Ki may draw on it to help him teach without ever exposing it). The **Curator** organizes what's arriving into the course's four movements; the **Researcher** (multi-model, provenance kept) pulls supporting material — everything it fetches lands as *imported* Artifacts with sources attached; **QA/QC** flags one quote it can't verify. Moto cuts it.

He names his **Luminaries** — Howard, Four Arrows — people whose bodies of work the course is built with. Their material enters with *their* attribution and their consent recorded; their share is set in the Program's split rule. He appoints one of them a **Creator at Program scope** — she can now publish material into the course's public face. He elevates a trusted member to **Program Wizard** to run operations he doesn't want to touch.

The course has one thing no other launch Program has: **the Scene**. The art and design are complete; the Program Realm gets a **Portal**, and inside is the Mastering Agency world — its own visual language, connected to the same identity, permissions, Wisdom, and Records. A learner who never enters the Scene misses nothing required; a learner who does gets the course as a place.

He defines **badges**: one for each movement completed, one for the whole arc — and one *contribution* badge the Program can award when the Catalyst accepts a member's material into the course record. He sets the enrollment terms (an **Offering**: membership entitlement — included with Dunaversity membership at launch) and publishes. Status: draft → **published**. Now it's discoverable: its public metadata — title, description, the two public essays — sits in the genesis namespace where anyone's Ki can find it.

**Money:** Moto spent 1,400 USDC-worth of Compute building (Researcher runs, drafting, the Scene integration). That development Compute is on the Program's record. When the monthly default distribution runs — treasury remainder to Programs, pro-rata by Compute consumed — Mastering Agency's share first pays Moto back the 1,400; what's beyond flows to the Program's **Squad wallet**, where the split he set sends shares to his Luminaries and keeps his in his FROST wallet.

**What this pathway demands:** Program Realm creation via Ki · Wisdom add-time classification UI · Curator/Researcher/QA-QC loops · Luminary attribution + consent + splits · Creator and Wizard appointment at Program scope · Scene loading in a Surface through a Portal · badge definitions · draft→published lifecycle · development-Compute metering · Squad wallet with split rules.

---

## Pathway 2 · Aashik — Cricket

*"How to be a fan." The engineering pilot: proof that a Program takes one evening, not one career.*

Aashik tells Ki, on Live, on the couch: "I want to make a course about cricket — how to actually be a fan." Ki suggests doing the build in Studio; the Realm is created right there from the phone. Defaults do everything: standard Stance, standard badges (one: "Fan"), open enrollment, no Luminaries, no Wizard, no Scene. Total setup: four minutes.

In Studio the next morning, the **Researcher** drafts the spine of the course from public sources — laws of the game, the formats, how to watch a Test without dying of boredom (its words, flagged by QA/QC for tone; Aashik keeps it). He records three voice notes walking through his own fandom; Ki turns them into course segments — *generated* Artifacts, his provenance. He publishes the same day.

The course grows from the bottom: learners post their own club stories and watch-along rituals. **Everyone can contribute; nothing becomes course-official until Aashik accepts it.** One member's explainer on scoring is so good Aashik appoints her **Creator at Program scope** — her material now publishes straight into the course. A cohort forms for the India–Australia series: a **Community** inside the Program with its own chat and its own privacy.

**Money:** Aashik spent almost nothing building — the payback is trivial and the ongoing share small but real; it lands directly in his FROST wallet (no Squad, no splits — the default single-Catalyst path).

**What this pathway demands:** Realm creation from Live · defaults that produce a working Program with zero configuration · voice-to-segment authoring · acceptance flow (one tap) · Creator appointment · Community-within-Program · FROST-direct distribution. **This is the path Techneural builds first** — if Cricket works end-to-end, the machinery works.

---

## Pathway 3 · Matt — Military History

*Big, contribution-heavy, and the test of acceptance + provenance: the course where the curriculum is lived experience.*

Matt (Service Alliance) forms the Program in Studio: military history, but built around testimony — "the history books have the maps; we have the people who were inside the tanks." The Researcher assembles the documented record of, say, the Battle of 73 Easting; that's scaffolding. The course's heart is an open call: *were you there? Tell it.*

A member responds. He was a gunner in the Gulf War — he records forty minutes on what the last great tank battle was actually like. **His testimony is his Wisdom, added to the Field, classified private-to-the-Program**: enrolled learners can hear it; it is not public, and it never leaves without his consent. His identity carries **trust evidence**: Service Alliance has issued him a **veteran verification badge** — KYC'd once, on-chain, durable — so his testimony arrives marked *verified veteran, 2nd Armored Cavalry*, not because a moderator judged him but because the badge proves standing. A second contributor has no badge; his story enters as attributed community material with lower evidence — visible, honest about what it is.

Matt listens, then **accepts the gunner's testimony into the course's authoritative record** — the deliberate act, recorded, that makes it curriculum. He asks the contributor: may we make this public? The gunner thinks about it for a week and says yes — **he** reclassifies it (his rights, his action), and it becomes public Wisdom any Realm can carry. The course awards him the contributor badge. Matt appoints three verified vets as **Creators**; a cohort of military-history teachers forms as a Community.

The **Sentinels earn their keep here**: war testimony is heavy. The emotional-safety watch runs close to this Program — pacing, content advisories, a quiet escalation path to qualified human support — without ever scoring anybody.

**Money:** contributors aren't charity. Matt's split rule allocates a share of the Program's distribution to accepted contributors, pro-rata; the gunner gets paid for the testimony the course now runs on.

**What this pathway demands:** open contribution calls · testimony capture (long-form audio) · acceptance-into-record as a first-class recorded Action · contributor reclassification (consent) flow · **badge-as-verification issued by another Organization (Service Alliance KYC)** honored inside Dunaversity · contributor shares in split rules · Sentinel emotional watch with escalation.

---

## Pathway 4 · Paul — Supporting Research

*The stretch case: not a course at all in the industrial sense — a Program that connects researchers, donors, and patients. Muscular Dystrophy · IBC-IC · Colon Cancer · Child Neurology · Glioblastoma Foundation.*

Paul forms Supporting Research as a Program with **five Communities, one per disease area** — each with its own privacy, its own members, its own pulse. The Program does five things: gets people into research programs, distributes research, raises money, runs communications, and holds communities.

The **Glioblastoma Foundation enters as an Institution** — an outside legal entity with standing (its documentation linked to its registry), a designate, and **KYB verification badged on-chain**. It can't vote; it can **sponsor** — it funds patient memberships and underwrites a research-distribution push. Its published studies arrive as *external* Artifacts (they live where they live), **verified** — hashes and registry records — and the Researcher summarizes them into plain language, with QA/QC holding the summaries to the sources.

Privacy here is the whole game. A patient in the Child Neurology community shares her son's diagnostic journey: **private to that Community** — discoverable only as metadata ("a parent's account of the diagnostic process exists here"), so another parent's Ki can surface *that it exists* and the parent can choose to join the Community for the full Wisdom. Her son's records stay **personal** — hers alone, forever, feeding nothing. A researcher posts a recruiting call for a muscular dystrophy trial; interested members express interest through their own Ki — **the introduction is consented on both sides before either identity crosses**.

Fundraising runs as **Offerings**: a donor buys a sponsorship Offering; the USDC flows through the treasury under the same unchangeable rules as everything else, into the Program's Squad wallet, distributed by the split rule Paul set — research-distribution costs, community operations, patient-support fund — every allocation recorded, auditable by any member.

**The honest boundary, stated in the Program's own Stance:** Supporting Research connects, educates, distributes, and funds. It does not diagnose, treat, or advise — the launch gates keep clinical effects out of scope, and counsel sees this Program's Stance before it opens (it is the closest thing to Inner Clinic territory in the launch set).

**What this pathway demands:** multi-Community Programs · Institution onboarding with KYB badge + sponsorship (the first real Institution flow) · external Artifact verification · private-metadata discovery (the fundamental grammar, exercised hard) · double-consent introductions · donation Offerings through treasury rails · per-Program Stance review gates.

---

## What the four prove together

Aashik proves the floor (anyone, one evening). Moto proves the ceiling (Scene, Luminaries, full authorship). Matt proves the culture (lived experience as curriculum, verification without gatekeeping). Paul proves the reach (Institutions, money, privacy under real stakes). One machinery, no classrooms anywhere.

*Step 4 next: the consumption flow on Live + the money walk (one member's 100 USDC followed to every recipient, including the $50K-floor question). Mark this page up first.*
