docs(prd): add PRD 0006 — Route alerts so they keep being read - #55
Merged
Conversation
Every module already depends on this one and it does not exist: spend-guard routes through it, code-scanner calls ctx.alert() in all four subsystems. The calls compile and the daemon runs, but nothing decides where an alert goes or whether it is a duplicate. Alert fatigue is the primary failure mode of the whole product — a detection nobody reads is identical to one that never fired, so every module's work on precision is undone if routing sends 400 messages to one channel. The hard parts are deduplication by incident identity and escalation on change rather than repetition; delivery is trivial by comparison. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Specification for the
alert-systemcore module, listed inPRD.mdand not yet specified.Every module already depends on this one and it does not exist: spend-guard routes through it, code-scanner calls ctx.alert() in all four subsystems. The calls compile and the daemon runs, but nothing decides where an alert goes or whether it is a duplicate.
Alert fatigue is the primary failure mode of the whole product — a detection nobody reads is identical to one that never fired, so every module's work on precision is undone if routing sends 400 messages to one channel. The hard parts are deduplication by incident identity and escalation on change rather than repetition; delivery is trivial by comparison.
Spec only — no implementation in this PR.