Kiduna Design Personas

Prompt 1 deliverable · 2026-07-22 · fixture version 2026-07-22.prompt-1

This is the durable persona bible for Kiduna design work. Alice, Bob, Carol, and Danny are the four permanent lead Sources used to develop and review every screen. Other Sources may appear as background characters, but they do not replace or redefine these four.

The machine-readable companion is data/personas.json. When this document and the JSON differ, resolve the difference explicitly; do not silently choose one. The controlling vocabulary remains 01_CANON-BRIEF.md in the 2026-07-22 design-prompt package.

Fixture invariants

• Alice, Bob, Carol, and Danny are public Code Names, not stored real-world identities. Code Names may contain spaces, need not be unique, and resolve through a GUID.
• Alice invited Bob. Bob invited Carol. Carol invited Danny. Those Host relationships never change between screens.
• The current screens take place more than a year into the seeded history, and the Sources have invited other Sources. Bob is the most active organizer and Host.
• Kinship Duna and Dunaversity are automatic for all participants in the Ecosystem, including these Sources. Other Organizations, Programs, and Communities vary by Source.
• Ki is the universal Actor. The four Sources have different conversational patterns, but none has a separately named personal ally.
• Wisdom informs. Presence instructs. Screen copy must not revive the retired term “Stance.”
• Money renders as facts. $KIDUNA is prepaid Compute usage credit, never an investment promise.
• The dated market-reference fixture used throughout this round is 1 $KIDUNA = 0.25 USDC on 2028-07-22, the date of this system snapshot. It is a design datum, not a prediction.
• No grades, leaderboards, or scores are attached to these Sources.
• Private nicknames translate through the Source GUID. A nickname changes only the naming Source’s own view.
• Two Sources are connected only when they exchange a Handshake. Proximity, discovery, invitation, or one-sided trust does not substitute for that mutual threshold.
• The Resources numbers are deterministic fixtures for comparative screen design, not authoritative balances or claims about any real person.

At a glance

The four lead names are intentionally ordinary. A public Code Name does not claim uniqueness, and the prototype must never imply that a familiar name identifies a real-world person.

Alice

Public Code Name: Alice
GUID: src-01JQ7M6W0KALICE8X4N2P9R3D
Pronouns: she/her
Former fixture: Danny Nikzad

Backstory

Alice is an independent systems designer and product architect for member-owned institutions. She spent a decade translating between engineers, operators, and community stewards, often entering when an organization had grown past what informal coordination could hold. She is good at finding the hidden transfer of authority inside an apparently harmless convenience.

She cares about systems that leave people more capable, plain consent, inspectable authority, durable mutual-aid infrastructure, and institutional memory that remains useful without becoming extractive. Outside work she walks before sunrise, repairs old field guides, collects small tools, and hosts long dinners where a difficult idea can take the time it needs.

Alice entered Kiduna looking for a place where careful systems work could remain answerable to relationships. She is generous with analysis and conservative about turning a pattern into infrastructure.

What Alice joins and forms

Alice is automatically in Kinship Duna and Dunaversity. She is an Organizer in Kinship Duna, an Organizer and Builder in Service Alliance, an Organizer in Mycelial Aid, and a Member in Cosmic Humanity.

In Dunaversity she is taking Mastering Agency, catalyzing Consentful Systems, and creating Records That Can Be Trusted. She formed the Community Small Tools, Long Memory and joined Mutual Infrastructure Practitioners.

Design implication: Alice’s Field should often contain inspectable structures, Records, version comparisons, and explicit authority. Her screens should feel calm and exact, never managerial for its own sake.

Conversation with Ki

Alice usually begins in text with a terse intention, then asks exact follow-ups. She uses voice after she has inspected the facts and wants Ki to synthesize a pattern. She delegates gathering, comparison, and reversible drafting. She retains commitments, grants, publication, and money movement.

Her money questions are concrete: “What is the Compute ceiling?”, “Which Realm consumed it?”, “What is reserved versus settled?”, and “What repeats next month?” She never asks Ki for price predictions, a way around another Source’s boundary, or a ranking of people.

Typical exchange:

Alice: Show me what changed, what it would authorize, and what still depends on Bob.

Ki: Two Records changed. One grant is ready for your confirmation. Bob has not accepted the Project role, so no shared work can begin.

Code Name and identities

Alice stores no real identity in Kiduna. Her public Code Name is Alice. She uses the cloaked Persona Field Notes for public writing about institutional design.

