I3268 — The published plan has an impact page whose graph and sortable table agree and name the commit they were read at

Generate /plan/impact/ on the site from plan.impact over every issue: a sortable, filterable table (id, milestone, wave, status, immediate unlocks, transitive reach, remaining blockers) and the graph via site/graph.js; row and node select each other; a no-JS table is the fallback.

BLOCKED wave 1 · p2 · implementation profile · parallel safe

Part of the-plan-says-what-a-fix-unblocks — The plan says what finishing an issue unblocks, and why each blocked issue is blocked.

Blocked. This issue cannot start until I3267 is done. The status is derived from that, not declared.

Objective

Why

Owner order 2026-10-17 for an interactive per-issue graph and an aggregated table ranked by impact. Proposed in ADR 0195 (What accepting an issue unblocks is answered by one counterfactual evaluator over the plan graph) (proposed; it carries no authority until the owner accepts it). Sources: chatgpt-majordomus:c284#5.

Current state

site/graph.js and diagrams.js draw graphs; no page ranks issues by unlock.

Desired state

The page is generated by derive; its numbers carry the source commit and graph fingerprint.

Scope

site/graph.js
site/data/generated/plan.json
apps/majordomus-cli/src/generate.rs
scripts/generate-site-data
lib/plan_json.awk
site/templates/plan-section.html
site/templates/dag.html

Dependencies

I3267READY One read-only evaluator says what accepting an issue would unblock, from plan.next's own readiness rules

Acceptance criteria

The table and graph name the same commit and fingerprint as plan.impact on the CLI
A new issue appears with no edit but its record

Validation

scripts/derive-check
majordomus plan validate

Evidence required

case_the_impact_page_agrees_with_the_cli

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started: —
verified: —
completed: —

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3268.yaml. Read it back with majordomus plan show I3268.