docs: add current-state-inventory-priority.md (priority by downstream leverage)#9
Merged
Merged
Conversation
Supplements AI-discoverability-plan.md §3.4. §3.4 was authored when no repo shipped the Phase-0 contract; with tier-1 + tier-2 onboarded (6 of 9 repos as of 2026-05-10), that table is stale as a priority guide. This doc reframes priority around the actual remaining work and ranks it by *downstream dependents* — not by ease of shipping. Structure: - §2 Current-state inventory (per-repo Phase-0 contract status) - §3 Outstanding work catalogued from parent plan §7 + phase1-plan.md - §4 Dependency graph (ASCII; shows what blocks what) - §5 Priority ranking by downstream-leverage (P1-A ranks #1 with 6 downstream items; tier-3 onboarding ranks #4 despite being "easy" because it doesn't unblock anything) - §6 Recommended execution order — single-threaded sequence + which items to parallelize when bandwidth allows - §6.4 explicit "easy first" trap: ships three quick PRs, leaves nothing unblocked - §7 Concrete recommended next move: ship P1-A as a single coherent PR (cuts the longest dependency chain in front of the entire Phase 1 + 3 + 4 stack) - §8 How to keep the doc in sync (read-then-act discipline) Source files referenced (all on main): - AI-discoverability-plan.md §3.4 — original tier-based framing - phase0-plan.md — completed - phase1-plan.md — to-do, Track A-D layout matches §3-5 here Prose-only gate (make check-docs-prose) green: doc is .md under docs/.
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.
Summary
Supplements `AI-discoverability-plan.md` §3.4. §3.4 was authored when no repo shipped the Phase-0 contract; with tier-1 + tier-2 onboarded (6 of 9 repos as of 2026-05-10), that table is stale as a priority guide.
This doc reframes priority around downstream dependents — not by ease of shipping.
What it adds beyond §3.4
Headline ranking
§6.4 The "easy first" trap, explicitly
§7 Recommended next move
Ship P1-A as a single coherent PR in `.github` — schemas tightened, `task_index.json` split, `tools.json` slimmed, `schema-changelog.md` created (folds P1-X). Then kick off P1-B, P1-C, and T3-* in parallel.
Test plan