ES-107 Navigation¶
Purpose¶
This page explains how to move through ES-107 and where implementation evidence belongs.
ES-107 connects implementation readiness to code review and integration. Navigation must preserve that transition: readiness defines the controls; implementation produces code and evidence under those controls.
ES-107 path¶
README
↓
navigation.md
↓
engineering_context.md
↓
activities.md
↓
evidence.md
↓
outputs.md
↓
readiness_gate.md
↓
stage_manifest.md
↓
ES-108
Repository areas used in this stage¶
engineering/ES-107/ guidance
template-library/implementation/ reusable implementation templates
examples/lmu-coicp/implementation/ completed reference examples
docs/implementation/ project-specific implementation evidence
Expected ES-107 project artifacts¶
docs/implementation/implementation_log.md
docs/implementation/ai_assistance_log.md
docs/implementation/work_item_completion_records.md
docs/implementation/implementation_evidence.md
docs/implementation/verification_notes.md
docs/implementation/implementation_decision_records.md
docs/implementation/implementation_risk_updates.md
docs/implementation/implementation_summary.md
Traceability expectation¶
Each implementation increment should connect to an implementation work item, design artifact, requirement, guardrail, verification activity, commit or pull request, and AI-use evidence when applicable.
Untraceable implementation should be challenged before review.
Do not hide important implementation decisions inside commit messages only. Commit messages are useful, but significant decisions need durable project evidence.
Navigation through ES-107 should feel like a controlled path from selected work item to reviewable implementation evidence.