---
id: "concept-observability-side-effect"
type: "concept"
source_timestamps: ["§5.3"]
tags: ["observability", "interpretability", "glass-box"]
related: ["concept-icm", "concept-edit-source-principle", "contrarian-observability-free"]
definition: "Because every intermediate output is a plain file, ICM is observable by default — no logging layer, no dashboard; you open a folder and read the files."
sources: ["paper"]
sourceVaultSlug: "icm-paper-folder-architecture-2026Jun02"
originDay: 2
---
# Observability as a Side Effect (Glass-Box AI)

## The accidental feature

The most useful property of ICM may be one not designed as a feature. Every intermediate output is a plain-text file, so the system is **observable without any added tooling**.

Rudin argued inherently interpretable systems should be preferred over post-hoc explanations of opaque ones. ICM is a glass-box workflow that was **never opaque in the first place**, because every artifact is human-readable — see [[quote-glass-box]].

## Mapping to human-AI guidelines

It maps onto Amershi et al.'s human-AI interaction guidelines:

- **Make clear what the system can do** → stage contracts ([[concept-stage-contracts]]) make capabilities explicit.
- **Support efficient correction** → markdown files: open, edit, save.
- **Support efficient dismissal** → review gates support deciding not to proceed.

## Caveats on "glass-box"

The enrichment overlay notes that "glass-box AI" has stricter definitions in regulated settings (Nokia's "Glass Box Imperative"; Ncontracts) that include:

- **Provenance** — which model version, which configuration.
- **Fine-grained traceability** — output spans → source snippets.
- **Formal safety controls and audit trails.**

ICM provides strong observability and partial auditability (via Git + human review), but **not yet automated traceability** — that gap is [[question-semantic-debugging]]. By colloquial standards ICM is a glass box; by strict governance standards it is a partial glass box.

## Contrarian framing

The broader contrarian move — that observability shouldn't require a logging or dashboard layer — is captured in [[contrarian-observability-free]].


## Related across days
- [[quote-glass-box]]
- [[contrarian-observability-free]]
- [[synthesis-glass-box-meets-dialogue]]
- [[question-semantic-debugging]]