tacigent-readiness-gates

A readiness gate classifies stage outputs into ready, needs_validation, or not_ready states to determine when downstream stages can proceed, preventing naive handoffs by enforcing standardized evaluation criteria.

Track blocking risks and missing coverage by specifying evaluation criteria including outstandingChecks, disconfirmingEvidence, and carryForwardRisks within the readiness classification to control validation and rework flows.

Readiness gates handle evidence changes by applying safe revalidation rules that downgrade status to needs_validation or not_ready, triggering automatic reopens and escalation handling to avoid blocking downstream stages.

Default strictness varies by stage group: intake, problem, and solution stages are more permissive, design, build, and pitch stages are stricter, and marketing is cautious, with specific thresholds defined by each stage skill.

Avoid using a three-state readiness model for simple linear handoffs that require no validation debt tracking or blocking risk assessment, as the deterministic judgment ordering and escalation rules add overhead suited for complex stage dependencies.