# Design R4 — the prompt (ready to paste into Claude Design)

**Attach `kidunaverse-design-r4-inputs.zip` (this folder) with the prompt below. Written 2026-07-08. Run it in the Kidunaverse design system project (2de4dee0-9628-4871-a4e3-fc4ddc902d31).**

---

```
You are designing round 4 of the Kidunaverse end-user app, in the Kidunaverse design
system project (2de4dee0-9628-4871-a4e3-fc4ddc902d31); colors_and_type.css is law
(espresso ground, Avenir body, Goudy Heavyface display, IBM Plex Sans callouts,
sky = touchable, gold = signature moments).

I've attached kidunaverse-design-r4-inputs.zip. Read in this order:
1. experience.md, organizations.md, protocol.md — Spec v4.1 (updated 2026-07-08).
   Experience is the assignment; Organizations gives you the ONLY example universe;
   Protocol gives you what's on-chain (wallets, Compute, votes).
2. orchestration.md, foundation.md — the system behind it.
3. r3/ — your round-3 output WITH Moto's resolutions already folded in
   (UX-SPEC-R3.md §11 changelog, OPEN-QUESTIONS.md resolutions). R3 remains in
   force except where the July 8 canon below changes it.

THE JULY 8 CANON (fixed — this is what changed since R3):
- Training is named: KIDUNAVERSITY, the first REALITY GAME. Nothing inside it
  affects the Kidunaverse — everything is fake, or staked and returnable. Entered
  through portals in chat (tap-to-enter with abortable crossing, per your resolved
  R3 §7). Allies wear roles/names inside; actors (NPCs) have purposes and routines;
  trainings can reach real channels (email, Telegram) as exercises.
- LEVELS render per duna, founder-set: Guest · Member · Organizer (with a Clan) ·
  Founder · Builder · Creator · Catalyst · Luminary. Design how a level shows and
  how a promotion feels (a gold moment? it's earned, not bought).
- Two new social objects: GUILD (ad-hoc named group — no wallet, sharing scope
  only, feather-light in UI) and INSTITUTION (outside entity with a squad wallet
  and contracts — a counterparty, never a voter; renders distinctly from members).
- COMPUTE is the canonical term (never "compute currencies"): you hold Kiduna
  Compute, Service Alliance Compute. The token chip grammar from R2 drift stands.
- Forums execute DUNA COMMANDS: a passed proposal performs named actions
  atomically ("purchase 27 acres" = purchase_property + transfer_usdc + …).
  Design how a proposal SHOWS its commands — members should see what will
  actually happen if it passes, as plainly as a receipt.
- The agentic internet: a member/institution registers a domain via a DNS TXT
  record and the whole domain becomes trusted within a duna's accountability.
  Design the moment a member's ally encounters a trusted vs untrusted domain.

EXAMPLES: use ONLY the 31 real dunas in organizations.md — BiHome (Inner Clinic),
Contraction (It's the Law), Celebrity Solar, Freehold Finance, Flag Tag, Homeworld,
Hyphal, Fanduna, Mountain River Trail, Party Line, Safeword, Soul Kitchen, The
Ceremony Machine, Wokelord, and the rest. No invented organizations, no lorem.
Boundaries are fluid: the purpose of a duna is legal standing/accountability —
which entity is responsible — never walls between people. Show the fluidity.

DELIVERABLES, in a /design-r4 folder:
1. UX-SPEC-R4.md — what changed from R3 and why, section by section.
2. Redraws of R3 screens 1b (voice) and 1l (the crossing) so visuals match the
   resolved copy (currently flagged in MANIFEST as visual-only pending).
3. THE WEB MONEY SURFACE (committed in your resolved R3 §9): join ($100 Compute),
  wallet, limits, reload Compute, Institution setup ($1K, enroll up to 10), and
  the authorize page that renders NOTHING but the act — what, how much, to whom,
  one signature. Espresso↔cream inversion, Goudy figures, no promotional chrome.
  4–6 screens, desktop + mobile web.
4. KIDUNAVERSITY: 3–4 screens — a portal offer in chat, one regimen scene in the
  isometric world (a real duna as setting: e.g., practicing a Forum vote inside a
  simulated Mountain River Trail land purchase), a practice-signature moment
  (teaching press-and-hold, per resolved R3 §7), and the Foundry-Scrip-style
  named sim Compute in the fiction.
5. LEVELS & SOCIAL OBJECTS: 2–3 screens — a promotion moment, a guild in a
  sharing flow next to connections/alliances/organizations, an institution as
  contract counterparty.
6. MOTION-ADDENDUM-R4.md and OPEN-QUESTIONS-R4.md (disagreements, sharply, with
  alternatives).

PACKAGING — exactly as round 3, it worked: MANIFEST.md listing every file and
where it lands under design-r4/ on kiduna.team; all references relative
(../_ds/kidunaverse-2de4dee0-9628-4871-a4e3-fc4ddc902d31/... for the design
system, ./assets/ for new assets, included); then compress /design-r4 into
kidunaverse-design-r4.zip, self-contained, and give me the download link as the
LAST thing in your response.
```
