The ADR module numbers your architecture decisions per workspace and manages them through the MADR lifecycle with supersession.
Screens from a running installation
Every decision starts as proposed. A rejected one can be proposed again; deprecated and superseded are final, and superseding always names the decision that takes over.
Context, decision and consequences are required and written in Markdown; alternatives are optional. Who decided, when, which project it belongs to and up to twenty tags sit beside them.
{ } JSON , CSV # Markdown ZIP From proposed to archived, every step is numbered and traceable.
Every decision gets an automatic, sequential number in your workspace (e.g. ADR-007) - easy to reference.
Proposed, accepted, rejected, deprecated or superseded; only the allowed moves are possible, and every change is recorded.
When one decision supersedes another, the link is preserved - the answer to "why did this change?" is always there.
Decisions are authored in Markdown and rendered safely on the server - a consistent, readable view.
Export all records as JSON, CSV or a Markdown ZIP - ready for audit and backup.
How many records an installation keeps is set in its licence; there is no per-record charge.
A proposal that sits for a month is a decision nobody is making. The report counts decisions by status, measures how long it takes to decide and lists proposals older than 30 days.
Every decision numbered, linked and exportable, on your own server.
New modules, release notes and writing on architecture. Leave with one click whenever you like.