Repository navigation
docs: retire dependency-graph-legibility - #375
Merged
Merged
Conversation
byronwall
marked this pull request as ready for review
November 13, 2026 03:00
This was referenced Nov 13, 2026
Merged
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.
Retire the
dependency-graph-legibilityinitiative. All five milestones merged on 2026-10-15 (#50, #56, #58, #60, #61). The planning folderdocs/intent/dependency-graph-legibility/is removed, its lasting facts move into the docs, anddocs/initiative-history.jsongets its closure record.What to do with it
Reference only. Merge to remove a finished plan that could mislead later planning.
docs/CODE_MAP.md(Client: Graph views).Proof
gh pr list --state mergedand the code on origin/main0bfb05ba.validate-sleuth.mjs docs/intent/dependency-graph-legibility --retirement:Validation passedbefore the folder was removed.cd site && pnpm build && pnpm test).Stack: retire shipped initiatives
What splits: Retiring every shipped software-design-sleuth initiative under
docs/intent/, plus status fixes for the ones that only partly shipped.Why it splits: Each retirement deletes one plan and moves its facts. One layer per initiative lets a reviewer check each closure record against its PRs on its own.
Why this split: One PR for all 13 would mix 13 unrelated deletions in one diff. Grouping by area (graph, compare, metrics, data flow) was rejected, because each closure record and its validator run belong to one initiative.
dependency-graph-legibility.compare-ref-picker.unified-navigation.dependency-and-treemap-quick-fixes.dependency-view.pr-compare.metric-system-overhaul.metric-trust.metric-portfolio.git-activity.symbol-graph.python-dataflow.dataflow-logic-visibility.Not retired, with status set in the last layer:
agent-reporting,tsx-dataflow-integration,dataflow-robustness,imported-quality-evidence,dataflow-library-models,dataflow-js-react-solid.🤖 Generated with Claude Code