14 · Production Monitoring Lock (2026-06-05)

Live infra (verified this run)

Component	State
wf-universal-scanner.timer	active + enabled, next 2026-06-05 04:10 CEST
incomex-agent-api-executor	Up 16h (healthy), :8090
postgres	Up 6w (healthy)
directus	Up 3w (healthy)
incomex-nuxt	Up 10h (healthy)
incomex-nginx	Up 42h
qdrant	Up 2mo (healthy)
agent-data / claude-kb / claude-mcp	healthy
uptime-kuma	Up 8w (healthy)

Monitoring surfaces (read-only)

• v_total_final_acceptance_scorecard — 11-dimension acceptance board.
• v_rp_process_canon_gate_summary / v_ax_trigger_canon_gate_summary / v_dotkg_realrun_preflight — per-domain gate boards.
• v_process_trigger_actionability_ledger — new severity-scored cross-axis gap ledger.
• birth_registry — background birth tracking (1,194,727; +20,677/day background).

Standing blockers (monitored, not engineering)

1. UI deploy — operator push/PR over diverged public git.
2. Officialization — human-president PROC-OWN-01..05.
3. REALRUN — dot:kg owner (PROC-OWN-04) + config flips + contract.
4. Trigger owner — AX-TRIGGER (Dieu-39).

Lock decision

• Did NOT insert into system_issues (2 birth triggers; 216k+ rows; unsafe noise). Monitoring stays read-only via views.
• The one safe write (v_process_trigger_actionability_ledger) is birth-free and rollback-staged.

Net

Production monitoring is locked and green; all four standing blockers are authority/operator, surfaced on read-only boards.