KB-7F92

Hardcode / PG-Native Self-Review (recheck-7)

3 min read Revision 1

08 - Hardcode / PG-Native Self-Review (recheck-7)

Codex recheck-7 held the final hardcode/PG-native gate not on any runtime regression (there was none) but because "authority construction still permits disguised fixed behavior through an unpinned canonicalizer and duplicate/drifting load-bearing contract descriptions… a PG-driven design is not complete when the construction authority can be interpreted differently by different agents."

What this pass removed (disguised fixed behaviour at construction time)

risk before (recheck-6) after (recheck-7)
canonicalizer interpretable per agent prose spec in doc 00 + reports ONE executable SSOT artifact, pinned by canonicalizer_sha256, --selftest exit 0 (G-CANONICALIZER-SSOT-ONLY)
duplicate/drifting authority same rules in doc 00 + guards + reports one load-bearing contract; all else NON_AUTHORITY_EXPLANATION (G-NO-DUPLICATE-CANONICAL-AUTHORITY)
revision-layer self-reference checkpoint own-revision read-back as authority revision diagnostic-only; finite ordered seal (G-NO-SELF-REVISION-ANCHOR)
document_id alias grammar allowed ./../// exact MCP id, all aliases rejected (G-DOCUMENT-ID-CANONICAL-MCP)
marker ambiguity kind/literal not bound closed kind enum + per-kind literal grammar (G-MARKER-KIND-LITERAL-CONSISTENCY)

Every load-bearing value is content-addressed or PG/platform-native; the one canonical procedure is now a single executable artifact, not competing prose. This directly answers "interpreted differently by different agents": there is one interpretation — run the artifact.

What this pass did NOT add (invariant preservation)

  • No runtime authority surface / readiness gate / #20 column / catalog family / 8th runtime hash contract. The canonicalizer SSOT is a pinned construction-document TOOL; H01..H07 stay 7; authority surfaces stay 27; gates 14; runtime-evidence 11.
  • The SSOT artifact is not an active_corpus membership member → membership stays f2bda8…fe251.
  • No name/owner/relkind/prokind/CASE runtime policy reintroduced (typed-set separation intact).

Counts 27 / 11 / 14 / 7 preserved; production mutation 0. Runtime PG-first/native/driven design unchanged and accepted by Codex recheck-7. Verdict: RECHECK7_HARDCODE_PG_NATIVE_SELF_REVIEW_PASS — no disguised hardcode remains; no runtime surface added.

Back to Knowledge Hub knowledge/dev/reports/architecture/t1-fix7-blueprint-patch-after-codex-recheck-7-constitution14-ssot-2026-06-09/08-hardcode-pg-native-self-review.md