# Kidunaverse cofounder skill — canon delta · 2026-07-22 · Taxonomy v1.3.5 + the Design Method

**Apply via Settings. Wins where earlier deltas conflict. Site: taxonomy.html (v1.3.5 amendment), design-method.html, design-prompts/.**

## Taxonomy v1.3.5 (owner-ruled)

1. **Presence renames Stance** — Wisdom informs · Presence instructs · Abilities enable · Automations sustain · Connections reach. A Source's Wisdom and Presence are the two most important things they add and keep updating. (Moto used the term in force; last week's musing is now ruled.)
2. **Host** = the Source who invited you (Gen-1 upline; UI shows their name/Code Name).
3. **The secret handshake** = the canonical name for the Host-set common word entered with the one-time Kinship Code at registration.
4. **Code Names: NOT unique**, spaces allowed, real identity discouraged; GUIDs underneath; per-Source private renaming translates via GUID; public handles retired.
5. **Guest** additionally = an invited person until they register.
6. **Kinship Duna is both an Ecosystem AND an Organization; "Kiduna" is its short form; kiduna.ai is its website.**
7. **Always "in Kiduna," never "on Kiduna."**
8. **NEW ECONOMICS DEFAULT — the ongoing 12%:** ongoing purchases pay lineage 18%; the 12% difference (vs the initial 30%) splits by default between **Creators** (by Compute/token flow through their Wisdom and Presence) and **Builders** (by flow through their agents — how useful they are). Forums can raise or lower. This completes the earn-by-role triad: Organize / Create / Build.
9. **The Resources page canon**: web-only personal nexus at kiduna.ai; the fully portable element (seed phrase, key share, public key, snapshot download); wallet = Solana, ONLY $KIDUNA/USDC/Badges (else may be lost); Stripe on-ramp (card, headless), Sphere off-ramp, connect-wallet; low-balance guidance + optional Stripe auto-refresh; earnings by Organizing/Creating/Building and by Duna; donations; spend by Realm; Offerings; balance shown monetary + toward goals + "how much good you did" + toward goals, all configurable by talking with Ki (right panel; Flutter/Flame; read-only in Surfaces with a link out for money moves); recirculation-not-consumption framing; impact/ripples (Compute through your Realms/Relationships; people using your Wisdom and Presence); the rotating Kinship line (centered, self-care, self-authorship, connection to others and the more-than-human world, "you are loved"); the invite flow (Kinship Code + secret handshake + private trust level + private relationship notes + private welcome context; copyable personalized invite; invitee = Guest; Ki pivots to Relationship-forming if they're already a member); the aggregate invitee CRM (participation only, nothing private).
10. **Card payments accounting**: Stripe USD → Duna bank account → on-chain via Sphere → distribution; lineage sees the pending cut ("paid by card — in the bank").
11. **Public member pages** reserved: kiduna.ai/code_name + "Join me in Kiduna" (placeholder).
12. **Registration = one page**: Code Name · Kinship Code · secret handshake · password ×2 · CTA. No email/phone/PII — nothing to subpoena; no Ki chat until registered + Compute purchased. Six-step flow and handles: gone.

## The Design Method (standing; design-method.html)

Prompt-driven, step-by-step, collaborator-agnostic (Claude Code/Codex/other): self-contained packages (CANON-BRIEF travels with prompts), one prompt per session in order, deliverables as versioned files, the design system is settled (fine-tune, don't restyle), **permanent personas Alice · Bob · Carol · David** (Alice invited Bob; Carol invited David; formerly Nikzad/Simon/Moto/Aashik), Moto marks up each output before the next runs, accepted outputs feed the kit, every design turn states its taxonomy impact.

## Round 1 package (design-prompts/)

DESIGN-PROMPTS-2026-07-22.md: P1 personas + backstories/styles/invite-trees · P2 the Resources dashboard rework · P3 invites + aggregate CRM · P4 the one-page registration · P5 public member pages placeholder. CANON-BRIEF.md controls vocabulary. ⚠ The current-screens zip was NOT attached to the instructing prompt — Moto drops it into the package before handoff.

## Package v2 (same day): self-executing

The screens zip (Kiduna Design Complete 2026-07-21) arrived and is embedded at 04_SCREENS/. **Lesson learned, now method canon: a handoff package must be an OPERATING ORDER, not a document set** — README/AGENTS.md/CLAUDE.md/00_START_HERE all carry the same imperative ("You are executing, not reviewing; your first response is the Prompt 1 deliverable; the only acceptable first question is about a missing file"), and PASTE-THIS.txt gives Moto the one-line kickoff message, because chat tools read nothing from a zip until told. Old package deleted; v2 in the Kidunaverse folder.

## Afternoon ruling · THE HANDSHAKE, GENERALIZED (taxonomy v1.3.6)

The Handshake is now a general instrument, not just onboarding: **a single-use verification word agreed out-of-band between two people.** Uses: (1) onboarding (Host sets it, passes with the Kinship Code); (2) **forming any Relationship** — one Source asks Ki to connect, names who the other person is, states the Handshake; the other Source must enter it when confirming; don't know it = not the right person, no Relationship forms. Rules: once only; agreed out-of-band (Kiduna never transmits it between parties); not stored beyond verification; failed Handshakes fail quietly (no disclosure of who was expected). Composes with trust levels and Cloaked Sources: person-to-person verification with zero institutional identity. Design prompts P3 and the canon brief updated; collaborator package v2 rebuilt in place.

## Evening · ENAMEL: the Studio UI system (+ the Kiduna Design System pack)

- **Studio Enamel v0.5 is the controlling visual canon for Studio** (site: enamel/; full pack in downloads with its working Next.js website). The three-layer world: **Field = lacquer** (near-black deep umber #0A0604, crisp/quiet/optically deep, sparse engraved arcs, no gradients) · **Realms = celestial enamel vessels** (warm metal/enamel rim, near-black core, ONE semantic type hue, custom inlaid geometric crest, localized reflected halo, nested glints, traveling label) · **Allies = people** (stable identity across four moods: Open · Engaged · Focused · Dreaming; camel + moon-cream identity ring; no permanent brightness/scale advantage — a relationship or task can be more prominent). Material rules: enamel deep, slightly irregular, tactile; highlights moon cream; wire/rims camel + sun gold; dimension from material hierarchy, never 3D spectacle. Recomposable systems: emblems, connection grammar, talismans, background geometry; tokens CSS; acceptance checklist; six personas × four moods = 24 Ally examples.
- **The Kiduna Design System pack (2026-07-22, 58MB)** is in downloads: fonts, preview, business card, the allies system (ALLY-SYSTEM/IMPLEMENTATION/GENERATION-GUIDE), asset libraries (icons, allies, talismans, organization crests, realm emblems), root SKILL.md, plus the embedded Enamel v0.4 bundle and the Alice/Field M0.3 handoff.
- ⚠ **Naming variance to reconcile**: the Enamel pack says "an Ally is the Source's persistent identity inside Kiduna" — visual-identity usage (the Source's avatar with moods), while taxonomy v1.3.4+ says all agents are Actors with Ki universal and no per-Source named allies. Likely resolution: the Enamel "Ally" card is the SOURCE's visual identity mark, not an agent — needs Moto's one-line ruling and then a rename sweep in the pack (or a taxonomy note).
- Kit v4.0 carries the ten Enamel handoff docs + tokens (enamel/); the two large zips stay in site downloads (linked, not embedded) to keep the kit portable.