# INTEGRATION — One App
**Kidunaverse Design Round 2 · answer to brief §3 · July 7, 2026**
Pairs with: `MOTION-SPEC.md` · `REALM-EXPRESSION.md` · `MAKING-SURFACE.md` · `Key Screens.dc.html`

---

## 0. The sentence

**The app is one surface — the Thread — standing on a living ground.** Everything that was five paradigms is now a *posture* of that one surface, not a place inside it. There is no navigation because there is nowhere to go: there are only things that rise from the ground (the Account, the deck, a summons), things that slide over it (the Vigil), and the ground itself shifting under your feet (drift).

The Commons did not lose. It became the floor everything else stands on — demoted from world to *weather*, which is the weight a launch app can carry (see Disagreement 1).

## 1. The composed model — five paradigms, five postures

| Round-1 paradigm | What it becomes | How it appears |
|---|---|---|
| **Thread** (+ Account) | the surface itself | always; the only scrollable thing in the app |
| **Docket** | a physical object *in* the Thread | a paper edge at the bottom of the screen — present only when cards exist, literally absent when empty |
| **Bell / Rooms** | a takeover that rises from the ground | only when convened; between rooms it is one line on the horizon, nothing more |
| **Vigil** | a lens over the Thread | pulled from any citation or card-back; recedes without residue |
| **Commons** | the ground | an ambient Flame layer under everything: realm temperature, activity glow, weather tint, ember moments |

One consequence worth stating plainly: **the app has no chrome that is always true.** The header is the relationship (ally name + grounding line + meter whisper). Everything else earns its pixels by being real *right now* — a deck that exists, a room that is convening, a rendering that just composed. When nothing is real, the screen is the ground, the ember, and the composer. That is the design.

## 2. Information architecture (anti-architecture)

```
THE GROUND  (Flame layer: realm temperature · activity glow · weather)
   └─ THE THREAD  (one scroll; the relationship)
        ├─ pinned above the top edge: THE CONTRACT (pull down to read/edit; prose)
        ├─ inline, at attention: THE ACCOUNT (since-you-were-gone renderings, sealed as artifacts)
        ├─ inline, rare: claims, corrections, seals, made-things, horizon lines
        ├─ resting on the bottom edge: THE DECK (only when cards exist)
        └─ the composer (text + voice; one door among many — Telegram etc. are equal doors)
   ├─ OVERLAY: THE VIGIL (lens; from citations only; no chrome entry point)
   └─ TAKEOVER: A ROOM (summons → room → seal → gone)
```

Reachability rule: **everything the system can do is reachable by saying so.** The gestures (pull the deck, pull the contract, open a lens) are accelerators for things you could ask for in words. There is no function that exists only as chrome.

The record (every rendering, every correction, every seal) is asked for, never browsed to: "show me the record" / "what did you tell me about Dana in June." Search is conversation.

## 3. The idle state — what "nothing needs you" looks like

Open the app on a quiet Tuesday and you get, top to bottom:

1. **The ground, breathing.** Espresso, warmed by whichever realm you last stood in, moving on a ~60s cycle. Alive but not asking.
2. **The ember** — the Kiduna mark, small, centered in the upper third, glowing faintly with organization-wide activity (brighter = more happening; it is a pulse, not a meter).
3. **One line from your ally**, present tense, specific, and good news: *"Nothing needs you. Eleven workers are on your behalf tonight — the Sleep Circle check-in collects itself Thursday."* Never generic. Never "all caught up!" — that is a feed's absolution, and there is no feed.
4. **The horizon line**, only if something is convened: *"Cosmic Humanity spins out Sunday, 7pm."*
5. **The meter whisper** in the header: `$87.40 · converts at launch`.
6. **The composer.** The relationship is always open.

No deck (no cards → no deck). No unread anything. No Account rendering — attention with nothing consequential since last look produces *silence*, or at most one line. Emptiness costs the member zero taps to confirm; it is the whole screen saying it.

## 4. How the Docket announces itself — without badge anxiety

Five rules, all load-bearing:

1. **Words, not numerals.** The deck's tab reads "Two things need only you," in the ally's voice. Never `②`, never red, never a count in the app icon.
2. **The deadline lives in the sentence,** not in an urgency treatment: "one closes Friday." Time pressure is stated once, honestly, then left alone.
3. **Physical, not chromatic.** The tell is a paper edge resting on the bottom of the Thread — an object in the world, with a shadow, at rest. It does not pulse, bounce, or accumulate.
4. **Bounded.** The deck holds ≤5. The Clerk holds further cards back and the ally says so in prose when it happens ("I'm holding two more until these clear"). An unbounded pending pile is an inbox; we don't build inboxes.
5. **Absent when empty.** No greyed-out deck, no "Docket (0)". The success state is the object not existing. Signing the last card plays the door-close: the deck slides away and the ground brightens for a breath.

Announcement inside a rendering: a claim that has a card ends with `→ card waiting` in gold — the claim explains, the card decides, and the same object is never both.

## 5. Drift mechanics — the ground shifting

