Add docs/ROADMAP.md recording what is next - #106
Merged
Conversation
The repository had no durable record of planned work. There is no ROADMAP, TODO, BACKLOG or CONTRIBUTING file, and the deferred alert commit/version layer existed only in conversation. docs/specs/brief-v2.md also told contributors to put migration notes in EXECUTION_PLAN.md, a file that has never existed in this repo. ROADMAP.md records the next major change (splitting build_basic_alert into build/verify/commit, immutable alert_versions, and dependency edges) with enough context to restart cold: the specific problems in the current code, the shape of the fix, the acceptance test, and the guard rails that protect frozen v1 decision behavior. It also records the v1.3 known limitations with a concrete follow-up each, the smaller unscheduled hardening items, and what stays deferred until Hardstop performs external actions or emits generated prose. Links it from the README, points the CHANGELOG limitations at it, and redirects the dangling EXECUTION_PLAN.md reference. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Why
The repo had no durable record of planned work — no
ROADMAP,TODO,BACKLOGorCONTRIBUTINGfile anywhere. The deferred alert commit/version layer existed only in conversation and in notes outside the repository, so it would not survive closing a terminal.Separately,
docs/specs/brief-v2.mdinstructed contributors to put migration notes inEXECUTION_PLAN.md— a file that has never existed here.What
docs/ROADMAP.mdrecords:build_basic_alert()doing construction, verification and persistence in one function; correlated alerts mutated in place; evidence written after the DB commit), the shape of the fix, the bounded acceptance test, and the guard rails that protect frozen v1 decision behaviorcreate_allper session, the silent_safe_raw_batch_hashdowngrade, tests writing into the realoutput/, untrackedconfig/sources.yamlimpact_scoredirectly, so source credibility changes the calculated business impact of the same physical eventAlso links it from the README, points the CHANGELOG's "Known limitations" at it, and redirects the dangling
EXECUTION_PLAN.mdreference.Verification
Docs only — no source changes. Verified that every relative link in the touched files resolves, and that each code path the roadmap names still exists and contains the symbol referenced.
🤖 Generated with Claude Code