Bob privately calls her Al. Carol calls her North Star. Danny calls her Alice from Systems. Each name is local to that Source and resolves to Alice’s GUID.

Invitation tree

Alice invited Bob on 2025-04-18. Her other direct invitees are:

Only aggregate participation belongs in Alice’s Cell view. Alice may see who appears stuck or active and what her lineage generated in aggregate; she may not see private Realms, private Wisdom, or hidden activity.

Resources profile

• Compute purchased: 48,000 $KIDUNA for 12,000 USDC.
• Current wallet: 18,400 $KIDUNA (fixture value 4,600 USDC) and 820 USDC; complete monetary view 5,420 USDC.
• Earned: 31,200 $KIDUNA — Organizing 18,000; Creating 9,200; Building 4,000.
• Earned by Duna: Kinship Duna 12,600; Service Alliance 10,800; Mycelial Aid 7,800.
• Donated: 6,400 $KIDUNA.
• Compute spent: 54,400 $KIDUNA — Service Alliance 18,600; Cosmic Humanity 12,400; Dunaversity Programs 11,800; Mycelial Aid 7,600; Relationships and Cell 4,000.
• On-ramped: 12,000 USDC. Off-ramped through Sphere: 5,400 USDC.
• Offerings bought: 2,100 USDC. Offerings sold: 7,860 USDC.

Her Resources view should foreground legibility and control: pending versus settled, recurrence, authority, and portable recovery before celebration.

Bob

Public Code Name: Bob
GUID: src-01JQ7M6W0KBOB4F8A1H5T2Y9
Pronouns: he/him
Host: Alice
Former fixture: Matt Simon

Backstory

Bob is an organizer, facilitator, and operating partner for distributed service networks. He learned organizing through neighborhood recovery work and spent years helping member networks turn energy into repeatable operations. Alice invited him after they co-facilitated a coalition meeting that nearly failed until the room slowed down enough to hear the quietest participants.

Bob cares that people who join actually find a place to contribute. He treats lineage as a span of care, not a surveillance surface. He wants work to pay clearly and institutions to survive their founders. He loves feeding a room before asking it to decide, maintaining trails, sending late-night voice notes, and helping someone find the useful edge of their power.

He is the most prolific Host among the leads. Every invitation feels to him like a promise to notice whether the person is stuck.

What Bob joins and forms

Bob is automatically in Kinship Duna and Dunaversity. He organizes in Kinship Duna; organizes and catalyzes in Service Alliance; organizes in Soul Kitchen; builds in Mountain River Trail; and participates in EP Rising.

In Dunaversity he catalyzes Hosting Without Surveillance, creates Lineage as Care, and takes Mastering Agency. He formed The Welcome Table and Rural Organizers’ Practice, and joined Kitchen Shift.

Design implication: Bob’s views often contain people needing attention, invitations in different states, role agreements, and distributions. They should communicate care and consequence without turning participation into a score.

Conversation with Ki

Bob is voice-first, chatty, associative, and quick to test a concrete next move. He wants a compact written summary and inspectable Records after a decision. He delegates preparation, reminders, invitation follow-up, and comparison, but confirms anything that speaks for him or commits a Realm.

He asks who has been paid, what remains pending, how a lineage distribution was calculated, and whether a role has sufficient Compute. He never asks which private Realms an invitee joined, what someone told Ki privately, or who is “winning.”

Typical exchange:

Bob: Who in my Cell looks like they might need a hand—not what they’re doing, just whether they’ve found their footing?

Ki: Two direct invitees have been quiet for more than a month. I can help you prepare separate check-ins. I will not infer why they are quiet.

Code Name and identities

Bob stores no real identity in Kiduna. His public Code Name is Bob. He uses the cloaked Alias Trail Steward for public trail coordination he does not want joined to his other work.

Alice calls him Bob S. Carol calls him Bridge Builder. Danny calls him Coach Bob. Each private name is local to the naming Source.

Invitation tree

Bob has thirteen direct invitees, making him the organizer-type fixture. Carol is part of this lineage alongside the twelve previously named invitees:

Bob’s mature Cell makes him the primary fixture for aggregate CRM design. Participation is shown only as aggregate activity and lineage generation; never disclose a person’s Realms or private context.

Resources profile

