Trace and read telemetry is best-effort, silent and capped #161

New issue

Closed

opened 2026-08-15 14:33:55 +00:00 by john · 0 comments

john commented

2026-08-15 14:33:55 +00:00

Owner

Source: strict re-review C-19
Verdict: DISPUTE - by design, closing

Claim as reviewed

Trace and read telemetry is best-effort, silent, capped, and tool-response byte coverage is conditional, so observability cannot be treated as an authoritative complete ledger.

At HEAD `f354864` (v3.3.0)

Accurate on every point, and each is a stated contract rather than an accident: the appenders return {written:false, reason} instead of throwing, the file is size-capped before the write, and the readers surface capped or malformed records rather than presenting partial data as complete.

Note

A record of a decision may never be able to change the decision - that is the reason the telemetry is best-effort, and making it authoritative would mean letting a full disk block a phase. The docs already decline to call it a complete ledger.

**Source:** strict re-review C-19 **Verdict:** DISPUTE - by design, closing ### Claim as reviewed Trace and read telemetry is best-effort, silent, capped, and tool-response byte coverage is conditional, so observability cannot be treated as an authoritative complete ledger. ### At HEAD f354864 (v3.3.0) Accurate on every point, and each is a stated contract rather than an accident: the appenders return `{written:false, reason}` instead of throwing, the file is size-capped before the write, and the readers surface capped or malformed records rather than presenting partial data as complete. ### Note A record of a decision may never be able to change the decision - that is the reason the telemetry is best-effort, and making it authoritative would mean letting a full disk block a phase. The docs already decline to call it a complete ledger.