Skip to content

Engineering Stage

ES-107 — Readiness Gate

Verify that AI-assisted implementation is traceable, verified, documented, and ready for code review and integration.

Readiness Gate
Implementation Review
Next: Manifest

ES-107 Readiness Gate

Purpose

This readiness gate verifies that ES-107 is complete and ES-108 can begin responsibly.

Code review and integration should not begin until implementation evidence is sufficient for reviewers to understand what changed, why it changed, how AI was used, and how the work was verified.

Completion standard

You are ready to continue when each gate is satisfied or explicitly marked not applicable.

Gate 1Work item traceability
Question

Can each implementation increment be traced to a work item, design artifact, and requirement?

Status:☐ Yes☐ Needs review
Gate 2Implementation log
Required evidence

docs/implementation/implementation_log.md

Status:☐ Yes☐ Needs review
Gate 3AI assistance log
Required evidence

docs/implementation/ai_assistance_log.md, when AI materially assisted implementation.

Status:☐ Yes☐ Not applicable☐ Needs review
Gate 4Work item completion
Required evidence

docs/implementation/work_item_completion_records.md

Status:☐ Yes☐ Needs review
Gate 5Verification notes
Required evidence

docs/implementation/verification_notes.md

Status:☐ Yes☐ Needs review
Gate 6Guardrail preservation
Required evidence

docs/implementation/implementation_evidence.md

Status:☐ Yes☐ Needs review
Gate 7Implementation decisions
Required evidence

docs/implementation/implementation_decision_records.md, when important implementation decisions were made.

Status:☐ Yes☐ Not applicable☐ Needs review
Gate 8Risk updates
Required evidence

docs/implementation/implementation_risk_updates.md

Status:☐ Yes☐ Needs review
Gate 9Transition readiness
Required evidence

docs/implementation/implementation_summary.md

Status:☐ Yes☐ Needs review

Exit criteria

ES-107 is complete when implementation is traceable, AI use is verified where material, verification notes exist, guardrails are checked, implementation decisions are recorded when needed, risks are updated, and reviewers have enough evidence to begin ES-108.

Common pitfall

Do not proceed to code review if reviewers must reverse-engineer what happened.

Engineering insight

A readiness gate protects review quality by making implementation evidence available before review begins.

Continue to Stage Manifest

Review the ES-107 stage contract, then continue to ES-108.

Continue to Stage Manifest →