register_canonical
Also known as: register canonical, canonical register
A schema field that names the canonical source-of-record for a verdict. Pinned in the verdict YAML as `register_canonical: "mattermost"`, with a required derived_from block naming the originating post.
register_canonical is the schema encoding of the precedence-of-authority discipline behind Path 2(2d). The concept being encoded is the verdict-of-record: the Mattermost post under the veritas handle is the canonical answer, and any other manifest of the same verdict is a derivative. The schema field is how that concept gets enforced rather than merely documented.
In the verdict YAML at axon_veritas/verdicts/<slug>.yaml, the field appears as a const-pin:
register_canonical: "mattermost"
derived_from:
register_post_id: <mattermost post id>
register_channel_id: <channel id>
register_handle: "veritas"
Schema validation rejects any verdict YAML that omits derived_from or that sets register_canonical to anything other than "mattermost". The structural pin is load-bearing in a way prose carve-outs are not — future verdict YAMLs cannot accidentally drift away from the discipline because the schema forbids it.
When the YAML and the Mattermost post ever disagree, the post wins by definition. The YAML is re-emitted to match. This is what the precedence-of-authority discipline buys: an automated reconcile path with no ambiguity about which side is authoritative.
register_canonical distinguishes the concept (the verdict-of-record itself) from the encoding (the schema field that names the register). The distinction matters because the encoding is what makes the discipline enforceable in machine-readable form; without the structural pin, the precedence-of-authority would live only in human-readable convention and would drift under edit pressure.
Schema encoding
This term is the schema-encoding side of verdict-of-record. Each entry cross-references the other; the two are intentionally separate.