The decision role records only context, the chosen option, and consequences, so a reader cannot reconstruct what alternatives were weighed or why the chosen option won. MADR (Markdown Any Decision Records) provides a proven body structure — considered options with per-option pros and cons, the chosen option, and the rationale — that generalizes to any decision, not architecture. Adopt MADR’s body fields as an AsciiDoc labeled-list template; keep the Status, Deciders, Date, and Technical Story header out because the item’s status attribute, its recorded_by relation, and git already express them.

The decision guidance template declares MADR-shaped fields: Context, Options (with per-option good/bad nested), Decision, Rationale, and Consequences. Future decisions record the alternatives weighed, the one chosen, why it won, and the resulting trade-offs.

Markdown files. The core repository’s adr.adoc. Rewriting the existing DEC-001 to DEC-006 items, which stay as historical records. A Drivers field, deferred until decisions need an explicit force list.