ES-108 Activities¶
Purpose¶
This page guides code review and integration work for ES-108.
Complete these activities for each integration increment. Iterate when review findings require implementation correction, design clarification, or additional verification.
Activity 1 — Create code review overview¶
Create:
docs/integration/code_review_overview.md
Use:
template-library/integration/code_review_overview.md
Summarize what is being reviewed, related work items, PRs, source requirements, design evidence, implementation evidence, review scope, and known risks.
Review context evidence.
Activity 2 — Complete pull request review record¶
Create or update:
docs/integration/pull_request_review_record.md
Use:
template-library/integration/pull_request_review_record.md
Record reviewer, author, PR or branch, files changed, checks run, comments, and review decision.
Pull request review evidence.
Activity 3 — Perform traceability review¶
Create or update:
docs/integration/traceability_review.md
Use:
template-library/integration/traceability_review.md
Confirm implementation traces to work items, requirements, design, guardrails, verification notes, commits, and PRs.
Traceability review evidence.
Activity 4 — Review AI-assisted implementation¶
Create or update:
docs/integration/ai_implementation_review.md
Use:
template-library/integration/ai_implementation_review.md
If AI materially assisted implementation, review the AI-use log, generated code areas, verification performed, accepted output, rejected output, and remaining risks.
If AI was not used, state not applicable.
AI implementation review evidence.
Activity 5 — Review guardrails¶
Create or update:
docs/integration/guardrail_review.md
Use:
template-library/integration/guardrail_review.md
Check whether implementation preserved guardrails from ES-106.
Guardrail review evidence.
Activity 6 — Create integration plan¶
Create:
docs/integration/integration_plan.md
Use:
template-library/integration/integration_plan.md
Define merge order, dependencies, required checks, rollback approach, post-merge validation, and follow-up responsibility.
Integration planning evidence.
Activity 7 — Complete integration verification record¶
Create or update:
docs/integration/integration_verification_record.md
Use:
template-library/integration/integration_verification_record.md
Record tests, checks, manual verification, evidence-flow checks, access-control checks, and post-merge results.
Integration verification evidence.
Activity 8 — Record review findings¶
Create or update:
docs/integration/review_findings.md
Use:
template-library/integration/review_findings.md
Record issues, severity, owner, resolution, whether rework is required, and whether risk was accepted.
Review finding evidence.
Activity 9 — Record integration decision¶
Create:
docs/integration/integration_decision_record.md
Use:
template-library/integration/integration_decision_record.md
Record whether the change is accepted, accepted with follow-up, rejected, or deferred.
Integration decision evidence.
Activity 10 — Complete integration readiness summary¶
Create:
docs/integration/integration_readiness_summary.md
Use:
template-library/integration/integration_readiness_summary.md
Summarize readiness for ES-109.
Transition evidence from integration to testing and verification.
Recommended working order¶
code_review_overview.md
↓
pull_request_review_record.md
↓
traceability_review.md
↓
ai_implementation_review.md
↓
guardrail_review.md
↓
integration_plan.md
↓
integration_verification_record.md
↓
review_findings.md
↓
integration_decision_record.md
↓
integration_readiness_summary.md
AI may assist review by comparing code against design, identifying missed tests, checking for guardrail violations, and drafting review findings. Engineers make the integration decision.
Do not let AI review replace human review. AI can help find issues. It cannot accept responsibility for integration.