Invariant 4 says all inter-agent data is JSON and markdown is only a render step; the history chapter's reconstruct artefact is Markdown precisely because a model reads it.

Invariant 4 says all inter-agent data is JSON and markdown is only a render step; the history chapter's reconstruct artefact is Markdown precisely because a model reads it.

A premise contradiction (severity nitpick) found by the cross-document consistency pass.

• End A: .abcd/development/brief/02-constraints/03-invariants.md:15 — "all inter-agent data is JSON; markdown is a render step"
• End B: .abcd/development/brief/04-surfaces/11-history.md:149 — "The artefact is Markdown because its consumer is a model being handed the session as context"

03-invariants says all inter-agent data is JSON and markdown is a render step. 11-history says reconstruct writes one self-contained Markdown artefact as its primary output, and that it is Markdown because its consumer is a model being handed the session as context. Only the telemetry file beside it is JSON. A Markdown document designed as a model's input is inter-agent data that is not JSON, so the invariant's 'all' does not hold.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 67.