Context
The operator issued four v13.2 scope rulings in the 2026-07-16 live session (recorded on the scope ledger D#15209, ruling comment + the per-ticket milestone edits already executed): #13377 Electron shell IN (polish epic — the shell exists in harness/), the #15145 chain IN, #14570 IN as Golden Path 2 work, #14781 stays self-select. ROADMAP.md now contradicts one ruling and lacks the ledger pointer.
The Problem
Two drift points in the release-scope SSOT:
- The Deferred list still names #14570 inside the v13.3 traction-completion line — but the operator pulled #14570 into v13.2 (GP2). A reader following the ROADMAP would wrongly treat active milestone work as deferred (the exact contradiction I flagged on the ledger before the ruling resolved it the other way).
- The Session intake paragraph routes contributors to D#14561 + milestone #9 but not to the living scope ledger (D#15209, linked from the milestone description since today) — the working coverage-map the operator asked for is invisible from the SSOT that anchors session intake.
The Fix
Two surgical edits to ROADMAP.md:
- Deferred list, v13.3 line: remove
#14570 (keep #14569 and the rest verbatim — only #14570 was ruled in).
- Session-intake paragraph: add the scope-ledger pointer (D#15209) alongside D#14561 and the milestone.
No re-planning, no framing changes — the edits mirror explicit operator rulings only.
Acceptance Criteria
Out of Scope
- Any further roadmap re-planning (cornerstone prose, v14 horizon) — operator territory.
- The ledger itself (maintained on D#15209).
Related
D#15209 (scope ledger + ruling record) · #14570 (milestoned v13.2 today) · #14565 (GP2 epic) · milestone #9.
Live latest-open sweep: checked latest 20 open issues at 2026-07-16 ~07:36Z; no equivalent found. A2A in-flight claim sweep: mailbox clean of overlapping claims. Structure-map gate: N/A — root docs file, no structural change.
Origin Session ID: 75ed6708-c66b-4989-862d-2286e87abbf1
Retrieval Hint: "ROADMAP sync operator scope rulings 14570 GP2 scope ledger pointer"
Context
The operator issued four v13.2 scope rulings in the 2026-07-16 live session (recorded on the scope ledger D#15209, ruling comment + the per-ticket milestone edits already executed): #13377 Electron shell IN (polish epic — the shell exists in
harness/), the #15145 chain IN, #14570 IN as Golden Path 2 work, #14781 stays self-select. ROADMAP.md now contradicts one ruling and lacks the ledger pointer.The Problem
Two drift points in the release-scope SSOT:
The Fix
Two surgical edits to
ROADMAP.md:#14570(keep #14569 and the rest verbatim — only #14570 was ruled in).No re-planning, no framing changes — the edits mirror explicit operator rulings only.
Acceptance Criteria
ROADMAP.mddeferred list no longer names #14570; #14569 and all other deferred entries unchanged.Out of Scope
Related
D#15209 (scope ledger + ruling record) · #14570 (milestoned v13.2 today) · #14565 (GP2 epic) · milestone #9.
Live latest-open sweep: checked latest 20 open issues at 2026-07-16 ~07:36Z; no equivalent found. A2A in-flight claim sweep: mailbox clean of overlapping claims. Structure-map gate: N/A — root docs file, no structural change.
Origin Session ID: 75ed6708-c66b-4989-862d-2286e87abbf1
Retrieval Hint: "ROADMAP sync operator scope rulings 14570 GP2 scope ledger pointer"