Gates
What it is
Section titled “What it is”Gates are quality checkpoints at sprint boundaries. Before a sprint can be marked complete, it must pass through a gate evaluation that checks defined criteria, gathers code evidence, and routes through an approval workflow.
Why it matters
Section titled “Why it matters”Gates enforce delivery standards. They prevent untested or incomplete work from advancing and create a documented record of what was verified at each sprint boundary — critical for client-facing engagements where audit trails matter.
Key concepts
Section titled “Key concepts”- Gate card:
GateCardsummarizes the gate with status, criteria completion, and evaluation results - Criteria checklist:
CriteriaChecklistlists pass/fail criteria that must be satisfied - Code evidence section:
CodeEvidenceSectionlinks gate criteria to actual code changes and test results - Sprint gate evaluator:
SprintGateEvaluatorruns AI-assisted evaluation against the criteria - Approval panel:
ApprovalPanelmanages the approval workflow with approve/reject actions - Detail route: Full gate detail page for deep inspection and sign-off
- New gate route: Dedicated page for creating a new gate with custom criteria
How to use it
Section titled “How to use it”- Navigate to [Program] > Gates.
- View gate cards showing status across sprints.
- Click a gate card to open the detail page.
- Review the Criteria Checklist — each criterion shows pass/fail status.
- Inspect the Code Evidence section for linked code changes.
- Run the Sprint Gate Evaluator for AI-assisted evaluation.
- Use the Approval Panel to approve or reject the gate.
- Create new gates from the gates page to define custom checkpoints.
Data model
Section titled “Data model”This feature uses the following tables:
sprintGates— Gate record with criteria, status, evaluation results, and linked sprintevidence— Code and test evidence linked to gate criteria