Design Round 7 · Deliverable 6 · The cut · renders canon 2026-07-11 · July 11, 2026

The cut — one real Project, end to end

Every R7 screen marked in or out for the first shippable Studio (6a), and the slice's test stated whole (6b): Moto and one trusted collaborator run the Lightbrush integration end to end — upload, connect, hand off to Claude Code, get work back, record it, and show it in the Field — before anything else ships.

6a

Every screen, marked

in — the first shippable Studio
Project creation — command + receipt01 · 1a
Project card, front and back01 · 1b
Narration + the Project's Scene (on-the-fly grade)01 · 1c
ACTIONS in Field and Chat01 · 1d
Side-by-side + Chat-only postures, the two words02 · 2a, 2d
Desktop HUD — four elements + the thread02 · 2b
Presence, file handoff through the server03 · 3a
Machine-grant card + shared trace (one grant shape)03 · 3b
Registered/unregistered rendering inside a Project03 · 3c
Package: compose · in-flight · return · fail/retry04 · 4a–4d
Acceptance (gold, pending OQ-2's resolution)04 · 4e
Ally maintenance — conversation + three cards05 · 5a
Scene from words + upload path (crafted)05 · 5b, 5c
out — created from within, after
Field-only and overlay postures (side-by-side + Chat-only carry launch)02 · 2a
The generative middle path for Scenes (words + crafted carry launch)05 · 5c
Scene-grade climbing in place (rooms ship at the grade they're born)02 · 2c
Working on each other's machines beyond the one build-grant shape03 · 3b
Codex as second agent (Claude Code proves the seam; the package is agent-agnostic)04 · 4a
Packages initiated by the agent (inbound proposals)04 · 4c
Move authoring beyond one sim-flagged draft (Crew Call is the proof)05 · 5d
Studio on the phone (the pulse ships with the app, not with Studio)07
Untrusted-relationship exchange surfaces (launch is two trusted members)03 · 3c
MCP server wiring UI beyond connected-system chips01 · 1b
6b

The test, run concretely — one page

Moto and one trusted collaborator run one real Project, end to end.

The run, in order, every step on an in-marked screen: create — Moto says it to Taro inside The Ceremony Machine; the receipt lands; the Project has a rough room in the Field (1a, 1c). upload — Moe drops RenderDeck's API notes and Dolly's tile set into the room; they organize into the graph (5c). connect — Dowbot and Dolly register under the Lightbrush agreement; RenderDeck works unregistered, said plainly (3c). hand off — Elias composes package #7 and sends it to Claude Code on his own machine (4a); the room shows it out, breathing, at the edge (4b). get work back — the return unpacks as draft Records, cited to the package (4c); one retry happens, honestly (4d). record it — Elias presses and holds; the work enters the duna's record vouched for by a person (4e). show it in the Field — the adapter Records stand next to Dolly in the room, and Moe walks over to look (3a).

What the test proves — every load-bearing law under real weight: the command-receipt spine, the Scene-per-Project decision, the server-mediated handoff between two trusted people, the package seam in both its states, provenance surviving from upload to acceptance, and one honest failure. If any in-marked screen isn't exercised by this run, it shouldn't be in; nothing out-marked is needed to finish it.

The R6 cut's test was recursion — the invited can invite. The R7 cut's test is production: the workshop can do a real day's work for a real duna with real tools before it learns any second trick. Studio is what we build everything else with; this slice is the moment it starts being that.