ES-106 Navigation¶
Purpose¶
This page explains how to move through ES-106 and where implementation readiness artifacts belong.
ES-106 connects design evidence to controlled implementation execution. Navigation must preserve that transition: design defines what should be realized; implementation readiness defines how coding may begin responsibly.
ES-106 path¶
README
↓
navigation.md
↓
engineering_context.md
↓
activities.md
↓
evidence.md
↓
outputs.md
↓
readiness_gate.md
↓
stage_manifest.md
↓
ES-107
Repository areas used in this stage¶
engineering/ES-106/ guidance
template-library/implementation/ reusable readiness templates
examples/lmu-coicp/implementation/ completed reference examples
docs/implementation/ project-specific implementation readiness evidence
What to copy¶
Copy templates from template-library/implementation/ into docs/implementation/, then complete them for your project.
Do not edit the original templates.
Expected project artifacts¶
docs/implementation/implementation_readiness_overview.md
docs/implementation/branch_and_workflow_plan.md
docs/implementation/implementation_work_items.md
docs/implementation/implementation_guardrails.md
docs/implementation/ai_use_plan.md
docs/implementation/verification_precheck.md
docs/implementation/repository_readiness_check.md
docs/implementation/implementation_review_plan.md
docs/implementation/implementation_readiness_summary.md
Traceability expectation¶
Every implementation work item should trace to at least one design artifact, architecture decision, requirement, work package, risk, verification expectation, or evidence obligation.
Untraceable coding should be challenged before implementation begins.
Do not create a branch and start coding before selecting and tracing the first work items. A branch is not a plan.
Navigation through ES-106 should feel like a readiness checklist for disciplined implementation, not a delay before coding.