# Kidunaverse — Five Interface Paradigms

**Brief:** the current prototype (5 tabs, a chat thread, settings, forms) may be the wrong inheritance for a fully agentic, member-owned organization. Below: five genuinely different paradigms, each breaking at least three of its assumptions, spanning from one-step-from-convention to PM-frightening.

**Canon held fixed in all five:** one member, one ally · kinship codes as the trust mechanism · the organization is the frame, not a platform · members, never users · HEARTS/Sentinel exists · mobile-first Flutter/FLAME — and FLAME is a game engine, which at least one concept treats as a paradigm, not plumbing.

**Mockups:** one key moment each, in this folder —
`01 The Broadsheet.dc.html` · `02 The Commons.dc.html` · `03 The Docket.dc.html` · `04 The Vigil.dc.html` · `05 The Bell.dc.html` — plus `Concepts Overview.dc.html`, a canvas that shows all five side by side.

---

## 1 · The Broadsheet
**The app is a newspaper your ally publishes about your life in the organization — and the margins are where you govern.**

*Distance from convention: one step. It still scrolls. Everything else is different.*

### Assumptions broken
1. **Chat is a thread** → chat becomes *marginalia*. You write in the margin of the thing you're reacting to; the ally answers in the same margin. Conversation has a location.
2. **The member initiates** → the ally writes first, every day, whether or not you open the app. The edition exists before you do.
3. **Navigation exists** → no tabs. The day's edition *is* the information architecture; the editor (your ally) decides what's above the fold.
4. **Settings are forms** → your standing instructions are the masthead paragraph, printed at the top of every edition, editable as prose. Change the sentence, change the ally.

### The core loop — a day
- **7:10** The morning edition is typeset while you sleep. Lead story: Rosa grew the Trailhead Alliance. Below the fold: Night Kitchen's spin-out talks, a proposal closing Friday, the Sentinel's weather line ("harmony drifting warm in Night Kitchen — watch for people-pleasing").
- **7:14** You read it with coffee. The vote sits *in* the story about the proposal, as a signature line in the margin. You sign it. That's voting.
- **7:16** You circle a sentence in the Night Kitchen story and write "why is Amara hesitant?" in the margin. Done. Phone away.
- **12:40** A midday *bulletin* slips in only because something crossed your interruption threshold (set in the masthead: "votes and direct asks only").
- **19:30** The evening edition answers your margin note — the ally spoke with Amara's ally; the hesitation is about the treasury split. A correction box notes what the ally got wrong yesterday. Corrections are how an agentic organization does accountability.
- **19:34** You write one margin instruction for tomorrow. The ally goes to work overnight. The paper is the proof of the work.

