Read the browser-local signals created across Print Prep Lab and expose what is missing before release: file identity, preflight, cost, capacity, imposition, quote assumptions and QA blockers. The board does not create evidence that was never recorded.
✓ Reads local signals✓ Reasons shown✓ No automatic sign-off
01 · RELEASE SIGNAL
Current operations state
Overall stateREVIEWwaiting for signals
Required signals0 / 7connected categories
Known blockers0from recorded checks
REVIEW
Build the operational record.
Run the linked tools and save their signals. This board will summarize them without changing the underlying job data.
02 · SIGNAL BOARD
Evidence by category
Release discipline
The board is designed to show missing evidence, not manufacture certainty.
Missing is different from failed
If no cost or capacity signal exists, the board marks that category missing rather than calling the job bad. A missing commercial model may be irrelevant for a personal print but essential for a production quote. Mark a category Not required only when that exclusion is deliberate; the board removes it from the readiness denominator without pretending the evidence exists.
Blockers come from explicit records
A failed Preflight result, a capacity window that is too short, an imposition with no fit, or an unresolved QA Blocker can place the board on HOLD. The dashboard does not infer physical print defects from a filename or guess whether an unrecorded proof passed.
Freshness matters
Signals include timestamps where the underlying tool supports them. Re-run critical calculations after trim, quantity, provider, stock or deadline changes. A mathematically correct snapshot can still be obsolete if the job specification moved.