Design Templates¶
Purpose¶
These templates support ES-105 — Detailed Design.
Use this family to prepare implementation responsibly. ES-105 should make interfaces, workflows, data structures, access control, AI interactions, error behavior, exception handling, and technical decisions explicit before implementation begins.
Recommended workflow¶
Architecture Readiness Summary
↓
Design Overview
↓
Interface Design
↓
Data Design
↓
Workflow Design
↓
Access-Control Design
↓
AI Interaction Design
↓
Error and Exception Design
↓
Technical Decision Records
↓
Design Review
↓
Design Readiness Summary
↓
ES-106 Implementation ReadinessCopy location¶
Do not edit the reusable templates directly. Copy completed project versions into:
docs/project-workspace/design/
Template set¶
Design Overview
Summarize design objective, source architecture, priorities, risks, assumptions, and open questions.
02Interface Design
Define contracts, validation rules, authorization, error behavior, evidence, and compatibility expectations.
03Data Design
Define entities, fields, relationships, evidence fields, access restrictions, retention, and governance notes.
04Workflow Design
Define normal, alternate, exception, human review, AI-assisted, and state-transition flows.
05Access-Control Design
Define roles, permissions, protected actions, protected data, denied behavior, and audit evidence.
06AI Interaction Design
Define AI input rules, output handling, review, acceptance, rejection, failures, and prohibitions.
07Error and Exception Design
Define error scenarios, safe behavior, user responses, logging, escalation, retry, and stop conditions.
08Technical Decision Records
Record detailed design decisions, alternatives, rationale, tradeoffs, and verification impacts.
09Design Review
Review design traceability, testability, access control, AI behavior, failures, and implementation readiness.
10Design Readiness Summary
Summarize readiness to begin ES-106 implementation readiness work.
Completion expectations¶
| Question | Evidence |
|---|---|
| What must the design prepare the team to implement? | design_overview.md |
| What contracts connect components? | interface_design.md |
| What data structures, evidence fields, and retention rules are needed? | data_design.md |
| What workflows and states must be supported? | workflow_design.md |
| Who can do what, under what conditions? | access_control_design.md |
| How does AI interact with users, data, workflows, or decisions? | ai_interaction_design.md |
| How should errors and exceptions behave? | error_and_exception_design.md |
| What technical decisions were made? | technical_decision_records.md |
| Has the design been reviewed? | design_review.md |
| Is implementation readiness work ready to begin? | design_readiness_summary.md |
Do not treat design as a lightweight bridge between architecture and code. ES-105 is where unclear architecture becomes implementable behavior, contracts, states, access rules, error handling, AI interaction, and verification obligations.
A strong design is not just buildable. It is reviewable, testable, auditable, operable, and safe to change.