chore: track the architecture-views.md staleness as issue #50, and measure the drift - #51
Merged
Merged
Conversation
…asure the drift The debt lived only in CLAUDE.md, docs/project-context.md and the sprint notes. This project's own rule is that GitHub Issues are the single source of truth for work items outside the BMad story flow, so a milestone task tracked in prose was the one most likely to be forgotten — and it already had been: the milestone the notes named (the close of Epic 4) passed on 2026-07-25 without it. Both notes now point at #50, and both carry what was MEASURED rather than what was assumed: · the drift is two commits, 59 insertions / 11 deletions — `7d4b1bd` (the D65 post-completion section) and `da23f9f` (the source-tree diagram freshness pass). NEITHER touches a decision body, a dissent or a renunciation, which is what the views file gathers, so the content drift is smaller than the hash suggests; · there is NO generator. `cargo xtask` exposes only `ci`, whose views-hash check merely VERIFIES the frontmatter hash. "DERIVED — never edit by hand" has always meant "not independently of the source", not "a tool does it"; · the bulk of the real work is re-checking that the 883-line view file's line citations still resolve, since architecture.md grew by 236 lines. project-context.md's note also stops naming Epic 4's close as the milestone: a sentence that describes a plan the project did not carry out reads as a fact and sends the next reader to the wrong place. No code changes. `cargo xtask ci` green. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
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.
The
architecture-views.mdregeneration debt lived only inCLAUDE.md,docs/project-context.mdand the sprint notes. This project's rule is that GitHub Issues are the single source of truth for work items outside the BMad story flow — so a milestone task tracked in prose was the one most likely to be forgotten, and it already had been: the milestone the notes named (the close of Epic 4) passed on 2026-07-25 without it.Both notes now point at #50, and both carry what was measured rather than what was assumed.
What the measurement changed
cargo xtaskexposes onlyci, whoseviews-hashcheck merely verifies the frontmatter hashThe two commits are
7d4b1bd(the D65 post-completion section) andda23f9f(the source-tree diagram freshness pass, D64 fallout). The bulk of the real work is re-checking that the 883-line view file's line citations still resolve, sincearchitecture.mdgrew by 236 lines — the file's whole contract is that it POINTS.project-context.md's note also stops naming Epic 4's close as the milestone: a sentence describing a plan the project did not carry out reads as a fact and sends the next reader to the wrong place.No code changes.
cargo xtask cigreen (ℹ views-hash STALE, exit 0 — still correct, and still the signal).🤖 Generated with Claude Code