# Kidunaverse — Design Round 2: The Integrated App

**Brief for Claude Design · July 7, 2026 · from Moto (Kinship Duna) + the co-founder desk**
Read this first, then `the-working-organization.md` (the system canon, v1.2), then `concepts-overview.md` (your own round-1 paradigms), then open the three prototype cuts. The design system is the project you're working in — its `colors_and_type.css` is law (espresso ground, Avenir body, Goudy Heavyface display, IBM Plex Sans callouts, sky = touchable, gold = signature moments).

## 1. What this round is

Round 1 gave us five paradigms (Broadsheet, Commons, Docket, Vigil, Bell) as *alternatives*. We then built three prototype cuts that each grabbed pieces. The result is fragments — five good ideas standing next to each other. **Round 2 is one app.** Not a winner-picking exercise and not a compromise blend: a genuinely integrated design where what was five paradigms becomes moments of a single coherent experience, and where the newest thinking (below) reshapes all of it.

## 2. What has changed since round 1 — the new canon

These five points are decided. Design from them, not toward them.

**a. The Account replaced the newspaper.** No daily editions, no masthead, no publication schedule. The primitive: a continuous ledger of claims, **rendered at the moment of attention**, covering since-you-were-gone, consequence-ordered (never recency), every claim cited, every rendering a correctable artifact, interruptions only past the member's Contract. Full derivation of this and the other seven member moments (Thread, Account, Docket, Seal, Codes, Rooms, Contract, Vigil) is in the working-organization doc, Part II. Those eight are invariants; their skins are yours.

**b. The ally is ambient — one relationship, many doors.** The member's ally hears them *everywhere it has presence*: instructions over Telegram at midnight are as binding as anything typed in the app; a voice note from the trail lands in the same relationship. It also hears **other people** continuously — the alliance group, replies on Bluesky, what a friend said — and it weights everything by source: the member's word is instruction; a code-holder's word is trusted context at their code's scope; a stranger's is unverified signal. It is always building context, on a wide range of topics. The app is not the only door; it's the door with the full instrumentation.

**c. The boundaries are soft. You never have to "know where you are."** We reject typed dunas ("health orgs get the clinical template, festival orgs get the loud one"). Realms are configurations, and moving between them is a *drift*, not a navigation event. Sliding into Service Alliance's realm just means you're using their token and participating in their domain — the ground shifts under you like walking into a different neighborhood, and the tells are ambient: the token in play, the rendering temperature, what your ally is grounded in. No borders, no mode switches, no "you are now entering." Design the gradient.

**d. The Kidunaverse builds things — from the inside, like a MOO.** This is an organization whose members and agents extend the world from within it: spinning out organizations, yes, but also web pages, games, experiments, social media presences, Telegram bots, new experiences — and above all **new agents**. Just as we're rethinking our own experience, the system must help every realm rethink theirs. Making is conversational (you and your ally make things by talking; artifacts appear in the world), and what's made is immediately *inhabitable* by others. The Studio/builder-kit is the deep end (arrives Aug 10); the shallow end — make a page, a bot, an agent, a game night — is everyday life and belongs in this design.

**e. This is a layer on the whole internet — the agentic internet.** The app is not a walled place; it's a lens over a fabric that extends across Telegram, Bluesky, email, the web (via the plugin and embedded codes), and whatever comes next. Presences out there and the home here are the same fabric. Kinship Codes are what carry trust across all of it. Design accordingly: the app should feel like the *home layer* of a member's whole internet life, not a destination competing with other destinations.

## 3. The integration problem, precisely

Here is our current working hypothesis of how the five paradigms compose — challenge it if you can do better, but replace it with something equally explicit:

- **The Thread** (with the Account rendered inside it) is the home — the relationship.
- **The Docket** is the spine — the bounded deck of sovereignty (sign/vote/bless), reachable from anywhere, empty-as-success.
- **The Bell/Rooms** is the ceremony layer — rare, convened, witnessed, sealing.
- **The Vigil** is the lens — inspection on demand from any claim or card, never a home.
- **The Commons** (world/terrain) is the *field* — currently seeded inside Vibe as the game, growing by evidence. In THIS design round, treat the field as the ambient sense-of-place layer: it may be as light as the drift-tells in (2c) or as heavy as a walkable world. Find the right weight for a launch app.

