adr-format-y-statement

A Y-Statement in architectural decision records is a concise, single-sentence format that captures context, concern, chosen option, alternatives, quality goals, and trade-offs. It enforces a fixed structure to standardize lightweight decision tracking across project teams.

You write concise ADRs by applying the Y-Statement format, which transforms architectural decisions into a single structured sentence. You provide the required context, concern, chosen option, rejected alternatives, and trade-offs to create a quick, consistent decision record.

Use a single-sentence ADR format for project-level or module-level architectural decisions when your team needs quick, consistent decision records without the overhead of lengthy documentation. It suits lightweight ADR needs where capturing context and trade-offs rapidly is the priority.

Required fields in a Y-Statement architectural decision record include context, concern, chosen option, rejected alternatives, quality goal, and trade-offs. It also prompts for an optional rationale to further justify the architectural decision.

Yes, you can use the Y-Statement format for module-level architectural decisions. It is specifically designed for both project-level and module-level ADR creation, enabling rapid generation of standardized decision records across different scopes of your architecture.

The best way to standardize architecture decision documentation across teams is to enforce a fixed Y-Statement structure. By using provided templates and examples, teams generate consistent, lightweight decision records that consolidate context, options, and outcomes uniformly.