Decision Guardian – surface architectural context
Content-aware rule matching on diffs surfaces only relevant decisions, not noise.

Markdown-driven decision surfacing with Trie-based matching outperforms Slack threads.
Engineering teams managing code context and institutional knowledge
ADRs (Architecture Decision Records) via git · Slack decision bots · Confluence knowledge bases
What is Decision Guardian?
Engineering teams lose critical context when senior engineers leave, architectural decisions go undocumented, or new developers modify sensitive code without understanding the why behind it. Decision Guardian solves this. You write decisions once in simple Markdown files. When a PR touches protected code, Decision Guardian automatically surfaces the relevant context as a PR comment or CLI output (based on pre-defined rules).
Github Marketplace -: https://github.com/marketplace/actions/decision-guardian NPM -: https://www.npmjs.com/package/decision-guardian
Would love your feedback :>
Content-aware rule matching on diffs surfaces only relevant decisions, not noise.
CODEOWNERS for architectural decisions—surfaces why code exists before breaking it.
Markdown ADRs automatically surface on PRs — prevents institutional amnesia at scale.
Auto-comments architectural context on PRs via GitHub Actions; solves real institutional knowledge loss.
Surfaces ADRs in PRs when protected files change, unlike static Log4brains.
Surfaces decisions on PRs, but tooling assumes decisions are documented—doesn't solve the core problem.