06 — Birth / Governance / RP Synchronization

Score: Birth/governance synchronization = 58/100. Birth discipline is excellent (birth-free DDL, before==after) and there is no fake-official. But the render layer is desynchronized from the governance layer: 3 of 5 displayed axes are not in axis_registry, ownership is empty, and every node is candidate/synthetic — RP shows things that governance does not know about.

Live governance ground truth (2026-06-05)

• axis_registry: 2 rows — AX-TOPIC=CANDIDATE, AX-PROCESS=CANDIDATE.
• axis_assignment: 25 (all AX-TOPIC).
• governance_object_ownership: 0 rows.
• approval_requests: 230; PROC-OWN-01..05 all pending (0 approved).
• dot_config: real_run_enabled=false, execute_enabled=false, dry_run_only=true, emit_enabled=false → REAL_RUN fully fail-closed.
• event_type_registry: 52 (process.* 0/7 active).
• birth_registry: 1,194,873, all recent DDL verified before==after (birth-free).

Per-design synchronization classification

Axis / object	In axis_registry?	RP shows it?	Governed?	Classification
AX-BASE (39 pivot nodes)	NO	YES	native pivot, not axis-governed	RP visible but not governed (synthetic axis)
AX-TOPIC (7)	YES (CANDIDATE)	YES	candidate, owner-gated	candidate only
AX-PROCESS (22)	YES (CANDIDATE)	YES	candidate, 0 official	candidate only
AX-TRIGGER (7)	NO	YES	not registered, owner absent	RP visible but not governed (synthetic axis)
AX-PXT (12)	NO	YES	derived ledger, not an axis	RP visible but not governed (synthetic axis)
job:cut	n/a (process)	YES (hardcoded branch)	READY_FOR_PRESIDENT, 0 votes	governed-ready but not voted
governance_object_ownership	—	—	empty	governance missing (table empty)
process.* events	event_type_registry	counted	0/7 active	born but inactive

The core sync gap — synthetic axes

AX-BASE, AX-TRIGGER, AX-PXT are rendered by RP but do not exist in axis_registry. This is the inverse of "governed but not visible" — it is "visible but not governed." A supervision UI that displays governance objects must not invent 3 of its 5 top-level axes. Two honest resolutions:

1. Register them (AX-BASE/AX-TRIGGER/AX-PXT as rows in axis_registry, even as SYNTHETIC or DERIVED status) so the display set == the registry set; OR
2. Label them SYNTHETIC/DERIVED in the UI so the supervisor knows these 3 are computed lenses, not governed axes. Until one is done, there is a dangerous-mismatch potential: the UI implies all 5 axes are equivalent governance objects when only 2 are even candidate-registered.

What is correctly synchronized (credit)

• No fake-official. 0/453 official is the true state; RP does not paint candidates green. governance_status carries UNGOVERNED_CANDIDATE / BLOCKED_OWNER / BLOCKED_NO_PRESIDENT_VOTE honestly.
• Birth-safe. Every view/function was created without firing the birth trigger (before==after). New designs did not pollute birth_registry.
• REAL_RUN fail-closed. No design can execute; dot_config flags all false. Approval→execution chain blocks unimplemented handlers.
• Approval state honest. PROC-OWN votes are genuinely 0; nothing pretends otherwise.

Sync classification summary

• design synchronized: AX-BASE counting (pivot-driven), birth discipline
• candidate only: AX-TOPIC, AX-PROCESS, all process candidates
• governance missing: governance_object_ownership (empty)
• birth missing: n/a (birth-free is intentional, not a gap)
• approval missing: PROC-OWN votes (authority-gated, expected)
• RP visible but not governed: AX-BASE, AX-TRIGGER, AX-PXT ← the fixable mismatch
• governed but not RP visible: none found
• dangerous mismatch: only potential — synthetic axes presented as peers of candidate axes without a label

Net

Governance integrity is strong (no fakes, birth-safe, fail-closed). Governance coverage of what RP displays is the gap: RP renders 3 ungoverned synthetic axes as if they were registry axes. Registering or labeling them is the sync fix, and it is T1-fixable (additive registry rows + a governance_class column on the contract).