Drift is a **grounding state**, not a navigation event. At any moment the ally is grounded in some realm's configuration (or between two — the state is a blend, and blends are legal). What changes when grounding changes:

- **the ground temperature** — the Flame layer crossfades toward the realm's hue (≤12% mix into espresso; see REALM-EXPRESSION.md),
- **the token in play** — the chip by the composer: `$KIDUNA` → `$SRVC`, crossfading as the work becomes theirs,
- **the grounding line** under the ally's name: *"grounded in Service Alliance,"*
- **the rendering voice** — the next thing the ally says is in that realm's register,
- **type mood** — display scale and spacing shift within the sanctioned range (Cosmic Humanity is airier; Fellowship of Play is denser and louder).

What triggers it: reading deep into another realm's claim; replying to it; accepting a piece of work there; a room convening there. The transition is 800–1400ms, eased, **interruptible and reversible** — scroll back up to your own realm's claims and the ground follows you back. You can always ask "where am I standing?" and get a sentence, but nothing ever *tells* you unprompted. No border, no toast, no breadcrumb. The tells are ambient and redundant — any one of them is missable; together they are the neighborhood.

Sovereignty note: drift never changes what your signature means, what the deck contains, or your Contract. You drift; your invariants don't.

## 6. Where the rest lives

- **Rooms, unconvened:** one horizon line in the idle state and a claim in the Account. That's all. No calendar surface, no room directory (see Disagreement 3).
- **The Vigil:** opens from any citation, any card-back, or by asking ("show me what you're doing right now"). It slides over the Thread, which stays visible, dimmed, beneath — you never left home. It closes by swipe or by lean-out and leaves **nothing**: no history entry, no "recently watched," no state on next open. Watching must stay free or it becomes a duty.
- **The Contract:** pinned above the Thread's top edge — pull down to read it whole, edit it in place as prose; the ally confirms its reading of the change. It is also quoted back inline wherever it binds (the gold-edged quote block).
- **The Seal:** arrives weekly as a page inside the Thread. Sign it (press-and-hold) or contest a line (the line becomes tomorrow's card). Receipts on every line.
- **Weighted listening, made visible:** what the ally heard from other people renders with its weight typographically — your word as instruction (gold, quoted), a code-holder's word at its scope (sky, scope stated), a stranger's word dim and explicitly `unverified signal · held`. The weights are inspectable in the Vigil (the working set names its sources).
- **Making:** three conversational exchanges → a thing exists, with a code. See MAKING-SURFACE.md.

## 7. Disagreements with §3 (sharp, with alternatives)

**1. The Commons should not ship as a walkable world — and not because of scope.** A terrain you walk *re-introduces explicit place*, which §2c just abolished: a map answers "where am I," and the canon says you should never need to ask. The field's launch weight is exactly the ground layer: temperature, glow, weather, embers. **Alternative if we're wrong:** the world ships as a *made thing* — a place some member and their ally built that you can visit (scene-4 machinery), not as the app's frame. The frame stays the Thread.

**2. "The Docket is the spine, reachable from anywhere" — no.** A permanent global affordance is chrome; chrome that is sometimes gold trains checking, and we're rebuilding the anxiety machine with better typography. The deck should be **absent when empty** and physically present when real. If sovereignty needs a guarantee of reachability, that guarantee is the ally ("anything waiting?") — the relationship is the spine, not a UI element.

**3. The Bell is not a "layer" — it is an event.** Between rooms there should be *no rooms UI at all*: no calendar tab, no "upcoming ceremonies" surface. One horizon line, negotiated past the Contract, is the entire footprint. A ceremony layer you can browse is a ceremony inflated.

**4. The Vigil should be structurally incapable of becoming a posture.** Beyond "never a home": no entry point in chrome, no persistence across app-opens, no notification ever originating from it. If a member watches daily, that is a signal the *Account* is failing them — the Renderer should learn from lens-opens (which claims get inspected) and render better, so watching decays naturally.

**5. One challenge to the hypothesis's framing: the home is not the Thread — it is the ground with the Thread on it.** Most opens will be idle opens. If we design the Thread as home, we will fill silence with text. Designing the *ground* as home makes emptiness beautiful instead of blank, and it is where the field earns its keep.

## 8. What a dev and a designer each take from this

**Dev (LangGraph):** grounding is a state on the ally session (realm id or blend + weights), set by the Renderer/conversation router, streamed to the client; the client owns only the crossfade. Deck presence = Clerk's bounded queue length > 0. Vigil = read-only subscription to the ally's working set, scoped per Part II §8. Idle line = a Renderer product with a "quiet" register. Nothing here requires new workers; it maps onto Ledgerkeeper/Renderer/Clerk/Sealer as specced.

**Designer (Figma):** one artboard family (the Thread) + three overlays (deck, lens, room) + one Flame layer with a 7-realm swatch set (see REALM-EXPRESSION.md). No nav components, no tab bar, no badge styles, no empty-state illustrations beyond the mark. The signature gestures: pull-down = Contract, pull-up = deck, press-and-hold = signature, swipe-down = lens away.