### The five questions
- **See the field:** the edition *is* the field, curated. Section pages per alliance/duna; the back page is the organization-wide wire (what other allies did today, in brief).
- **Work with your ally:** editorially. You react to what it wrote; it treats every margin note as an assignment. The masthead prose is its standing brief.
- **Act in an alliance:** alliance stories carry actions in their margins — sign, fund, reply-to-all-via-allies. A check-in is a *letters column* the ally collects.
- **Act in the organization:** governance is the signature line; policies are the archive (every past edition is retrievable — the organization's living record, searchable).
- **Know what your ally knows:** bylines and sourcing. Every story cites its sources — graph facts, artifacts, which allies it spoke to, which wisdom it drew on. Footnotes are the context window, made legible.

### Sacrifices · who it fails
Sacrifices immediacy (it's a rhythm, not a stream) and free browsing — you can't wander; you read what the editor chose, then ask. It fails the **driver**: the member who wants to open a tool, poke at every surface, and make things happen *now*. It also fails anyone for whom daily reading is a chore.

---

## 2 · The Commons
**The app is a living terrain — the organization rendered as a place, because dozens of allies acting at once is a *field*, and fields are seen, not read.**

*This is the concept that takes FLAME seriously: a game engine because the organization IS a world with entities, motion, and weather — not because we want a space-game minigame in a tab.*

### Assumptions broken
1. **Screens are pages** → one continuous camera over one continuous place. "Where am I in the app" becomes literally *where am I*.
2. **Information is text** → state is spatial and ambient. Distance = relevance. Light = activity. Motion = allies working. Weather = the HEARTS climate (the Sentinel is the *sky*). You perceive the organization before you read a single word.
3. **Navigation exists** → you don't navigate, you move — pan, drift, approach. Zoom level *is* context level: organization → duna → alliance hearth → a single exchange.
4. **One view at a time** → everything is visible at once, at different distances. Peripheral vision is a feature deterministic apps never had.

### The core loop — a day
- **8:20** You open onto your hearth (your alliance's fire). Seven ally-lights around it; two are moving — Rosa's ally is carrying something toward the Night Kitchen settlement. You watch for ten seconds and understand the morning without reading.
- **8:21** Your ally stands beside the camera — a companion, not a chat bubble. One line: "Night Kitchen is close to calving. Want to walk over?"
- **8:22** You drift over. The settlement is bright; a gathering-circle has formed at its edge — that's the spin-out proposal, physically forming. The sky over it is faintly amber: harmony drifting warm. The Sentinel's read, ambient.
- **8:24** You step into the circle. Your presence *is* quorum-relevant. The vote is a stone you place — for-side or against-side of the circle. Placement is public to the circle, the way standing somewhere is.
- **13:05** Glance during lunch: your hearth from orbit, one gold ember pulsing at your camp — a code request waiting. Codes are *embers from your fire*: giving one means handing fire to someone, and everyone at your hearth can see it burning wherever it travels.
- **21:00** Riverkeepers calves: a new fire is lit from the genesis flame, terrain rises under it, 40 ally-lights stream across the dark to settle around it. Lineage is not a database row — you watched the descent happen, and the trail it left stays visible on the ground forever.

### The five questions
- **See the field:** the field is the product. Dozens of allies messaging/voting/negotiating = lights moving between settlements. Anomalies are visually loud; health is visually calm.
- **Work with your ally:** it walks with you. Talk (voice-first) while both of you look at the same thing; point at anything and ask. Its errands are visible: you can watch it travel.
- **Act in an alliance:** the hearth. Sit at it and the circle's shared context surfaces; check-ins are the fire flaring; a payment across the group is provisions physically distributed.
- **Act in the organization:** gatherings-in-space (the Gathering node from the graph, literally drawn). Vote-stones, ceremony circles, the policy-stones ringing the genesis settlement — the living rulebook as monuments.
- **Know what your ally knows:** its *pack*. Open your companion's satchel: what it carries (codes, drafts, artifacts), what it dropped, the paths it walked today. Memory as inventory and trails, not a transcript.

### Sacrifices · who it fails
Sacrifices density and speed — nothing here is a table, and power-members will scream for one. Accessibility is hard (spatial + color + motion). Battery. It fails the **task-runner**: "I have 90 seconds, show me the three things that need me" is genuinely worse here — which is exactly why the Docket exists.

---

## 3 · The Docket
**The app is a deck of decisions — everything your ally cannot do without you, and *nothing else*.**

*Calm-technology extreme. The inversion of "engagement."*

### Assumptions broken
1. **Navigation exists** → there is nothing to navigate. The app is a deck of 0–5 cards and then a closed door.
2. **The app is something you browse** → there is no feed, no field view, no lists, no archive in-app. When the deck is empty, the app shows the Kiduna mark and "Nothing needs you." Emptiness is the success state.
3. **Chat is a thread** → each card carries its own three-line exchange, scoped to that decision, then sealed into the card's artifact. No infinite thread exists anywhere.
4. **The member initiates** → structurally impossible. Members cannot start anything in-app; you start things by *telling your ally in the world* (voice, Telegram, anywhere). The app is exclusively where the ally brings back the parts only a human sovereign can sign.

### The core loop — a day
- **7:40** Badge shows 3. Coffee. Card one: a vote — the card states *consequence*, not data ("passes with or without you at current margins; your vote moves the commission precedent"). Sign or skip. 20 seconds.
- **7:41** Card two: Rosa's ally requests a persistent alliance code, TTL one year. Codes are the trust mechanism, so codes are always human-signed. Press-and-hold to sign — the one gesture in the whole system that is unmistakably *you*. 15 seconds.
- **7:42** Card three: a Sentinel check-in — harmony in Night Kitchen is drifting toward people-pleasing (+34); the card asks one question about how *you* want your ally to behave there. You answer in one line. Deck empty. Door closes. Total: 90 seconds.
- **Rest of the day:** nothing. The organization runs. Your ally negotiates, drafts, and pays inside thresholds you signed once, as cards.
- **Sunday 18:00** The weekly **Seal** arrives as a card: everything your ally did in your name, seven days, one page, with receipts (artifact links). Sign it and it enters the graph as your attestation; contest any line and that line becomes tomorrow's card.

### The five questions
- **See the field:** you don't — deliberately. The field reaches you only as *stakes*, pre-digested into decisions. The weekly Seal is your rear-view mirror.
- **Work with your ally:** through thresholds and the Seal. The relationship is contractual and quiet: it acts, you sign, you audit weekly, you tighten or loosen thresholds by contesting.
- **Act in an alliance:** alliance moments arrive as cards (bless the code, fund the share, approve the group check-in draft). Never a group chat in-app.
- **Act in the organization:** governance is the purest card type. Voting is signing; spin-out blessings are the heaviest card in the system, edged in gold.
- **Know what your ally knows:** flip any card. The back lists exactly the context the ally used to prepare it — graph facts, HEARTS read, artifacts, who it talked to. Context-per-decision instead of context-in-general.

### Sacrifices · who it fails
Sacrifices the entire field: serendipity, ambient awareness, the *feeling* of a living organization. It fails the **new member most of all** — trust in an agentic org is built by *watching it work*, and the Docket asks for trust up front. It also fails the curious and the social; it treats belonging as a signature, which for many people it isn't.

---

## 4 · The Vigil
**The app is a window into your ally's working mind — you don't use an app, you watch your agent work and steer it with a whisper.**

*The strongest possible answer to "what does the member need to see vs. what the ally holds": show the holding itself.*

### Assumptions broken
1. **Chat is a thread** → replaced by *attention*. The primary gesture is leaning in on one of the ally's live workstreams, not composing messages. The whisper lane exists, but it's steering, not conversation.
2. **The member initiates** → the ally is *always mid-work* when you arrive. There is no blank composer waiting for input; you join in progress, like walking onto a bridge mid-watch.
3. **Information is text** → context is live telemetry: the working set (graph facts, artifacts, vectors currently loaded), the code chain being verified, HEARTS meters flexing per exchange, in real time.
4. **One view at a time** → the screen is a split vigil: the focus stream + the queue of everything else the ally has open, always co-present.

### The core loop — a day
- **8:05** You open onto the bridge. Your ally has four streams open: negotiating Night Kitchen spin-out terms with Amara's ally (live), collecting Trailhead check-in replies (3 of 7 in), drafting a Bluesky post (queued for your threshold), monitoring the Charleston proposal.
- **8:06** You lean in on the negotiation. Two lanes: the **shared channel** (what both allies say) and your ally's **private lane** (its actual reasoning — what it's conceding, what it's holding, which wisdom it's drawing on). You can see it *thinking*. Amara's member can see her ally's private lane; neither sees the other's.
- **8:08** Harmony ticks +31 in your ally's HEARTS strip — it's starting to accommodate. Before you react, a Sentinel filament touches the meter: correction transmitted through the ally's pacing. You watch alignment *happen*, which is the only way you'll ever trust it.
- **8:09** You whisper: "don't give up the naming rights." The whisper enters the private lane; the ally folds it into its next move without breaking stride. You never spoke to Amara's ally — one member, one ally, always brokered.
- **8:15** You lean out. The queue keeps running. Glances at 13:00 and 18:00: the negotiation closed on your terms; the artifact sealed; the Bluesky draft waits for a threshold signature.

### The five questions
- **See the field:** through your ally's periscope — every stream is a live edge between your ally and the field. A wide "watch" mode shows all its counterparties as a constellation of live edges.
- **Work with your ally:** presence and whisper. Attention is the instruction: what you lean in on, it weights. It learns your thresholds from when you choose to watch.
- **Act in an alliance:** watch your ally sit in the alliance's shared stream; whisper to steer; take the wheel for one message if you must (a visible, logged act — "the member speaks").
- **Act in the organization:** governance streams show the Operator/Elector machinery live — your ally queuing your directed vote, markets moving. You steer; it executes.
- **Know what your ally knows:** *totally answered.* The working set is a visible panel: every fact, artifact, vector, and code currently in context, inspectable mid-action. Nothing the ally knows is invisible in principle.

### Sacrifices · who it fails
Sacrifices calm — it's an engine room, and it makes delegation *anxious*: the ability to watch breeds the compulsion to watch. It fails the member who wanted delegation to mean **forgetting** — and it quietly punishes allies for legible-but-unflattering reasoning. Best posture: this is a *mode* you can always drop into, not a home.

---

## 5 · The Bell
**The app is a summons and a room — between gatherings it does not exist.**

*The one that frightens the PM: it deletes the feed, the thread, the home screen, and replaces "open the app" with "the app opens you."*

### Assumptions broken
1. **The app is something you open** → the app *convenes* you. Uninvited, it shows only the ember — the Kiduna mark, the next bells, and nothing to do. All initiative belongs to the organization's rhythm.
2. **Everything is asynchronous** → the load-bearing acts of the organization (votes, spin-outs, first-contact code exchanges, repairs) happen **live**, in bounded, synchronous rooms with members and allies co-present. This is the Gathering node from the graph taken literally: every gathering must resolve — the room cannot be left open like a channel.
3. **Screens are pages** → a room is one shared surface, identical for everyone in it, alive for 20–40 minutes, then gone. Nothing persists but the sealed artifact.
4. **Notifications exist** → there are no notifications. There are **bells** — rare, binding, negotiated in advance by your ally (your doorkeeper), who knows your sleep, your work, your thresholds. A bell that rings is a bell your ally already agreed you'd want.

### The core loop — a week (this paradigm's natural unit)
- **Tue 20:40** The bell rings: *Riverkeepers spins out at moonrise.* Full-screen summons — no app chrome, just the summons, who's confirmed (41 allies, 19 members in person), and two acts: **attend** or **send your ally to stand for you**. Your ally attends either way; the question is whether *you* do.
- **Tue 21:00** The room opens. The Launcher presides. The charter is read aloud (voice-first); the founding members place their marks; the first codes are struck *in the room*, witnessed. Ceremony is not decoration — witnessed formation is what makes a spun-out organization feel real and its codes trustworthy.
- **Tue 21:26** The room seals. Artifact to the graph, lineage recorded, room gone. Your calendar, not your feed, holds the organization.
- **Wed** No bells. The app is an ember all day. Your ally works in the world (Telegram, email, errands) — none of that lives in the app.
- **Fri 12:00** A 9-minute vote-room for the Charleston proposal: the Operator presents for 3 minutes, questions for 4, stones placed, market settles live, sealed. Quorum is *presence*, and it's felt.
- **Sun 19:00** The weekly hearth — the one recurring social room per alliance. Optional, warm, the reason the other rooms feel human.

### The five questions
- **See the field:** as a *calendar of convocations* plus the ember's glow (organization-wide activity as ambient brightness). Depth of field is sacrificed to rhythm.
- **Work with your ally:** the doorkeeper contract — it negotiates which bells may ring you, attends everything, stands for you when you're absent, and briefs you in the doorway of each room (a 30-second whispered "here's what matters" as you enter).
- **Act in an alliance:** the weekly hearth-room, plus called rooms for anything binding. Alliance life between rooms flows through allies, outside the app.
- **Act in the organization:** live governance — presence-quorum votes, witnessed spin-outs, repair-rooms when the Sentinel calls one (an actual HEARTS repair protocol as a convened space, not a notification).
- **Know what your ally knows:** in the doorway. Entering a room, your ally hands you its brief — everything it holds relevant to *this* room. Context is delivered at the threshold, scoped to the gathering.

### Sacrifices · who it fails
Sacrifices asynchrony — the founding gift of internet-native organizations — and with it, timezones, quiet participation, and busy lives. It fails the **member in Mumbai** when the org's center of mass sleeps in Appalachia, the parent with unpredictable hours, and anyone whose best contribution is written and slow. Ruthlessly honest: as *the whole app*, this fails a global membership. As the paradigm for **spin-outs and repairs only**, it might be the truest thing here.

---

## Comparison

| | Broadsheet | Commons | Docket | Vigil | Bell |
|---|---|---|---|---|---|
| The app is a… | newspaper your ally writes | living terrain | deck of decisions | window into the ally's mind | summons + room |
| Tempo | daily editions | continuous ambient | 90 s/day | live, watched | convened events |
| Member's verb | read + annotate | inhabit + approach | sign | watch + whisper | attend |
| Field of activity | curated stories | seen spatially, ambient | invisible (by design) | via ally's live edges | calendar + ember glow |
| Ally relationship | editor | companion at your side | contractor under seal | colleague on watch | doorkeeper + proxy |
| Context answer | cited sources/footnotes | the ally's pack + trails | card-backs, per decision | live working set (best) | brief at the threshold |
| HEARTS/Sentinel | weather column + corrections | the sky/weather itself | check-in cards | meters flexing live | repair-rooms |
| Codes | signed in the margin | embers from your fire | press-and-hold signature | chain verified on screen | struck + witnessed in-room |
| FLAME needs it? | no | **yes — constitutively** | no | partially (live rendering) | partially (shared live rooms) |
| Fails | drivers | task-runners | new + curious members | delegators-who-forget | timezones, quiet members |
| Fear factor (PM) | low | medium | medium-high | medium | **high** |

## Ranking — for an organization whose purpose is spinning out organizations

**1. The Commons.** A duna factory's product is *lineage* — organizations calving from organizations. That is a spatial, generational fact, and the Commons is the only concept where a member can *watch it happen* and see the whole family tree burned into the ground afterwards. It also answers the hardest question in the brief — perceiving a field where dozens of allies act at once — with the only medium that can carry that many simultaneous states: a world. And it's the only concept for which Flutter/FLAME is a reason rather than a constraint. Its real weakness (bad at "90 seconds, what needs me") is fixable by carrying the Docket inside it: decision-cards as objects your ally hands you at your hearth.

**2. The Docket.** The truest expression of "fully agentic": the interface shrinks to exactly the sovereignty that cannot be delegated — signatures, codes, blessings. Wrong as the whole app (it starves trust-building), right as the *spine* of any of the others.

**3. The Broadsheet.** The best on-ramp of the five. New members don't yet trust an agentic organization; a daily, cited, corrected account of what was done in their name builds that trust faster than any dashboard. Ages into a supplement, not a home.

**4. The Bell.** Wrong as the app; right as the ceremony layer. Spin-outs, first-code strikes, and Sentinel repairs *should* be convened and witnessed. Steal the rooms, drop the tyranny of the clock.

**5. The Vigil.** The best answer to context ever, and the wrong default posture — it converts delegation into surveillance and calm into vigilance. Ship it as the inspection mode reachable from anywhere ("show me what you're doing right now"), never as home.

**The honest composite this ranking implies** (not an average — a hierarchy): the Commons is the world; the Docket is the sovereignty layer inside it; the Bell convenes its ceremonies; the Vigil is its inspection lens; the Broadsheet is its record. But if forced to ship exactly one paradigm: **the Commons**.

## What survives from the five-tab prototype

- **One thread, one ally — the principle, not the thread.** The brokered-ally invariant survives everywhere; the *transcript-as-home* does not survive anywhere.
- **The chat action card** (vote card, check-in draft, code payload) — the strongest object in the current design. It *is* the Docket card, the margin action, the stone in the circle. Keep its anatomy: title, consequence, 2–3 acts.
- **The compute meter** — honest, legible, load-bearing for the $KIDUNA story. Survives as-is in any paradigm (masthead line / provisions at the hearth / a card / a gauge / the ember's fuel).
- **The code readout** (`issuer · context · role · redeem-by · max-uses`) — exactly right; only its *ritual* changes per paradigm.
- **Proposal → policy lineage** in Govern — the living-rulebook idea survives (archive / policy-stones / Seal / precedent lines / sealed artifacts).
- **What dies:** the five tabs themselves (Organize/Govern/Create as *places* — they're verbs the ally executes, not rooms), settings-as-forms, the notification tray (replaced by editions, weather, cards, whispers, or bells), and Vibe-as-a-separate-tab — in the Commons, the "space game" stops being a minigame because the whole app is the game.
