01 — Live State & SSOT Confirmation

All numbers below were read live on 2026-06-04 via query_pg (RO) and ssh→psql. Old reports are evidence; these live values are authority.

1.1 Counters

metric	live value	note
birth_registry	1,158,148	== prior checkpoint's post-KB value; unchanged by all PG mutations this macro
dot_tools total	309
DOT_* (wildcard LIKE 'DOT_%')	303	includes non-underscore DOT… codes
DOT\_% literal-underscore (discovery universe)	~109 across 14 families	engine keys on literal DOT_
DOT_KG_*	36	18 on-demand producers + 18 cron/dual verifiers, all paired_dot set
dot_tools.last_executed set	157	backfill — 1 distinct timestamp, all usage_count=0
KG last_executed set	0	KG genuinely never ran
dot_iu_command_run	55 rows / 15 commands	IU-command layer (plan/apply/verify); NOT DOT_*
job_queue	13 rows, 6 finished, 1 real run_id group	job:cut verified
event_type_registry	45 → 52	+7 DRAFT process.* (active=false) this macro
v_axis_process_inventory (v1)	60	untouched
v_axis_process_inventory_v2 (new)	46	pair-grouped, on-demand inclusive
discovery views v1	evidence 113 / candidates 17 / orphans 84	live, untouched
AX-PROCESS / AX-TOPIC	CANDIDATE	unchanged

1.2 SSOT confirmations (from prior checkpoint, re-verified live)

• 36 dot-kg DOTs, not 18 — confirmed (count DOT_KG_* = 36). The "18" is the pair count.
• Producer blind spot — confirmed via the exact view filter (doc 03).
• 0 DOT executions — confirmed: every DOT_* family shows members_with_runtime_real = 0; last_executed is a backfill, not a run.
• Binding constraint = correlation — confirmed: dot_iu_command_run has no process_run_id/correlation_id; only job_queue.run_id correlates, and only for job:cut.

1.3 Schema reality (the substrate we build on)

• dot_iu_command_run: run_id (uuid, per-command), command_name, category, run_mode (plan/apply/verify), run_status (planned/applied/verified/refused), mutating, params_digest, gate_snapshot jsonb, evidence jsonb, actor, created_at. No process_run_id, correlation_id, dot_code, started_at/ended_at, error_ref.
• job_queue: has run_id (uuid), idempotency_key, state, picked_at, finished_at, attempts, last_error, actor. This is the model to emulate.
• event_outbox / event_pending: both already have correlation_id (text), plus source_system, occurred_at, safe_payload jsonb, event_domain, event_type. Correlation carrier already exists.
• event_type_registry: (event_domain, event_type, event_stream, delivery_lane, default_severity, description, active, created_at). No PK/FK/unique, no triggers. Check constraints: event_stream ∈ {comment,review,update,birth,task,alert,health}, delivery_lane ∈ {immediate,delayed}, default_severity ∈ {info,warning,critical}.
• No process_run_id / parent_run_id / component_run_id column exists anywhere in public.

1.4 Safety classification

EXECUTION_MODE. RW channel verified live (current_user=directus, db=directus, births match RO read). All writes this macro are additive read-only views + inactive draft rows, each rehearsed net-zero then committed. No forbidden action available was taken.