Observability debt registry
Source of truth for components in observability debt — those that predate policies/observability-first.kmd (ratified 2026-05-29) and do not yet satisfy its release gate (R5.1 [slo], R2.3 cardinality, R6.2 runbooks, R1.1 structured logs). Referenced by the policy's §Exceptions and populated by the koder-spec-audit observability audit (KTOOLS-033).
While the audit posture is soft-warn (acceleration phase), an entry here is an acknowledged, time-boxed exception — not a silent gap. Promote to the release gate (--strict) once a component clears its row.
Schema
| Column | Meaning |
|---|---|
component |
repo-relative module path (dir holding koder.toml) |
missing |
which checks fail: slo (R5.1) · cardinality (R2.3) · runbook (R6.2) · logs (R1.1) |
since |
date the debt was first recorded |
target |
date/condition to clear it (or backlog#NNN) |
notes |
context |
Debt
| component | missing | since | target | notes |
|---|---|---|---|---|
core/settings |
logs, slo | 2026-06-23 | core/settings/backlog#006 (needs C/GTK obs binding) |
GTK4C desktop app, no Go module + no request-serving surface. The canonical obs binding (`enginessdkgoobs) is Go-only; no C OTLP binding exists in the SDK. Hand-rolling would violate §4.3 (single SDK). Deferred until a C/GTK obs binding ships; client telemetry then respects auto-report opt-out (§8.3). The other three core |