Observability Theater

In one production compliance platform, an event fires on every run. It carries a field meant to record which compliance obligations that run actually verified. The field has a clear, meaningful name. It satisfies the schema. It shows up on dashboards. And it is permanently, structurally empty — the code that assigns it writes a hard-coded empty list, never computed from anything. The docstring beside it is honest about the gap: the value is a placeholder, and the wiring needed to fill it “does not yet exist.” The dashboard downstream displays which obligations a run checked. It always displays zero.

The intuitive assumption is that an empty field costs nothing: it carries no data, so it does no harm. The human-factors research says otherwise. When an automated system reports the same stable output on every event, operators stop scrutinizing it. The output stops registering as a signal and starts functioning as background. A field that always reads empty trains the people watching it to treat empty as the expected, correct state. After enough exposures, nobody questions it — the field is visually present but cognitively dismissed. This is not a failure of attention. It is the predictable way human attention responds to a stimulus that never changes.

Hospitals know this dynamic. Studies of intensive-care units find that the overwhelming majority of alarms are clinically insignificant, and that nuisance alarms erode nurses' confidence in the monitoring system as a whole. Security operations centers see the same: high false-positive rates produce desensitization, and desensitized analysts miss real incidents. An empty telemetry field is the silent version of the same failure. A nuisance alarm is loud and wrong; an empty field is quiet and wrong. There is no alert to dismiss — the field simply reads zero, on every event, indefinitely. Operators have nothing to react to and therefore nothing to flag. The controlling variable is not loudness; it is invariance.

In a compliance-automation product, governance telemetry is not optional instrumentation — it is the audit trail. Logging standards require that records carry sufficient detail for after-the-fact investigation. An event that permanently emits an empty obligations field fails that requirement on every event, silently. The audit trail is present; the audit evidence is absent. Worse, the empty value cannot tell two very different facts apart: “no obligations were evaluated” and “the wiring to record obligations does not exist” produce the identical zero. An internal engineer may know it is a placeholder — but the day an external auditor queries the event stream, a comment buried in the source code is not a documented control. The placeholder presents as evidence.

The remedy is not a smarter dashboard. It is a field-level liveness contract: a schema commitment that asserts not only the type of a field but the conditions under which it must carry content. The obligations field MUST contain at least one obligation identifier when a governance pack was applied and the run completed evaluation — emitting empty in that case is a contract violation, not valid data. Until the real wiring lands, a single instrument helps immediately: a counter that increments every time the field is emitted empty. That converts a silent failure into a visible debt counter. Once leadership can see how many audit records per day ship hollow, the cost of inaction becomes legible — and the business case for the fix becomes tractable.

The core line is worth saying flatly: a named field is a promise. When it promises specific content and emits none on every event, it has not merely failed to inform — it has produced false confidence in monitoring coverage that does not exist. Fixing it is not only a code change. Operators who have internalized empty as normal will read the first real value as an anomaly to be investigated rather than a migration that finally worked. A fix that repairs the wiring and skips the human handoff just replaces one form of theater with another. The honest goal is telemetry whose fields carry information — and that can be checked, by a machine, on every event.