• Compute purchased: 240,000 $KIDUNA for 60,000 USDC.
• Current wallet: 1,240,000 $KIDUNA (fixture value 310,000 USDC) and 4,260 USDC; complete monetary view 314,260 USDC.
• Earned: 1,480,000 $KIDUNA — Organizing 1,050,000; Creating 260,000; Building 170,000.
• Earned by Duna: Kinship Duna 530,000; Service Alliance 530,000; Soul Kitchen 240,000; Mountain River Trail 180,000.
• Donated: 140,000 $KIDUNA.
• Compute spent: 340,000 $KIDUNA — Service Alliance 126,000; Soul Kitchen 74,000; Mountain River Trail 61,000; Dunaversity Programs 49,000; Relationships and Cell 30,000.
• On-ramped: 60,000 USDC. Off-ramped through Sphere: 22,610 USDC.
• Offerings bought: 9,200 USDC. Offerings sold: 38,640 USDC.

Bob’s Resources view should foreground recirculation: how money and Compute moved through people and Realms, what is pending, and where attention—not surveillance—may be useful.

Carol

Public Code Name: Carol
GUID: src-01JQ7M6W0KCAROL9D3P6V2N8
Pronouns: she/they
Host: Bob
Former fixture: Moto

Backstory

Carol is a learning designer, creative producer, and Catalyst for participatory Programs. They moved between documentary production, leadership education, and community arts before becoming a full-time Catalyst. Bob invited them into Kiduna. Carol helped establish Dunaversity’s practice-led approach and invited Danny after a watershed restoration gathering.

Carol cares about play as serious civic capacity, learning that changes who can act, creative provenance, and relationships with the more-than-human world that are not merely decorative. They love improvised games, oral history, making a room feel braver, and the moment a learner becomes a contributor.

Carol is generous with experiments but exact about attribution and the boundary between a proposal and a committed Action.

What Carol joins and forms

Carol is automatically in Kinship Duna and Dunaversity. She creates in Kinship Duna; catalyzes and creates in Dunaversity; organizes and catalyzes in The Fellowship of Play; creates in Homeworld and Fanduna; and participates in Cosmic Humanity.

Carol catalyzes How to Be a Cricket Fan, creates Practice-Led Facilitation, and takes Mastering Agency. They formed The Play Commons and Storykeepers’ Room, and joined Homeworld Field Notes.

Design implication: Carol’s screens should support generative conversation, versioned Media, provenance, recognition, and a clean handoff from playful proposal to exact confirmation.

Conversation with Ki

Carol uses voice while moving and text when comparing versions or approving exact language. Their speech begins expansive and metaphorical, then becomes decisive once Ki reflects the pattern back. Carol delegates generative exploration, scheduling, and first drafts, while personally confirming attribution, publication, and money movement.

They ask whether contributors were recognized, what recirculated, which Program consumed Compute, and what can be donated safely. They never ask how to maximize passive income, for contradictions hidden in another Source’s private Wisdom, or for a leaderboard.

Typical exchange:

Carol: Keep the wildness, but show me the exact moment this becomes public.

Ki: The first three versions stay private in the Program. Publication begins only with the Confirmed Action shown here. I can preview the public artifact before you decide.

Code Name and identities

Carol stores no real identity in Kiduna. Her public Code Name is Carol. They use the cloaked Mask C. North in an experimental performance Realm.

Alice calls her C. Bob calls her Playmaker. Danny calls her Carol of Homeworld. These names never change what other Sources see.

Invitation tree

Carol invited Danny on 2025-06-08. Her direct invitees are:

Resources profile

• Compute purchased: 160,000 $KIDUNA for 40,000 USDC.
• Current wallet: 310,000 $KIDUNA (fixture value 77,500 USDC) and 2,140 USDC; complete monetary view 79,640 USDC.
• Earned: 760,000 $KIDUNA — Organizing 150,000; Creating 470,000; Building 140,000.
• Earned by Duna: The Fellowship of Play 280,000; Dunaversity 240,000; Homeworld 135,000; Cosmic Humanity 105,000.
• Donated: 110,000 $KIDUNA.
• Compute spent: 500,000 $KIDUNA — The Fellowship of Play 170,000; Dunaversity Programs 130,000; Homeworld 90,000; Cosmic Humanity 70,000; Relationships and Cell 40,000.
• On-ramped: 40,000 USDC. Off-ramped through Sphere: 18,400 USDC.
• Offerings bought: 6,800 USDC. Offerings sold: 29,400 USDC.

Carol’s Resources view should make contribution, recognition, and recirculation legible without aestheticizing money or turning impact into a performance score.

Danny

Public Code Name: Danny
GUID: src-01JQ7M6W0KDANNY5C8R1L4S7
Pronouns: he/they
Host: Carol
Former fixture: Aashik

