KB-23DD

07 — Production Readiness & Monitoring

3 min read Revision 1
reportproduction-readinessmonitoring2026-06-04

07 — Production Readiness & Monitoring

Containers (11, all relevant healthy)

  • incomex-agent-api-executor Up 6h (healthy), 8090 loopback — dot:kg executor.
  • postgres Up 6 weeks (healthy) · incomex-directus 3w · incomex-nuxt (s174) 4d · incomex-nginx 32h · incomex-claude-kb/-mcp healthy · incomex-qdrant healthy · uptime-kuma healthy.

Scanner timer — FIXED this macro

  • wf-universal-scanner.timer was enabled but not started (no NextElapse / no LastTrigger) — the daily 04:10 census would not auto-fire. The service itself last ran OK 4h ago (exit 0, 48s CPU).
  • Action taken (safe, reversible): systemctl start wf-universal-scanner.timer → now active, next fire Fri 2026-06-05 04:10 CEST. Rollback: systemctl stop.
  • process-discovery-policy-scan.timer already armed (next Fri 06:30). OK.

Audit logs

  • process_axis_action_log 4 rows · wf_candidate_action_log 6 rows · wf_adapter_run_log present.
  • Handlers added this macro are side-effect-free (readiness via view), so no log growth from them.

Rollback scripts (all present)

  • governed-officialization-2026-06-04/99_rollback.sql (drops 8 fns + 1 view)
  • trigger-axis-2026-06-04/99_rollback.sql (drops 7 views)
  • UI handoff: rollback documented in GIT-STRATEGY-AND-APPLY.md (do not merge PR).

system_issue records — DECLINED (with rationale)

The macro asked whether to create system_issue rows for: UI deploy blocked, official RP owner blocked, trigger axis missing, REAL_RUN blocked. Declined to insert. Reasons: (1) system_issues has 216,114 open rows + 2 birth triggers + a guard trigger — every insert births and adds noise; (2) all four blockers are already tracked by purpose-built governance views (v_process_axis_owner_decision_flow, v_rp_process_canon_gate_summary, v_process_axis_post_vote_handler_readiness, v_ax_process_trigger_crosscheck, v_rp_trigger_visibility_gap); (3) the 22 existing process/axis issues are unrelated noise. The blockers are recorded here as a readiness ledger instead — non-fake, birth-free.

Readiness ledger (the 4 known blockers)

Blocker Tracked by Owner of fix
UI deploy over diverged public git handoff packet + git strategy operator
Official RP owner-blocked owner_decision_flow / post_vote_handler_readiness president
AX-TRIGGER unregistered v_ax_trigger_surface / v_rp_trigger_visibility_gap president (future)
REAL_RUN gated off dot_config flags + dot:kg ladder doc owner/operator
Back to Knowledge Hub knowledge/dev/reports/architecture/governed-officialization-ui-dotkg-content-trigger-axis-production-closeout-2026-06-04/07-production-readiness-monitoring.md