# OPEN QUESTIONS — DESIGN ROUND 8
**The sharpest disagreements, one per item · July 13, 2026**

---

## OQ-1 — The Relationship room's threshold

**Built:** a Relationship renders as a small room exactly two can stand inside (01 · 1c), per-Organization, entered like any Scene.
**The alternative:** the Relationship as a card only — a two-sided object you read, never a place you go — with the room reserved for relationships that have accumulated real material.
**Why I built the room:** canon says a Relationship is a node, not an edge, and the Field's law is that nodes you can be *in* are places. A card-only rendering makes the most intimate object in the system the only major node without a somewhere.
**The honest counter:** most Relationships are thin; an empty room per Relationship per Organization is a lot of empty rooms, and emptiness reads as failure. A threshold rule (room earned by material, like the Project ruling) would rhyme with ruling 1. **Flag if:** the graph shows most Relationship Records staying under a handful of entries — then adopt the earned-room rule and let the card be the default rendering.

## OQ-2 — TV's household visit under one membership

**Built:** one member signs in; the room watches and visits together under that membership, Host ally guiding where the member's grants end (05 · 5a, 5c).
**The alternative:** TV as strictly the signed-in member's view — others in the room are incidental viewers the system doesn't model at all.
**Why I built the household visit:** it's true to what a TV is (a shared glass), it gives the Host ally a real job on the fourth surface, and it makes "visiting together" a designed act instead of an accident.
**The honest counter:** it puts the member's membership between strangers-on-the-couch and the world — a party guest can walk the member's Scenes at ten feet. The grants boundary holds (nothing personal renders; the Host ally takes over past the member's public rooms), but the *social* boundary is the member's problem. **Flag if:** counsel or members read household visiting as an accountability gap — then TV falls back to public and Community-level Scenes only when more than the member is plausibly present (which TV cannot detect, hence the flag).

## OQ-3 — Express registering pages "as [Organization]" with a gold hold

**Built:** domain/page registration from Express is press-and-hold gold, because the Organization's registry is part of its authoritative Record (04 · 4c).
**The alternative:** registration as a light, receipted act — gold reserved for votes, founding, and acceptance into the Record narrowly construed (work products, proposals), with the registry treated as operational data.
**Why I built gold:** ruling 2's line is "work enters or changes the Organization's authoritative Record." A domain claim is exactly such a change — it alters what every Express user everywhere sees about that domain, under the Organization's name. If that isn't Record-touching, the word has no edge.
**The honest counter:** registrations could be frequent for an active Organization, and R7's own worry (a ceremony repeated hourly devalues every ring) applies. **Flag if:** registration volume in practice looks like acceptance volume did — then registry writes become light and the Record's "authoritative" boundary gets drawn tighter, explicitly.

## OQ-4 — The bench as Live's future inspection grammar

**Built:** the bench (02 · 2c) is Studio-only; Live holds "at my desk later" (ruling 4 honored).
**The alternative:** ship a read-only bench on the phone now — cards viewable, nothing changeable, no acceptance — so members can at least *look* at an agent from anywhere.
**Why I kept it desk-only:** a read-only bench on the phone is the top of a slippery slope R7 already named: the moment inspection feels complete on the phone, mobile acceptance follows, and the phone still can't walk a diff. Shipping the look without the verbs invites the verbs.
**The honest counter:** the bench's cards are citations and sentences — exactly what the phone renders best — and "I can see my ally's Contract anywhere" is a trust feature, not a workshop feature. The Contract card specifically may deserve phone visibility even if the full bench doesn't. **Flag:** recommend the Contract card (alone) become viewable in Live one round after launch, and the rest of the bench wait for a real mobile inspection grammar.

## OQ-5 — The container chip on every Express page

**Built:** the chip is always present in the toolbar — "in Kinship Duna" by default (04 · 4b).
**The alternative:** the chip appears only when Express has something to say (a registered resource on the page, an act in progress), staying invisible during plain browsing.
**Why I built always-present:** the chip is the accountability statement — *on whose behalf* — and an accountability statement that appears only sometimes teaches members it's optional. The default's visibility is also Kinship Duna's honest presence in the product: everything unclaimed happens somewhere.
**The honest counter:** a permanent brand chip in the toolbar reads as advertising to people who installed a utility, and "in Kinship Duna" over ordinary reading may feel like being watched even though reading is never recorded. **Flag if:** early members report the chip as surveillance-feeling — then it collapses to the mark alone during plain browsing and speaks only when touched.
