# OPEN QUESTIONS — DESIGN ROUND 7 **The sharpest disagreements, one per item · July 11, 2026** --- ## OQ-1 — A Scene per Project **Built:** every Project is born with its own bounded Scene at the on-the-fly grade (01 · 1c). **The alternative:** Projects as objects *inside* the Organization's one Scene — a workbench in the org's hall rather than a room of its own. **Why I built the Scene:** a Project has exactly a Scene's properties — its own members, grants, things, and edges. Rendering it as a room makes the grant boundary walkable and gives collaboration a *somewhere* (presence, 03 · 3a, needs a floor). The cost is proliferation: an org with thirty Projects has thirty rooms. I'd rather solve that with how the org's grounds arrange rooms than flatten the Project into furniture. **Flag if:** orgs are expected to run many tiny short-lived Projects — then the workbench model may read better and the Scene should be earned at some size. ## OQ-2 — Acceptance and the gold ceremony **Built:** acceptance of returned agent work is press-and-hold with full gold — the fourth signed act (04 · 4e). **The alternative:** acceptance as a recorded act with light; gold reserved for a Project's completion or for acceptance into the *duna's* record specifically. **The argument for gold:** it's the moment machine output enters an organization's record under a member's name. The signature signs the vouching, not the work. If the highest-volume consequence Studio produces isn't signed, provenance becomes decoration. **The honest counter:** launch canon holds gold to three acts; acceptance may happen dozens of times a day, and a ceremony repeated hourly devalues every other ring. A middle path exists: gold only when acceptance crosses a boundary (draft → the duna's record; Moto's signature) and light for work-in-progress acceptance (Elias's). **Recommendation:** ship gold, watch frequency for two weeks of real use, adopt the middle path if the ring dulls. ## OQ-3 — The spacebar-hold peek **Proposed** (02 · 2d, MOTION §1): hold space to glance at the other rendering, release to return; nothing commits. It's the one Studio-only gesture this round adds, and it violates a soft rule — every other gesture in the system exists on every surface. **Alternative:** no peek; the two words are cheap enough. I kept it because desktop work has a genuine "just checking" rhythm that phones don't, but I hold it loosely: cut it before letting it become precedent for surface-specific gesture growth. ## OQ-4 — Studio on the phone **Built:** nothing called Studio ships on the phone. The Project reaches members through Kiduna Live — the room, the narration, ACTIONS, package news — and five acts stay at the desk (compose, wire, grant, accept, upload), with "at my desk later" as the phone's verb for holding an intention (07 · 7a). **The alternative:** a minimal mobile Studio — at least acceptance, since press-and-hold is native to touch and the signature is not a money act (web-only law covers money, not signatures). **Why I refused it:** acceptance without the ability to genuinely inspect what's being vouched for is signature theater. The phone can't walk a diff yet. **Flag if:** Live's Field gains a real inspection grammar for returned work — then mobile acceptance becomes honest and should be revisited, and I've said so on the canvas. ## OQ-5 — The server's one refusal **Built:** the server refuses a returning package only when its contents fall outside the package's own declared scope, stated as which constraint the return violated (04 · 4d). **The alternative:** the server never refuses; everything returns as drafts and members judge. **Why the refusal stays:** the package's constraints are the member's stated will; a return that exceeds them landing even as draft normalizes overreach and trains members to skim. One structural check, stated plainly, keeps "constraints" a real word. But it *is* the only place in R7 where the system says no on a member's behalf, which is why it's flagged rather than assumed. ## OQ-6 — Where ACTIONS accumulate **Built:** no queue, no inbox, no badges; standing ACTIONS live at their objects, on the Project card, and behind "what's waiting on me" (01 · 1d). **The alternative:** a docket surface — the Concepts round drew one — listing everything waiting across all Projects. **Why conversational-only:** the docket is one aggregation away from becoming a task manager with counts, and counts are how meters sneak back in. But a member leading four Projects will ask "what's waiting on me" every morning; if the ally's answer to that is always a well-formed list, we've built the docket anyway and should admit it as a card (not a surface) in R8. --- ## Resolutions · 2026-07-12 (Moto) 1. **Scene per Project — RESOLVED, refined:** every Project gets a stable Scene identity and Field address, but a fully materialized room is earned only when the Project's scale or complexity makes it useful. 2. **Acceptance and gold — RESOLVED, middle path:** gold only when work enters or changes the Organization's authoritative Record; work-in-progress acceptance remains light. 3. **Spacebar-hold peek — RESOLVED: cut.** 4. **Studio on the phone — RESOLVED:** no Studio on phones for v0; Live may handle participation and simple approvals, while complex diffs, grants, uploads, and acceptance remain in Studio until Live supports genuine inspection. 5. **The server's refusal — RESOLVED, strengthened:** the Package manifest is enforced; violating returns remain quarantined as evidence, with the exact violated constraint stated, but cannot enter the Project as drafts or Records. 6. **Where ACTIONS accumulate — RESOLVED:** the Docket is admitted as a projection of standing ACTIONS, not a separate inbox; ACTIONS stay attached to their objects; no badges.