Roadmap: v13.2 is an org release; the DockLayouts rewrite gates it

Context

Operator ruling (in-session, 2026-08-28): the DockLayouts greenfield rewrite — Discussion #17818's graduation AND its implementation results — lands before the v13.2 release. DockLayouts is a flagship item. And since the repository split (the Fleet Manager app now lives in neo-agent-institution, the Agent OS in neo-agent-brain, the agent process substrate in neo-agent-skills), v13.2 is in effect an org-spanning release: its gate behavior crosses repos, while ROADMAP.md still reads as engine-internal.

The Problem

ROADMAP.md is the session-intake SSOT for release scope ("start from this roadmap"), and it currently under-describes two load-bearing facts:

1. Cornerstone 2 (Qt-parity docking) does not name its actual delivery path. The greenfield rewrite (Discussion #17818: hard cut to a decomposed src/dashboard/dock/ package, semantic tab activation, resizable edge zones, neo.dock.* wire family) is now the operator-ruled route to the docking cornerstone, and it is release-gating. An agent or contributor routing from the roadmap today lands on the pre-split epic shape and cannot see that the rewrite gates the release.
2. The org span is nowhere stated. The release gate already includes behavior owned by other repos (the cockpit UI arc, One Reality's Docker topology), and the docking rewrite itself has an explicit engine → Institution consumer sequence. Readers still parse v13.2 as a single-repo release.

The Architectural Reality

• ROADMAP.md holds next-release scope only; cornerstone table rows carry anchors + done signals; stewards are named in the "How it runs" paragraph (#15798 → @neo-fable, #14442 → Grace).
• Discussion #17818 is pre-quorum ideation: three peer cycles are in (Emmy, Vega ×3, @neo-fable domain-owner cycle), OQ1–OQ8 pending author-side resolution, STEP_BACK sweep claimed by Vega. The roadmap edit therefore records sequencing (graduation + implementation gate the release — the operator ruling) and stays outcome-neutral on the open OQs; the implementation epic replaces the Discussion anchor once it files.
• Cross-repo release ordering for the rewrite is already scoped inside the Discussion (its OQ8: engine/Institution pin-and-merge sequence — release ordering, not compatibility layers). The roadmap names the span; it does not re-design the mechanics.
• Engine milestone 9 stays the engine-side tracking surface; other repos track their own issues (transferred anchors browser-redirect).

The Fix

Surgical edit to ROADMAP.md only:

1. Org-release paragraph in the v13.2 intro: name the four-repo span (engine, neo-agent-institution, neo-agent-brain, neo-agent-skills), keep engine milestone 9 as the engine tracking surface, and state the consumer-repo pin discipline (pin engine by commit until consumer PRs land).
2. Cornerstone 2 row: anchor the greenfield rewrite (Discussion #17818 → its implementation epic at graduation) beside #13158; done signal gains "the rewrite ships before the release: engine hard cut + Institution consumer PR land"; demo signals stay.
3. Steward line: record cornerstone 2's rewrite path steward (@neo-fable, domain owner) beside the existing steward entries.

Acceptance Criteria

• AC-1: ROADMAP.md names v13.2 as org-spanning with the four repos and the consumer-pin discipline, in one paragraph, without redesigning release mechanics.
• AC-2: The cornerstone-2 row anchors Discussion #17818 (or its successor implementation epic) and states that the rewrite's graduation + implementation gate the release; existing demo done-signals are preserved.
• AC-3: The steward sentence names the cornerstone-2 rewrite steward; existing steward entries are untouched.
• AC-4: The edit stays outcome-neutral on Discussion #17818's open OQs (no namespace, module, or schema decisions asserted as settled).

Out of Scope

• Other cornerstone rows and their anchors (their stewards own them).
• A link-rot sweep of transferred issue anchors (they browser-redirect; the dead-link lane #17809 owns systematic link repair).
• Release-cut mechanics across repos (Discussion #17818 OQ8 owns the engine/Institution ordering; buildScripts/release/publish.mjs owns the engine cut).
• VISION.md and architecture guides.

Decision Record impact

none — roadmap scope framing; the rewrite's ADR 0029 amendment rides its implementation wave.

Related

• Discussion #17818 (greenfield DockLayouts rewrite — release-gating per operator ruling)
• #13158 (Qt-parity docking epic, cornerstone anchor)
• #17539, #17540 (dock epics, sequenced behind the rewrite — bodies amended 2026-08-28)
• Milestone 9 (v13.2 engine tracking)

Origin Session ID: d6d42839-ab27-4fc8-bb96-45d8b360c37c

Retrieval Hint: query_raw_memories("v13.2 org release roadmap DockLayouts rewrite release-gating operator ruling")

Live latest-open sweep: checked latest 20 open issues + A2A claim window (last 60 min) at 2026-08-28T10:55Z; no equivalent found, no colliding claim.