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.
Can each implementation increment be traced to a work item, design artifact, and requirement?
docs/implementation/implementation_log.md
docs/implementation/ai_assistance_log.md, when AI materially assisted implementation.
docs/implementation/work_item_completion_records.md
docs/implementation/verification_notes.md
docs/implementation/implementation_evidence.md
docs/implementation/implementation_decision_records.md, when important implementation decisions were made.
docs/implementation/implementation_risk_updates.md
docs/implementation/implementation_summary.md
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.
Do not proceed to code review if reviewers must reverse-engineer what happened.
A readiness gate protects review quality by making implementation evidence available before review begins.