Path 2(2d)
Also known as: Path 2(2d), verdict-overlay architecture
The verdict-overlay architecture used to render per-claim verification state on outward surfaces. Veritas emits a derivative manifest of its register-of-record; the consumer-render surface overlays that manifest onto the producer-side substrate at build time.
Earlier in the pipeline’s life, a verified claim looked like this on the producer side: the claims.yaml carried a verification_status field that Veritas was expected to update after each TEST run. That coupling created a drift class — two authors (substrate-lane and verification-lane) writing into the same YAML, each with valid edits, each capable of silently overwriting the other.
Path 2(2d) closes the drift class. Producer-side claims.yaml carries verification_status: unverified at all times — the field is no longer load-bearing for consumer-render. Veritas emits its verdict to a separate manifest at axon_veritas/verdicts/<slug>.yaml, derived from the canonical register-of-record (the Mattermost post under the veritas handle). The consumer-render surface (Astro build) overlays this manifest onto the substrate at build time, reading verification_status from the verdict YAML, not from claims.yaml.
The 2(2d) designation reflects a precedence-of-authority discipline: the Mattermost post is canonical; the YAML manifest is a derivative cache. If the two ever disagree, the post wins and the YAML re-emits. The schema for the verdict YAML enforces this with a required derived_from field pointing back to the Mattermost post id.
Path 2(2d) is what makes “publish broadly with per-row verification badges” architecturally sustainable. Substrate authors author. Verification verifies. Render renders. Each layer is single-author at its own grain; no layer overwrites another.