Software Design Document

Owner: [Owner]
Status: [Draft/In review/Approved]
Version: [Version]
Target release: [Date or milestone]

Problem or decision: [Problem, decision, or outcome governed by this specification]
Reviewers: [Roles responsible for technical, product, security, and operational review]

1. Design goals

[Component owner]

2. Context and constraints

[Sequence or state transition]

3. Architecture

[Schema and compatibility rule]

4. Component responsibilities

[Timeout and retry behavior]

5. Data model and state

[Authorization boundary]

6. Interfaces and contracts

[Log, metric, and trace signal]

7. Failure handling

[Rejected alternative and reason]

8. Security

[Security: record the behavior, data, constraints, edge cases, ownership, and acceptance evidence that apply to this Software Design Document]

9. Observability

[Observability: record the behavior, data, constraints, edge cases, ownership, and acceptance evidence that apply to this Software Design Document]

10. Alternatives and decision

[Alternatives and decision: record the behavior, data, constraints, edge cases, ownership, and acceptance evidence that apply to this Software Design Document]

Review and Change Control

[Reviewers, decision owner, unresolved questions, linked evidence, approval date, and change history]