Backstory

Danny is an ecological field technologist and cooperative operations builder. He works where ecological monitoring, land stewardship, and cooperative logistics meet. Carol invited him after they collaborated on a watershed gathering.

Danny cares about land repair led by people who live with the consequences, technology that works offline, clear recovery paths, and keeping sacred or private knowledge out of general retrieval. He loves rivers after rain, repair manuals, community radio, and turning field observations into shared practice.

He entered cautiously, completed his first Dunaversity Program before contributing, and now builds small Actors that help teams prepare field Records without claiming authority over them.

What Danny joins and forms

Danny is automatically in Kinship Duna and Dunaversity. He builds in Dunaversity, Mountain River Trail, and Mycelial Aid, and participates in Indigenous Revival and Safeword.

He creates How to Be a Cricket Fan and Field Records Without Extraction, and has completed Mastering Agency. He formed Watershed Repair Log and joined Offline-First Builders.

Design implication: Danny’s screens should foreground boundaries, offline or delayed states, explicit classification, recovery, Compute ceilings, and the difference between an Actor’s draft and a Source’s authority.

Conversation with Ki

Danny is text-first, terse, sequential, and comfortable with silence while he inspects. He uses short voice check-ins from the field. He delegates research, formatting, and reversible drafts while retaining classification, sharing, wallet, and recovery Actions.

He asks for the exact Compute ceiling, what can be recovered, whether a charge is reserved or consumed, and which Realm authorized it. He never asks for another Source’s private location, access to sacred material, or market hype.

Typical exchange:

Danny: Offline for six hours. What can I prepare without committing?

Ki: You can gather the permitted field Media and draft the Record locally. Sharing, classification changes, and Compute settlement will wait for a verified connection and your confirmation.

Code Name and identities

Danny stores no real identity in Kiduna. His public Code Name is Danny. He uses the cloaked Persona River Cartographer for public field reports that should not reveal his everyday Code Name.

Carol calls him D. Alice calls him River Danny. Bob calls him Cartographer. Each private name remains attached to Danny’s GUID only in the naming Source’s view.

Invitation tree

Danny is the low-volume Host fixture. His screens should show that a small Cell can be healthy without nudging him to recruit more people.

Resources profile

• Compute purchased: 36,000 $KIDUNA for 9,000 USDC.
• Current wallet: 21,000 $KIDUNA (fixture value 5,250 USDC) and 310 USDC; complete monetary view 5,560 USDC.
• Earned: 28,000 $KIDUNA — Organizing 8,000; Creating 12,000; Building 8,000.
• Earned by Duna: Mountain River Trail 10,000; Mycelial Aid 8,000; Indigenous Revival 6,000; Dunaversity 4,000.
• Donated: 4,000 $KIDUNA.
• Compute spent: 39,000 $KIDUNA — Mountain River Trail 12,000; Mycelial Aid 10,000; Indigenous Revival 8,000; Dunaversity Programs 6,000; Relationships and Cell 3,000.
• On-ramped: 9,000 USDC. Off-ramped through Sphere: 2,100 USDC.
• Offerings bought: 1,200 USDC. Offerings sold: 3,850 USDC.

Danny’s Resources view should feel portable and recoverable. It should prefer exact facts, low-balance guidance, and explicit safety over animation or abundance cues.

Cross-persona review matrix

Every later screen should be reviewed against the four different needs below rather than merely swapping a name and avatar.

Implementation contract

1. Import the four design personas from data/personas.json; do not redefine names in component-local arrays.
2. Use alice, bob, carol, and danny as the URL and fixture IDs.
3. Never infer a real identity from a Code Name, public profile, connected wallet, or private nickname.
4. Use the sourceGuid as the fixture identity when a screen needs disambiguation.
5. Preserve Alice→Bob, Bob→Carol, and Carol→Danny in invitation, lineage, and Resources views.
6. Display activity as plain time-based states. Do not collapse it into a score.
7. Use the resource seed as dated facts. Any “live” price label in a mock must visibly retain its fixture timestamp unless it is connected to a real price source later.
8. When a later prompt changes one profile, update this document and the JSON seed in the same change.

Taxonomy impact

No taxonomy change. This prompt instantiates existing canonical concepts—Sources, Hosts, Cells, Code Names, GUIDs, Cloaked Sources, Organizations, Programs, Communities, Resources, Wisdom, Presence, and Ki—without proposing a new system term.