# Kiduna Design Prompts · Round 1: Outside the Field · 2026-07-22 **YOU ARE EXECUTING, NOT REVIEWING.** This package is an assignment, not a document set: work the prompts below IN ORDER, one per session, starting with Prompt 1 immediately. Read `01_CANON-BRIEF.md` first — controlling vocabulary and rules. The complete current screens are in `04_SCREENS/` (offline copy of the offline screens in 04_SCREENS/ — open the HTML directly; the pages these prompts target are `04_SCREENS/out/outside/resources.html`, `signup.html`, `organization-selection.html`, `landing.html`, `checkout.html`, plus the Studio and Live pages for context). The general design system — inside the Field and outside — is liked and stays; fine-tune to buildable precision, never restyle. Do not invent vocabulary; anything not in the canon brief is a question, not a coinage. Deliverables are files (specs, mocks as HTML using the existing design system, data seeds), returned as a zip or a repo change — never loose prose in chat. --- ## PROMPT 1 — The four Personas Rename the design personas across all screens and fixtures: - **Alice** (was David Nikzad) - **Bob** (was Matt Simon) - **Carol** (was Moto) - **David** (was Aashik) Then write a durable persona bible we can build on far into the future — these four are the Sources we develop every screen for (other people appear in screens as background; these are the leads). For each persona: 1. **Backstory** — who they are, what they care about, what they do for work and love. 2. **What they'd join and form**: which Organizations (from the launch set: Kinship Duna + Dunaversity automatic; plus e.g. Service Alliance, The Fellowship of Play, Mountain River Trail, Mycelial Aid, EP Rising, Safeword, Fanduna, Homeworld, Soul Kitchen, Indigenous Revival, Cosmic Humanity…), which Dunaversity Programs (courses) they'd take or catalyze, which Communities they'd form or join. 3. **Conversational style with Ki** — terse or chatty, voice or text, how much they delegate, what they ask about money, what they never ask. 4. **Code Name and identities** — their public Code Name (remember: Code Names need not be unique, can have spaces, and most people should NOT use their real identity); any Cloaked-Source usage; who calls them what (personal nicknames translate per-Source via GUID). 5. **Invitation tree** — **Alice invited Bob; Carol invited David.** All four have invited others — some many (an organizer type), some few. Name their invitees (background characters), when they joined, and how active each is. Assume the system has been live for **over a year**, so numbers are reasonably mature. 6. **Their Resources profile** — what they've purchased, earned (Organizing / Creating / Building), donated, spent by Realm, on/off-ramped — coherent with the backstory and the economics in the canon brief. Assume **$KIDUNA has launched and has a market price**; pick one and keep it consistent. Deliverable: `PERSONAS.md` + a data seed (JSON) other prompts and fixtures consume. Every later prompt uses these four; never re-derive them. --- ## PROMPT 2 — The Resources page (the real one) Rework the offline screens in 04_SCREENS/outside/resources?persona=david and .../resources?persona=matt (rename per Prompt 1) into a **true resources dashboard**. It does not make sense as it stands. Context that governs the design: **What this page IS.** The one significant logged-in page that lives only on the web (kiduna.ai) — never a Surface's home. It is the Source's **personal nexus and control center**: everything else in Kiduna is about relationships and groups; this place is for you alone. It is the fully **portable element** — if you trust neither Apple nor Microsoft nor anyone with your account and money, this is where you hold it yourself: download a snapshot, log in from anywhere, find your key connections, extract your money. Solid, calm, in-control feel. It will also render **read-only inside the Surfaces** (same technology — Flutter/Flame — same panels), with a link out to the web page for anything that moves money or changes core identity. **The interaction model — this is the key.** There is no reason for a traditional dashboard when you have AI. **Ki lives in the right panel of the page**, exactly as in the Surfaces, and the page is highly interactive between what's on the Field (left: panels, summaries, drill-downs) and Ki (right). Summaries with drill-downs, clean — but different views, deeper cuts, and reconfiguration of the dashboard itself happen **by talking with Ki** ("show me by Realm," "which of my invitees are active," "set a goal"). The dashboard's own setup is a conversation. **Remove:** "Download Kiduna Studio for Mac," "Founding Round," and anything else extraneous to a resources nexus. **Show (with sensible information architecture, not a wall):** - Compute purchased — USDC paid, $KIDUNA received (market price live). - Wallet value, unmistakable: USDC balance and $KIDUNA balance, each valued. - On-ramp / off-ramp history, and the actions: **off-ramp via Sphere · on-ramp via Stripe crypto headless (pay with card) · connect wallet.** - Earned, by category and **by Duna**: **Organizing** (lineage: 30% of initial purchases at 20/5/3/2; 18% lifetime on ongoing at 12/3/2/1) · **Creating** (default share of the ongoing 12% pool, driven by Compute/token flow through their Wisdom and Presence) · **Building** (the other side of that 12% pool, driven by flow through their agents — how useful they are). Note on the page model, not the UI: the Forum can vote these defaults up or down. - Donated. - Spent on Compute, by Realm. - Offerings bought and sold (if any). - **Overall balance, several ways**: complete monetary · monetary against the Source's financial goals · **how much good you did** · good against goals · broken down by goals the Source sets — all of it settable and reworkable conversationally with Ki. - **Impact and ripples**: how much Compute flowed through your Realms and Relationships; **how many people are using your Wisdom and your Presence** — the two most important things a Source adds and keeps updating. Resources here are about **recirculation, not consumption**: what you brought in, how it transformed and grew. **The wallet section (portable identity):** seed phrase and key share for recovery, public key visible; explicit copy that this wallet supports **only Compute ($KIDUNA), USDC, and Badges (NFTs) on Solana** — send anything else and it may be lost (recoverable only by opening the wallet elsewhere with the seed phrase); strong plain guidance on writing the seed phrase on paper and keeping it safe; suggest moving money regularly to a bank account and keeping a low USDC balance here, with an optional **auto-refresh via Stripe** when the balance runs low. Core-identity changes happen here and feel appropriately weighty. **The Kinship vibe:** the page draws from the Wisdom and is processed by Ki for this Source — a rotating, ever-changing line that reminds them to stay centered and practice self-care; of self-authorship (this is their life and only theirs; they are the authority as much as any other human); of their connections to others and to the more-than-human world; that their strength is what the universe wants; that they are loved. Quiet, never saccharine, always changing. Deliverable: full screen spec + high-fidelity mock for Alice and Bob's states (different profiles, per Prompt 1 data), component inventory, and the Ki-interaction script for five representative asks. --- ## PROMPT 3 — Inviting, and the aggregate CRM Design the invitation flow and the invitee view, living on the Resources page (in the Field/panels, with Ki, or both — design the interplay). **Creating an invite** collects five things: 1. **The Kinship Code** to pass along (one-time, only usable by that person). 2. **The secret handshake** — a single common word the inviter types and the invitee must enter. 3. **Trust level** — high / medium / low (private, never shown to the invitee). 4. **Anything the inviter wants to add to the relationship in advance** (private; used to support the relationship — and to repair it if there are issues). 5. **Anything that helps Ki welcome them** — interests, context (private). Output: a **copyable, personalized invite** for email/text, warm and in the inviter's voice. Until the person registers, they exist in the system as a **Guest**. **Already-a-member handling:** Ki should say when it believes the person is already in Kiduna — in which case the flow pivots to **forming a Relationship** instead of a system invite — which uses the same instrument: the two agree a **Handshake** out-of-band; the initiator tells Ki who the person is and states the Handshake; the other Source must enter it when confirming, or the Relationship does not form (single-use; failure is quiet). Design that pivot and its fallback (Ki is unsure; the person declines; the Handshake fails). **The aggregate CRM:** the Resources page tracks the Source's invitees — who joined, when, how much they're participating, what they've generated for the lineage — **aggregated only**: never which Realms they joined, never anything private. This is the Host's span of care (their Cell): the point is knowing who's stuck and who's thriving, not surveillance. Deliverable: invite-creation flow (panel + Ki paths), the invite artifact itself, the Guest state, the pivot flow, and the CRM view integrated into Resources. --- ## PROMPT 4 — Registration, one page Replace the current six-step onboarding (email, handles, all of it — gone) with a **single registration page**: 1. **Code Name** — spaces allowed, need not be unique. How you'll be known to strangers in Kiduna and publicly. The page suggests NOT using your real identity: you can reveal your real identity later to people you trust; with surveillance and personal-data collection what they are, we won't hand the world another surface. Make the privacy promise clear and short: **Kiduna stores no personally identifiable information — no email, no phone — so there is nothing to subpoena and no way to connect accounts to real-world identities.** This is a registration page: every word earns its place; and no chatting with Ki until registration and the Compute purchase are complete. 2. **Kinship Code** — the one-time code passed by the person who invited you (canon term: their **Host**; on the page, show the Host's name or Code Name — "Invited by Carol" — not the word Host). 3. **The secret handshake.** 4. **Password/passphrase.** 5. **Repeat password/passphrase.** 6. CTA. Uniqueness architecture: two people may share a Code Name — fine. **Everyone has a GUID underneath**; when reaching someone or inviting, the system disambiguates, and any Source can privately rename anyone for themselves ("my Jaya") — the nickname translates via GUID. Common names and nicknames always work. Then continues to the Compute purchase: card via **Stripe** (USD lands in the Duna's bank account, recorded, moved on-chain via **Sphere**, then distributed — the lineage sees the cut coming to them once the funds move on-chain, marked "paid by card — in the bank") or connect wallet / USDC direct. Auto-enrollment in Kinship Duna and Dunaversity on completion. Deliverable: the registration page spec + mock, the exact microcopy (the privacy paragraph is the hard writing — do it well), the card-payment accounting states, and the lineage pending-distribution view. --- ## PROMPT 5 — Public member pages (placeholder) Reserve and sketch — do not fully design — public pages at **kiduna.ai/code_name** for each member: what minimally shows (Code Name, whatever the Source chooses to make public, nothing else), and a **"Join me in Kiduna"** button that starts the invite-request path. Handle the non-unique Code Name case (disambiguation page). One page of spec; held for later. --- ## Standing rules for every prompt in this series Always "**in Kiduna**," never "on Kiduna." · The humans are **Sources**; the agents are **Actors**; Ki is the universal Actor. · **Host** = the Source who invited you (your Gen-1 upline). · **Kinship Duna is both an Ecosystem and an Organization — it holds everything else; "Kiduna" is simply its short form, and kiduna.ai is its website.** · Wisdom informs; **Presence** instructs (the capability formerly called Stance). · Money renders as facts; gold is reserved for Deliberate acts; the four privacy classifications get four unmistakable treatments; every Element carries an inspect affordance. · Deliverables are files in the repo/package, versioned, never loose in chat.