---

title: 11 — Consolidated Implementation Roadmap (Branch J) date: 2026-05-31

11 — Consolidated Implementation Roadmap (Branch J)

One roadmap, gate-ordered. Grouped into as few large macros as possible.

What can be done NOW (no approval) — DONE this macro

• Approval scan, rehearsals (display_policy, registry_pin, parent_code overlay, PIV-500 candidates), commit-ready packs, static UI preview v2 (deployed), no-hardcode evidence, acceptance read-only run, next prompts. ✅

What waits for APPROVAL (human/council) — gated

gate	scope	unlocks
RG1+RG2	six-object foundation commit	everything downstream
RG3	pivot bundle (PIV-500/301/302/303/311) + parent_code wiring	grand total, drift/phantom-candidate/orphan/label pivots, drilldown
RG4	phantom law (council)	phantom_count, PIV-302 promotion, phantom event/issue types
RG5	display_policy commit	threshold/grouping live
RG6	registry_pin commit	PIV-321, pin column
RG7	Directus collection registration (Directus write)	read API over views
RG8	Nuxt render-shell on /knowledge/registries-pivot	the converged surface
RG9	legacy retirement + route cutover	retire Đ28 page/endpoints

What waits for PG VIEWS

PIV-500/301/302/303 are view-backed (need v_count_rollup_src + v_count_drift committed first). API endpoints /integrity /drift /tree /living-lists /substrate need the six views.

What waits for API

Nuxt render-shell (RG8) reads the doc-06 endpoints; legacy retirement (RG9) needs the shell at parity.

What waits for UI

Route cutover/redirect and CI no-hardcode gate enforcement (RG9) need the shell live & green.

What waits for LAW decision

Phantom_count, PIV-302 "phantom" promotion, phantom cleanup workflow (RG4 council only).

Ordered commit sequence (the instant approvals land)

1. RG1+RG2 → record sign-off to approval_requests/apr_approvals → \i 001..006 + 900_verify (V3 closure) in ONE tx → verify 6 objects, idle 0.
2. RG3a → CREATE VIEW v_count_rollup_src (helper) → bulk-INSERT PIV-500/301/302/303 + PIV-311 in ONE statement is_active=false off-peak → activate → verify engine SUM.
3. RG3b → ONE-statement UPDATE pivot_definitions … parent_code (13 edges) → verify 13 non-null, 0 dangling.
4. RG5 ∥ RG6 → CREATE TABLE display_policy + seeds; CREATE TABLE registry_pin → PIV-321.
5. RG4 (council, independent) → phantom law → phantom_count + PIV-302 promotion + NEW event/issue types.
6. RG7 → register six views as Directus read collections + read policy → build 8 endpoints (pivot-query pattern).
7. RG8 → /knowledge/registries-pivot render-shell + components (doc 08) → wire v2 preview live.
8. acceptance (doc 10) green → RG9 → converge /knowledge/registries, redirect, retire Đ28 violations → CI no-hardcode gate.

Grouping into few macros (recommended)

• Macro F1 — Foundation Commit (RG1+RG2+RG3): six views + pivot bundle + parent_code, ONE gated session. Engine warning: pivot INSERT/UPDATE fires statement-level full refresh — always ONE batch statement, is_active=false, off-peak.
• Macro F2 — Surfaces (RG5+RG6+RG7): display_policy + registry_pin + Directus/API exposure.
• Macro F3 — Render & Converge (RG8 → acceptance → RG9): Nuxt shell, wire preview, acceptance, cutover, CI gate.
• Macro L1 — Phantom Law (RG4): council-only, runs in parallel, independent of F1–F3 commits.

Verdict

Roadmap consolidated into 4 gated macros (F1, F2, F3, L1). All "now" work complete; all commits correctly deferred to their gate.