06 — Open Work Map (separated by domain)

Date: 2026-06-03. Every item tagged with its gate. Nothing here is "in progress" — it is the queued backlog after returning to Registries-Pivot.

1. Governance — gated work

Item	Gate	Owner	Action
Execute canonical production rollout	ospa ≥ 1 (human L2/L4 ratification)	Human ratifies → Agent executes	Run post-gate prompt ONE_ROOF_PRODUCTION_ROLLOUT_EXECUTE_ON_RATIFICATION (doc 05)
Ownership-accountability APR ratification	Human L2/L4	Human council	Produces the ratified APR code + raises ospa
Governance event activation tier (design)	After rollout live	Agent (design-first)	Currently fail-closed by design; activation is a separate future gated tier, not part of the base rollout
App-side label_rule alignment	Independent	Agent + app owners	Align application label_rules with governance topic axis (cross-facet reconcile already designed on clone)

2. Registries-Pivot — work (the workstream we are returning to)

Per RP design doc 13, sequenced & gated. RG1 = human ratify Master Design v0.1; RG2 = count-integrity rehearsal accepted.

Macro	Prompt	Gate
M1 (P0)	REGISTRIES_PIVOT_COUNT_INTEGRITY_READONLY_REHEARSAL	after RG1
M2 (P1)	REGISTRIES_PIVOT_ADDITIVE_SCHEMA_AND_PIVOTS_DRESS_REHEARSAL	after M1 + Điều32 packet
M2.5 (P2)	REGISTRIES_PIVOT_DIRECTUS_API_EXPOSURE_PLAN	after M2 (design-only)
M3	REGISTRIES_PIVOT_LAW_RECONCILE_PACKET	council
M4 (P3)	REGISTRIES_PIVOT_UI_PREVIEW_STATIC	after RG6
M5	REGISTRIES_PIVOT_PIN_REGISTRY_BIRTH	after RG5 + approval
M6 (P4)	REGISTRIES_PIVOT_IMPLEMENT_CONVERGED_SURFACE	after RG1–RG8 all accepted
M7 (P5)	REGISTRIES_PIVOT_NOTIFICATION_CLEANUP_INTEGRATION	after M6 + M3 ratified
DEFER: ghost detection (Qdrant), IU/KG pivots — separate later macros.

Immediate RP next step = M1 (see doc 09 for the ready-to-paste prompt). M1 is a BEGIN..ROLLBACK read-only rehearsal — safe, no commit.

3. App-side label_rule alignment

• Cross-facet reconcile (topic axis = facet-1 domain labels via topic_taxonomy_map; collection label_rules = facet-2/4 structural; orthogonal) designed & proven on clone (divergent 4→0, projection_gap 1→0).
• Open: apply the alignment app-side without editing app-owned label_rules destructively. Independent of the governance gate.

4. Event activation tier

• Governance events are intentionally fail-closed in production (0 emitted).
• Open (design-first): a dedicated activation tier (register event types → activate → dispatcher contract). Must be register-before-emit (Điều45), signal-only, MOT-not-executor. Gated behind rollout-live.
• RP's own notification/cleanup (M7) reuses the same system_issues/event_outbox contract — keep the two designs consistent.

5. UI / Nuxt future work

• RP UI preview (M4, static, additive nginx mount under /ui-preview/registries-pivot/<version>/) → converged render-shell (M6) at /knowledge/registries-pivot.
• Current production /knowledge/registries-pivot shows only a generic knowledge doc; the interactive surface awaits M4/M6 (gated on RG approvals).
• Forbidden until gated: production Nuxt change, DB mutation, fabricated/hardcoded counts.

6. Law / ratification work

• Governance: human L2/L4 ratify ownership-accountability APR (raises ospa).
• RP: RG1 (ratify Master Design v0.1) + RG2 (count-integrity accepted) + RG3–RG8; M3 council packet (ratify phantom definition, register issue/event types, route convergence, canonical CAT).
• All require council/human; no self-approval (Điều20).

Domain separation rule

Governance gated execution and Registries-Pivot rehearsals are independent tracks. RP M1–M5 design/rehearsal work can proceed (gated by RG, not by ospa) without waiting for the governance production rollout. Only RP items that would touch production governance state must respect the ospa gate.