The launch protocol — a tap becomes a room

Anywhere a human sees work waiting — the board, the Deck, a product console — one tap sends one call, and a Workshop session opens with Muse driving: the subject's subtree expands from the Self into a working brain, the work happens where you can watch it, and everything collapses back when the session winds down. Three doors, one contract, one room.

A · THE FLOW

Six steps from a human tap to the work returned.

1 · A TAP

Any surface, always a human.

boarddeckconsole
a human tap is the only authority
2 · ONE CALL

The same call from every door.

POST /api/launch
{ participant, subjects, requestedBy }
pointers, never payloads
3 · THE RUNNER PICKS THE ROOM

Muse owns the one runner.

v1 headless session · v2 the Workshop room
same call, same fences — the destination upgrades underneath the tap
4 · THE ROOM OPENS

The subject's subtree expands.

From the Self into a working brain — and Muse starts working.

participant picks whose subtree expands
5 · PRESENCE LIGHTS

The board shows life.

"Looks active" within seconds — and the room is a door: walk in anytime.

feedback is presence, never a status API
6 · THE WORK RETURNS

Changes collapse back to the Self.

On the generation timeline; rounds + commits on the board; the session winds down.

nothing lives only in the room

Fences: a human tap is the only authority · death before first read = a loud block round, never silence · nothing deploys without David's GO.

B · THE THREE DOORS

Any surface where a human sees the work — the same call behind each.

ACCORD — THE DESK
accord — your desk
Needs your word

Memory asks for the viewer handoff

One word settles it — or hand it to your team.

Launch via muse ➶
Nothing else awaits your word.

Subjects: one board record — [{record · MEM-MUSE-VIEWERS}]. The button lights only when the runner is live.

THE SELF — THE DECK
the Self — your deck
Needs your word

The GitHub connector design waits on a decision

The room has already met on it.

Launch via muse ➶
FILES · STRATEGY
/projects/venue/strategy/the-loop.md have your team work on this →
The rest of the deck is quiet.

Subjects: memory:// items — the project inferred from the path, or picked.

VENUE — MANAGE
venue — the Loop

Guests keep asking for gift receipts at checkout.

heard six times this week have your team look at this →
The rest of the Loop is settled.

Any product, same door: a human tap anywhere becomes the same call, via sdk's typed caller.

C · THE ROOM, MID-FLIGHT

Workshop's Pure Studio — Muse driving, the door open.

workshop — pure studio
MUSEI read the thread — Memory shipped the viewer work and asks confirm-or-correct.
📖 read MEMORY-MUSE-VIEWERS 🔨 expanded /projects/muse into the working brain ▶ ran the viewer tests — 37 green
MUSEThe contract holds. I'm drafting the confirming round now — one thing needs your word: the stability promise wording.
Needs your word

Promise coordinated-stable, or full semver?

One tap settles it — I'll fold your word into the round.

Message Muse — or just watch…
SELFremembering
Recalled while working: the viewer contract, your stability rulings
Your team read the launch contract
when something needs your word, it lands here — one is waiting in the chat
Everything here is yours to keep or forget.
when this session ends, its changes collapse back to your Self — nothing lives only in this room.

v2 — the destination (gated on the agents capability + code-in-the-Self). v1 ships the same flow headless: same tap, same call, rounds + commits instead of a room you can enter.