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

Three reviews open. Eleven new signals. Four drafts waiting on you.

Everything below is pulled together from the tools your reviewers already use. Each item points to a document by its code, never to the document itself. You decide what closes.

STATE
Production readiness review PHASE D · GATE

Supplier readiness review PHASE C · EVIDENCE

Field-return readiness review PHASE F · HOLD
61%
Readiness across open reviews
7
Open signals awaiting a person
4
Drafts ready for your decision
3
Reviews open this week
Start here Pick a department from "View as" in the rail to see only that team's work, or stay on all departments for the whole program. The counts above follow your choice.
[F] Open your coordination flow
Build and watch the boundary-led path every review travels. The flow shows where each signal enters, where the boundary holds, and the one gate a named role closes.
Map view to build it. Review view to read the in-scope and locked-out lanes. The path ends at the proof packet.

Your reviews

3 open
GATE HOLD A gate review cannot close while its validation evidence is unlinked. Routed to the change advisory reviewer. Open review
EVIDENCE A supplier evidence summary is requested but not yet linked. The review holds until it travels with the review. Open review
RECURRENCE A timing question matches a pattern seen twice before. The reviewer can pull the prior resolution forward. See the watch
WINDOW A field-service window needs a confirmed date before the spare-parts cadence can be set. Open review

Eleven signals brought into view since Friday. Seven still wait on a person. None close without you.

Drafts waiting on you

You always send
Weekly readiness readout for the executive reader
DRAFT · summary only · the drafting step reads the summary and cannot close anything
Review & send
Supplier timing reply for the readiness review
DRAFT · references SCAR by code, never the source file
Review & send
Gate-hold note for the change advisory reviewer
DRAFT · states the missing evidence, holds the gate open
Review & send
Shared coordination note for the supplier counterpart
DRAFT · timing and gate status only, no content shared
Review & send

Today

Work view
09:00 Readiness stand-up · cross-team coordination TEAMS
11:00 Gate review · production readiness GATE D
13:00 Lunch · own time
14:30 Supplier timing sync · evidence still open SCAR
16:00 Mentee check-in · early-career reviewer
18:30 Family dinner PERSONAL · kept private

Where it all lands

Every review, signal, and draft resolves to one reviewed proof packet.
The packet carries the evidence by code, the gate outcome, and the one role that decides closure.
A person closes it. The drafting step reads the summary and cannot close anything.
See the proof packet →

The boundary, plainly

Records referenced by code, never by content.
No controlled config, credentials, or source files cross.
Role labels stand in for real people.