# Software design record

Document the internal design of a component so maintainers can understand its boundaries and trade-offs.

## Architecture

Component responsibility: [purpose]. Inputs and outputs: [contracts]. Upstream and downstream dependencies: [services]. Draw or link the flow from [event] to [result].

## Data and failure behavior

State model: [states and transitions]. Persistent data: [storage and ownership]. For [failure], define [retry or recovery] and [observable signal]. Note ordering and concurrent use if relevant.

## Design review

Alternative considered: [design and trade-off]. Validate with [test or prototype]. Operational owner, rollout plan and decision date: [details].
