adrkit

Decision memory for human- and agent-authored plans — architecture decision records that are machine-readable, enforceable in CI, and legible to agents, without leaving git.

Most ADR tooling is a markdown template and a static site generator. That records a decision; it doesn’t make the decision do anything. adrkit treats a record as typed data with a markdown body and adds one field — affects — so a tool can answer “which decisions govern this pull request?” and put the answer where the next decision is being made.

An 80-second tour, from the terminal to the pull request to the GitHub Copilot app:

https://github.com/user-attachments/assets/2ab466f9-53f0-4274-a87c-98d8d5e5ecdf

A still of the final screen. Select it to watch the 15-second recording.

On a pull request, the governing-decisions Action posts that answer as a comment, and GitHub Copilot code review can cite a record because it lives in the repository:

mbeacom/adrkit-demo is a small payments-ledger repository with these pull requests open, a managed ARB queue issue, and recordings of every command.

Decision governance, not generated documentation

Generated knowledge systems answer “how does the system work now?” adrkit answers “what did people decide, what alternatives were rejected, and which decisions govern this change?” ADR-0037 sets that boundary: generated knowledge systems are downstream read models of adrkit’s human-reviewed decision corpus, never decision authorities.