Evidence flow

Build one readiness path from source status to human gate to result packet.
What gets shared The status and a short summary can be shared. Controlled files stay protected. A reviewer approves first. Candidate workspace, mock data only.
Path builder · local preview

Build the path before a single signal crosses the line.

Lay out the source status, the boundary check, the human gate, and the result. Map view draws the path. Review view shows what stays in scope, what stays protected, and the result a reviewer opens.

Readiness path
Path IDPATH-READY-001

PresetProduction readiness

Gate statePending

Write-backBlocked

Boundary-led readiness path

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

Sheet 1 of 1 Production readiness
Map Source to boundary to human gate to result
Controlled data locked out

Active OK Ready Pending Locked

Every path ends at the readiness packet

The builder shows the path. The readiness packet is what a reviewer and an executive actually open.

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