tacigent-readiness-gates

What problem does it solve?

Tacigent's Readiness Gates define a common sub-protocol that stage skills refer to, ensuring outputs carry a readiness status and that downstream stages know how to consume or transition based on that status. It prevents naive handoffs and standardizes how readiness is evaluated across stages.

Core Features & Use Cases

• 3-state readiness: ready, needs_validation, not_ready, with explicit criteria for downstream handoff, validation, or additional work.
• Deterministic judgement: a defined ordering where blocking conditions, validation debt, and defaults control transitions.
• Reopen and escalation: safe revalidation, reopens and downgrades when evidence changes, and escalation handling to avoid blocking downstream.
• Stage discipline: default strictness per stage group (intake/problem/solution more permissive; design/build/pitch stricter; marketing cautious), with stage-specific thresholds defined by the respective stage skills.

Quick Start

Apply the readiness classification to a stage output to determine whether it can be handed off to the next stage.