Engineering Stage

ES-106 — Readiness Gate

Verify that implementation can begin with traceability, guardrails, AI-use controls, verification expectations, and review discipline.

Readiness Gate

Implementation Control

Next: Manifest

Stage ES-106

Current Page Readiness Gate

Inputs Readiness package

Outputs ES-107 decision

Role Reviewer / team

← Previous Outputs

Current Readiness Gate

Next → Stage Manifest

ES-106 Readiness Gate

Purpose

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

AI-assisted implementation should not begin until repository workflow, work items, guardrails, AI-use controls, verification expectations, and review expectations are ready.

Completion standard

You are ready to continue when each gate is satisfied or explicitly marked for review.

Gate 1 Design traceability

Question

Does the implementation readiness package trace back to ES-105 design evidence?

Required evidence:

docs/design/ and docs/implementation/implementation_readiness_overview.md

Status: ☐ Yes ☐ Needs review

Gate 2 Branch and workflow plan

Question

Is branch, commit, pull request, review, and merge workflow defined?

Required evidence:

docs/implementation/branch_and_workflow_plan.md

Status: ☐ Yes ☐ Needs review

Gate 3 Implementation work items

Question

Are implementation work items bounded, traceable, and reviewable?

Required evidence:

docs/implementation/implementation_work_items.md

Status: ☐ Yes ☐ Needs review

Gate 4 Implementation guardrails

Question

Are implementation boundaries and prohibited shortcuts explicit?

Required evidence:

docs/implementation/implementation_guardrails.md

Status: ☐ Yes ☐ Needs review

Gate 5 AI-use plan

Question

Are acceptable AI assistance, prohibited AI use, verification expectations, and evidence expectations defined?

Required evidence:

docs/implementation/ai_use_plan.md

Status: ☐ Yes ☐ Needs review

Gate 6 Verification precheck

Question

Are expected tests, checks, and verification activities identified?

Required evidence:

docs/implementation/verification_precheck.md

Status: ☐ Yes ☐ Needs review

Gate 7 Repository readiness

Question

Is the repository ready for implementation work?

Required evidence:

docs/implementation/repository_readiness_check.md

Status: ☐ Yes ☐ Needs review

Gate 8 Review plan

Question

Are implementation review expectations defined?

Required evidence:

docs/implementation/implementation_review_plan.md

Status: ☐ Yes ☐ Needs review

Gate 9 Transition readiness

Question

Does the readiness summary explain why ES-107 can begin?

Required evidence:

docs/implementation/implementation_readiness_summary.md

Status: ☐ Yes ☐ Needs review

Exit criteria

ES-106 is complete when implementation can begin with traceability, guardrails, AI-use controls, verification expectations, and review expectations.

Common pitfall

Do not begin AI-assisted implementation if the team has not agreed how AI-generated code will be reviewed.

Engineering insight

Readiness gates protect implementation from inheriting ambiguity that should have been resolved before coding.

Continue to Stage Manifest

Review the formal ES-106 stage contract before moving to ES-107.

Continue to Stage Manifest →