Example
The audit starts with common gates such as preflight, approvals and QA, while optional gates can add risk, stock and supplier evidence. This prevents an irrelevant process from blocking a job solely because that module was never used.
v99 · ENTERPRISE PLATFORM
Run a deterministic audit before a job is released.
Check that required local evidence exists and is not explicitly blocked, then show exactly which gate prevents READY.
Interactive module
Release Readiness Audit
Audit result—
Required0
Unresolved0
Practical workflow
Choose the gates that apply, then fail closed
Interpretation
For each selected gate, missing evidence is different from failed evidence. Missing produces REVIEW because the decision is incomplete; a stored blocking state produces HOLD because there is known negative evidence that must be resolved.
Boundary
READY appears only when every selected mandatory gate has evidence and none of it is explicitly blocked. That conservative behavior is intentional: readiness is a release claim, not an average score.
Why this module exists
Production context around the calculation.
Missing is different from failed
The audit distinguishes evidence that has never been recorded from evidence that explicitly failed.
Applicability prevents false blockers
Not every job needs roll media, palletization or booklet binding. Required gates are selectable.
READY is intentionally conservative
The audit only turns ready when every selected mandatory gate has acceptable evidence.