Scope coordination metadata only · architected so controlled data never moves · no source file crosses the boundary · candidate branch · mock data
Workspace

Flow

Coordination-path builder · local preview

Build the path before a single signal crosses the line.

Lay out the trigger, the summary source, the boundary check, the human gate, and the result. Map view draws the path. Review view shows what stays in scope, what stays locked out, and the result a person opens.

Coordination path
Path IDPATH-COORD-001
PresetChange window
Gate statePending
Write-backBlocked

Boundary-led coordination path

One state, two reads. Map the path, then review the boundary and the result.

Sheet 1 of 1 Change window
Map Trigger to boundary to human gate to result
Controlled data locked out

Active OK Ready Pending Locked

Every path ends at the proof packet

The builder is the loom. The proof packet is what a reviewer and an executive actually open.

Local preview only
Result surface
One reviewed item, source to boundary to gate to close. The drafting step reads the summary and cannot close anything. A named role disposes it.
Gate state: pending · the Close affordance stays disabled until a named role signs.
Proof packet
The result

The reviewed item end to end. Summary, owner role, evidence state, gate, and the disposition a person made.
Shared view
Counterpart coordination

Only the timing and open items both sides agreed to see. No source file, no controlled data.
Signals
The watch queue

The flag feed measured against this path. Held gates, missing evidence, and recurrence, each with an owner role.
Open the proof packet
Coordination metadata only No source files Generic role labels only Source systems remain the authority Candidate branch, mock data