ES-105 Navigation¶
Purpose¶
This page explains how to move through ES-105 and where design artifacts belong.
ES-105 connects architecture evidence to implementation readiness. Navigation must preserve that transition: architecture defines responsibility; design makes responsibility implementable.
ES-105 path¶
README
↓
navigation.md
↓
engineering_context.md
↓
activities.md
↓
evidence.md
↓
outputs.md
↓
readiness_gate.md
↓
stage_manifest.md
↓
ES-106
Repository areas used in this stage¶
engineering/ES-105/ guidance
template-library/design/ reusable design templates
examples/lmu-coicp/design/ completed reference examples
docs/design/ project-specific design evidence
What to copy¶
Copy templates from template-library/design/ into docs/design/, then complete them for your project.
Do not edit the original templates.
Expected project artifacts¶
docs/design/design_overview.md
docs/design/interface_design.md
docs/design/data_design.md
docs/design/workflow_design.md
docs/design/access_control_design.md
docs/design/ai_interaction_design.md
docs/design/error_and_exception_design.md
docs/design/technical_decision_records.md
docs/design/design_review.md
docs/design/design_readiness_summary.md
Traceability expectation¶
Design decisions should trace to at least one of:
- architecture component;
- architecture decision record;
- functional requirement;
- nonfunctional requirement;
- constraint;
- risk;
- evidence flow;
- AI-control boundary;
- access-control rule;
- workflow requirement.
Untraceable design decisions should be challenged.
Engineering control point¶
ES-105 is complete only when design evidence is specific enough for ES-106 to evaluate implementation readiness without relying on memory, assumptions, or private conversations.
Do not scatter design decisions across chat, issue comments, or code comments only. Important design choices need durable repository evidence.
A design that cannot be found later cannot guide implementation, testing, maintenance, or review.