ES-108 Navigation¶
Purpose¶
This page explains how to move through ES-108 and where review and integration artifacts belong.
ES-108 connects implementation evidence to testing and verification.
ES-108 path¶
README
↓
navigation.md
↓
engineering_context.md
↓
activities.md
↓
evidence.md
↓
outputs.md
↓
readiness_gate.md
↓
stage_manifest.md
↓
ES-109
Repository areas used in this stage¶
docs/engineering/ES-108/ guidance
template-library/integration/ reusable review and integration templates
examples/lmu-coicp/integration/ completed reference examples
docs/integration/ project-specific review and integration evidence
What to copy¶
Copy templates from template-library/integration/ into docs/integration/, then complete them for your project.
Do not edit the original templates.
Expected project artifacts¶
docs/integration/code_review_overview.md
docs/integration/pull_request_review_record.md
docs/integration/traceability_review.md
docs/integration/ai_implementation_review.md
docs/integration/guardrail_review.md
docs/integration/integration_plan.md
docs/integration/integration_verification_record.md
docs/integration/review_findings.md
docs/integration/integration_decision_record.md
docs/integration/integration_readiness_summary.md
Traceability expectation¶
Every reviewed change should connect to at least one implementation work item, requirement, design artifact, implementation evidence record, verification result, pull request or commit, and integration decision.
Untraceable changes should not be integrated without explanation.
Common Pitfall
Do not merge first and document later. Integration evidence should exist before or as part of the integration decision.