---
id: "contrarian-observability-free"
type: "contrarian-insight"
source_timestamps: ["§5.3"]
tags: ["contrarian", "observability"]
related: ["concept-observability-side-effect"]
challenges: "The assumption that inspecting an AI pipeline's intermediate state requires building logging, dashboards, or tracing tooling."
sources: ["paper"]
sourceVaultSlug: "icm-paper-folder-architecture-2026Jun02"
originDay: 2
---
# Observability shouldn't require a logging or dashboard layer

## What this challenges

The assumption that inspecting an AI pipeline's intermediate state requires building logging, dashboards, or tracing tooling on top of the system.

## The argument

If every intermediate artifact is a plain file, **observability is free**: you open a folder and read it. The system is a glass box **by construction** rather than by the addition of an explanation layer — inverting the usual build-observability-on-top posture. See [[concept-observability-side-effect]] and the canonical quote [[quote-glass-box]].

## Validation status

The observability-via-plain-artifacts claim is correct and aligns with modern observability guidance that systems should be *designed* so behaviour data are captured as part of normal operation.

However, the enrichment overlay flags that in regulated or safety-critical settings, "glass-box AI" requires more than readable artifacts:

- **Provenance** (model version, configuration).
- **Fine-grained traceability** (output spans → source snippets).
- **Explicit safety controls and audit trails.**

ICM provides observability strongly; traceability and formal safety controls are flagged as future work — see [[question-semantic-debugging]]. By colloquial usage ICM is a glass box; in formal governance contexts it is **incomplete**.


## Related across days
- [[concept-observability-side-effect]]
- [[synthesis-glass-box-meets-dialogue]]
- [[quote-glass-box]]