v0.3.1

Changes

• Clarify that repeating the same ADC directive label is allowed e.g for multiple decisions.
• Clarify that ADC directives are optional and that adopters do not need to use all four labels.

This patch release changes wording only; directive semantics are unchanged.

v0.3.0

Makes ADC adoption agent-first. The quickstart now begins with a one-line prompt asking a coding agent to adopt the convention, then defines the expected repository changes: copy a published release locally and reference it from the repository agent instructions. This release adds compatible adoption guidance without changing directive semantics or existing requirements.

v0.2.0

Strengthens how agents handle existing Agent Decision Comments. The quickstart now treats governing ADCs as active constraints and requires explicit justification for changes, while the detailed guidance requires invariant changes to be justified. This release adds compatible guidance without changing existing directive semantics.

v0.1.1

Clarifies how Agent Decision Comments apply to public APIs and generated documentation. Consumer-facing guarantees remain in ordinary API documentation, ADCs explain the rationale behind those guarantees and API shapes, and implementation-only rationale stays in source comments.

v0.1.0

Initial public release of the Agent Decision Comments specification. Defines the decision, invariant, assumption, and tradeoff directives, along with their format, scope, review workflow, versioning policy, and adoption guidance.