Claims-Producer-Side

Verification pipelines have a habit of accidentally collapsing two distinct concerns. The author of a claim and the verifier of a claim get folded into the same artifact, and the artifact carries both authorial state and verification state. Whichever lane edits the artifact last wins. Drift accumulates silently.

The claims-producer-side discipline keeps the two separated. Claim manifests live in the producer-side repository, authored by a single lane (the substrate-lane). The schema for these manifests carries verification_status: unverified as the steady state, both before and after a Veritas TEST run. Verification state does not live in the producer-side YAML; it lives in the verdict-of-record (Mattermost post + derivative axon_veritas/verdicts/ YAML).

Single-author-per-artifact is the load-bearing constraint. The substrate-lane is the only lane that edits claims.yaml. The verification-lane reads claims.yaml to run TESTs, but never writes to it. The render-lane reads claims.yaml at build time, but never writes to it. Each lane has its own write surface; no lane overwrites another’s authorship.

The discipline pairs with substrate-canonicity-coproduction: the substrate is canonical not because the producer-lane declares it canonical, but because downstream consumers (verification, render) demand the canonical paths. Both sides — producer-declared and consumer-demanded — are required for canonicity. Single-side declaration is insufficient.

When the producer-side claim is corrected, the substrate-lane edits the YAML; the substrate-pin advances; Veritas re-fires the TEST against the new substrate and re-posts the verdict. No producer-lane edit ever changes verification state, and no verification-lane edit ever changes claim content.