# OPEN QUESTIONS — DESIGN ROUND 6
**Sharpest disagreements and decisions-where-silent, one per item · July 10, 2026**
Format: the spec position → the disagreement or gap → the alternative(s), with reasons. Where I disagreed, I built what the spec says and flagged here (the law of the prompt).

---

**OQ-1 · The invitation page discloses the Profiler's work pre-account — how much?**
v5.2 says the invitation "reads like it was written by someone who knows his work." I built the disclosure sentence plus an expandable source list (01 · 1d), on the argument that a system that studied someone and said nothing is surveillance with manners. **Disagreement risk:** counsel may prefer less pre-account surface (the source list names third-party platforms before any terms are accepted). **Alternative:** disclosure sentence only, list deferred to first session. I'd resist going below the sentence — the sentence *is* the ethic.

**OQ-2 · Is extending a code the signed act, or is *sending the profile* a second one?**
Spec is silent. I bound profile + code into one signature (01 · 1c): one act, one ceremony, because the profile only leaves the member's hands inside the invitation. **Alternative:** separate signatures (one for "hold this profile," one for "extend this code") — cleaner audit lines, but two gold moments in one flow cheapens both, and the profile alone never crosses a boundary. Decided: one signature; flagging because the receipts differ.

**OQ-3 · Ki's page offers conversation to strangers (04 · 4b) — is that canon?**
Roles §1 says Ki serves all guests; nothing says kidunaverse.com/ki is conversational pre-account. I decided it is — it gives the curious-uninvited an honest door that isn't a marketing page, and it exercises the Guest path with zero new machinery. **Alternative:** static page, conversation only after a code. Safer for abuse/cost (Compute is metered — who pays for stranger chats?), and that cost question is real: propose a tight rate-limited guest scope funded by Kinship Duna as the answer, not silence.

**OQ-4 · Voice in Live at launch.**
Surfaces §2 folds voice into Chat as one conversation; nothing requires it in Live for August 10. I cut it (05): the band is text in Live at launch. **Disagreement with my own cut:** steering while reading is genuinely worse than steering while listening; if any post-cut capability earns early re-entry, it's Live voice-out (ally speaks, member taps). Flagged as the first from-within build.

**OQ-5 · The mode products' door on mobile web vs. native app.**
Spec is silent on whether kiduna.one / kiduna.live are PWAs, wrappers, or just the web app pinned to a mode. I designed them as the same Flutter build opened in one mode (their whole point is sameness), which implies web-first at launch. **Alternative:** native store listings for each — discoverability, but three store products before August 10 is real cost for two products whose message is "this is the same app." Decided: web at launch, one listing (Kiduna) in stores.

**OQ-6 · The relationship card renders on the /handle page (04 · 4a) — duplication risk.**
The two-sided card now lives in Chat, Studio (R5), and the directory. I rendered it verbatim in all three because it is the *one* object both sides own — but the spec should name a single source of truth for its copy (the graph record) and say the three surfaces are renders, not copies. Gap, not disagreement; one sentence in Foundation would close it.

**OQ-7 · "Four others here" — does the generative room count people?**
Sentinel law forbids meters on people; the fallback's sentences state presence counts ("four others here"). I kept counts — presence is a fact of a room, not a score of a person — but drew the line at *named* distance ranks or activity totals. Flagging because the boundary (counting presence yes, counting behavior no) is mine, not the spec's.

**OQ-8 · Foundry Scrip's name inside Kidunaversity.**
R4 named the practice currency in-fiction; v5.2 renames the mode and the experiences but not the fiction. I carried "Foundry Scrip" (02 · 2d). If Kidunaversity's fiction is now a university rather than a foundry, the name should follow the fiction — "Bursar's Scrip" — before the strings ship. Pure naming; zero mechanics.

**OQ-9 · Handle collisions with the outside world.**
Handles are unique across members and allies — but kidunaverse.com/swyx will exist the day he joins, while @swyx also names accounts elsewhere. Spec is silent on whether the directory ever asserts sameness ("this is the @swyx of X/GitHub"). I kept the pages silent on outside identity except where a registered social account (Express, out of this cut) proves the binding. Decided and flagged: **no unproven sameness claims in the directory, ever** — it's the registered/unregistered law applied to identity.

**OQ-10 · The Studio cut hides nothing — but R5's Studio canvas exists.**
Builders reading the kit will see R5 canvas 03 (the full Studio) next to R6's three-job cut and may build toward the wrong one. The MANIFEST states precedence (cut first, R5 as horizon), but the spec site should mark R5 · 03 "design horizon — not the August 10 build" in its own header. Editorial gap; one line.
