KB-48E5

No Duplicate Canonical Authority (recheck-7 blocker C)

3 min read Revision 1

04 - No Duplicate Canonical Authority (recheck-7 blocker C, Constitution Article 14)

Load-bearing copy: doc 00 §Canonical hash encoding banner + doc 06 G-NO-DUPLICATE-CANONICAL-AUTHORITY.

The defect (Điều 14: one authority of one nature)

The same load-bearing canonicalization rules appeared in doc 00 (encoding/extractor/record sections), in the guards, and in the report docs. Three copies of one authority can drift — exact, semantic, or structural duplication. Article 14 requires one authority of one nature, with every other copy explicitly non-authority.

The fix

  • One load-bearing canonical contract = the executable SSOT artifact FIX7-CANON-V1-CANONICALIZER (pinned by canonicalizer_sha256).
  • Everything else is NON_AUTHORITY_EXPLANATION: doc 00's "Canonical hash encoding", "Active-scope / fence / section extractor", and "Record encoding schema" sections each carry a banner that says so and reference the SSOT; this entire report directory is non-authority.
  • Guard G-NO-DUPLICATE-CANONICAL-AUTHORITY (= Codex G-CANONICAL-CONTRACT-SSOT-NO-DUPLICATE; one guard, the other string is a non-authority alias — itself an Article-14 application to the guard name) fails closed on:
    • a second load-bearing canonical / extractor / record / marker contract appearing in ACTIVE_AUTHORITY (exact, semantic, or structural duplicate) → DUPLICATE_CANONICAL_AUTHORITY;
    • an implementation package shipping or referencing a canonicalizer whose hash/version ≠ the pinned SSOT → CANONICALIZER_SSOT_MISMATCH (G-CANONICALIZER-SSOT-ONLY);
    • a report example that conflicts with the SSOT → fail closed or the report is marked report-only.

Scope of the no-duplicate guard (exact / semantic / structural)

  • Exact: a verbatim second canonical rule block in an ACTIVE doc → reject.
  • Semantic: an ACTIVE doc stating a canonical rule that contradicts the SSOT (e.g. a different sort order, separator, or grammar) → reject.
  • Structural: a package or guard that re-derives a digest by its own procedure instead of invoking the SSOT → reject.

Why this is the Article-14 core fix

Codex's recheck-7 hardcode/PG-native gate held precisely because "the construction authority can be interpreted differently by different agents." With one executable SSOT and everything else declared non-authority, there is a single interpretation: run the artifact. Prose can no longer compete with the executable. (doc 00 banner + doc 06 guard-quality rule 12.)

Back to Knowledge Hub knowledge/dev/reports/architecture/t1-fix7-blueprint-patch-after-codex-recheck-7-constitution14-ssot-2026-06-09/04-no-duplicate-canonical-authority.md