HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
DecispherHQ
decision-guardian
TypeScript2026–2026
DecispherHQ / decision-guardian

decision-guardian

Shift from passive documentation to active enforcement.

5Distinct people
15Mentions
0Explicit recommenders
71GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Shift from passive documentation to active enforcement.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 3:59:04 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week15 dated mentions

Observed mentions: 2026-02-10 05:15:46 UTC to 2026-03-15 22:06:01 UTC. Weeks start Monday, UTC.

0123452026-02-09 00:00:00 UTC to 2026-02-16 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 commentsFeb 92026-02-16 00:00:00 UTC to 2026-02-23 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-02-23 00:00:00 UTC to 2026-03-02 00:00:00 UTC (exclusive): 3 mentions; 3 submissions, 0 commentsFeb 232026-03-02 00:00:00 UTC to 2026-03-09 00:00:00 UTC (exclusive): 4 mentions; 4 submissions, 0 comments2026-03-09 00:00:00 UTC to 2026-03-16 00:00:00 UTC (exclusive): 5 mentions; 4 submissions, 1 commentsMar 9

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 92026-02-09 00:00:00 UTC2026-02-16 00:00:00 UTC220
Feb 162026-02-16 00:00:00 UTC2026-02-23 00:00:00 UTC110
Feb 232026-02-23 00:00:00 UTC2026-03-02 00:00:00 UTC330
Mar 22026-03-02 00:00:00 UTC2026-03-09 00:00:00 UTC440
Mar 92026-03-09 00:00:00 UTC2026-03-16 00:00:00 UTC541

What Hacker News says

4 sources

Built my first ever open-source project: Decision Guardian

I wanted to share my first-ever open-source project. It’s a tool that surfaces your architectural decisions on pull requests or lets you check them locally using a CLI. You can also set up various rules to trigger actions based on changes in a PR. I’d love to hear any feedback or suggestions on how I can improve it :> Github Action : https://github.com/marketplace/actions/decision-guardian NPM -: https://www.npmjs.com/package/decision-guardian Source code -: https://github.com/DecispherHQ/decision-guardian
2 points · Open discussion

Spotify's take on ADRs is great, but how do you enforce them at scale?

Hey HN, I built Decision Guardian — an open-source GitHub Action and CLI that automatically surfaces architectural decisions as PR comments when code touches protected files. The problem it solves: Spotify published a great post in 2020 about when to write Architecture Decision Records. I followed the advice. My team wrote ADRs. They sat in docs/adr/. Nobody read them before opening a PR. https://engineering.atspotify.com/2020/04/when-should-i-write-an-architecture-deci… The gap isn't documentation — it's surfacing. The right moment to surface a decision isn't onboarding or sprint planning. It's when someone is actively editing the code the decision protects. How it works: 1) Write decisions in a Markdown file (compatible with existing ADRs) 2) Add the GitHub Action to your workflow 3) When a PR modifies protected files, Decisio
Read the rest
n Guardian posts the relevant decisions as a comment automatically Decision format (plain Markdown): <!-- DECISION-DB-001 --> ## Decision: Use Postgres for Billing *Status*: Active *Severity*: Critical *Files*: - `src/db/*/*.ts` ### Context We evaluated Postgres vs MongoDB. Billing requires ACID compliance. MongoDB was rejected — no transaction guarantees. Features worth calling out: 1) Severity levels (Critical / Warning / Info) — can block PRs on critical violations 2) Advanced matching: glob patterns, regex, content-based rules, boolean logic 3) CLI works with any CI (GitLab, Jenkins, CircleCI, pre-commit hooks) 4) Handles PRs with 3000+ files without OOM 5) Idempotent comments — no spam, updates in place 6) Zero external network calls — nothing leaves your GitHub runner 7) 109 tests, ReDoS protection, path traversal protection vs. CODEOWNERS: CODEOWNERS assigns reviewers. This explains why the review matters. Best used together. vs. Danger.js: Danger requires code. This requires Markdown. Non-JS engineers can own their decisions. It's MIT licensed, single-step GitHub Action or npx decision-guardian CLI. Happy to answer questions. Repo: https://github.com/DecispherHQ/decision-guardian
6 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.