Your job: make these one thing. Concretely answer — what is on screen when a member opens the app? How does the Docket announce itself without becoming a badge-anxiety machine? Where do Rooms live when no room is convened? How does the Vigil open from a claim and close without leaving residue? How does the field express realm-drift (2c) in every surface? What is the app's *idle state* — the screen when nothing needs you and you're just… home?

## 4. Scenes the design must carry (use these, not lorem)

Real content from the working-organization doc, Part V–VI. Your key screens should be drawn from these:

1. **11:40pm, back from two night shifts.** The Account renders two days in nine claims: a proposal needing signature, a study contradicting a BiHome protocol, the Sleep Circle check-in your ally ran (holding the personal questions per your Contract), a presence report (enrolled two via Telegram, held one at the gate), a spin-out room Sunday.
2. **The drift.** Reading a claim from Service Alliance, the member replies, gets pulled into a small piece of work there, spends their token, drifts back — *without one navigation event*. Show the ground shifting.
3. **Dana's code.** Press-and-hold signature; the code travels back out through the member's Telegram presence to Dana, in people-space.
4. **Making something.** A member and ally, in conversation, make a thing — e.g., a sign-up page + Telegram bot for the Fellowship of Play's solstice event, or a small agent that watches tide charts for the river crew. Three exchanges, and it exists, has a code, and others can find/use it. Show birth, not configuration.
5. **The room.** Cosmic Humanity spins out at 7pm — summons, the room itself, nineteen codes struck and witnessed, the seal. Ceremony that feels ceremonial on a phone.
6. **A stranger and a friend.** The ally heard both today — a stranger's unverified claim and an alliance member's request. Show how differently they land (weighted listening made visible in the Account/Vigil).
7. **The Seal.** Sunday's one-page attestation with receipts; contesting a line.

## 5. Deliverables

Produce, in a `/design-r2` output set:

1. **`INTEGRATION.md`** — the composed model: your answer to §3, stated as explicitly as this brief. Include the app's information architecture (or anti-architecture), the idle state, and the drift mechanics.
2. **8–12 key screens** as static HTML mockups, mobile-first (390×844), design-system-native, one per scene above plus the idle/home state — each with a one-paragraph rationale in the file as a comment or sidecar note.
3. **A motion & transition spec** (prose + simple diagrams fine): how drift feels, how the Docket arrives, how a room convenes, how the Vigil opens/closes. We render in Flutter/Flame — say what the engine must be able to do.
4. **The realm-expression system:** exactly which variables a realm's configuration may set on the experience (rendering temperature, type scale mood, field tells, token presence, sound?) and which it may never touch (the eight invariants, the DS's core tokens, the Docket's semantics). This is the "no typed dunas" answer: a continuous expression space, not templates.
5. **The making surface:** the conversational creation flow (scene 4) and where made-things live — how a member encounters something another member made, in-app and out on the agentic internet.
6. **Open questions & disagreements** — where you think our hypothesis in §3 is wrong, say so with an alternative, sharply. Canon in §2 is fixed; everything else is challengeable.

## 6. Anti-goals

No tabs-as-places. No feeds (recency-ordered infinite surfaces). No settings pages (the Contract is prose). No notification tray. No mode switches or "you are now in X" borders. No typed-duna templates. No lorem ipsum, no placeholder org names — the realms are Kinship Duna, BiHome, Service Alliance, Cosmic Humanity, The Fellowship of Play, Party Line, Lui Mutual (all real, all filed). No dark patterns of any kind — emptiness is success, and "nothing needs you" must feel like good news.

## 7. What we'll do with your output

It comes back to the co-founder desk the same night for a final iteration of the team page and a comprehensive rework of the prototype against your design. Aim for decisions we can build, stated so a dev reading LangGraph code and a designer reading Figma both know what to do. Sharp edges over consensus.
