KB-1A23

Supertrack A — Blocking RP Resolution Matrix

4 min read Revision 1
fix7architecturet1-reviewrp-correctedsupertrack-a

01 — Supertrack A: Did Codex resolve all blocking RP?

Vocabulary: RESOLVED / PARTIAL / STILL_OPEN / CONTRADICTION.

RP Blocking? Status Basis
RP-01 runtime-evidence tables YES PARTIAL 11 tables byte-defined (doc 02), non-authority, enumerated via #20; capability_environment folded explicitly. BUT the H04/H05/H02 sub-payload-key→column binding (CP-06 doc 07) is not byte-implementable without guessing: H04 evidence-hash keys mis-stated as signoff_binding columns (contradiction); scope_hash composition unpinned; 4 runtime aggregates lack a pinned total order. → drives P-01/P-02/P-03.
RP-02 retention authority YES RESOLVED Option i: retention fields on counted storage_class_manifest #05; no 28th surface; sealed/versioned/hash-bound; flows into H01/H02; generic engine reads ACTIVE row; seal rejects archive-required-without-target.
RP-03 consolidated DDL + expected-constraint catalog YES RESOLVED One normative 10-step creation order + 5 deferred-constraint groups; expected constraints are typed authority_scope_manifest #20 rows (no free-form JSON, no new surface); pg_constraint/pg_index both-EXCEPT; dropped deferred FK → OBJECT_AUTHORITY_IMMUTABLE fail. (Minor advisory P-04: benign-extra-index disposition unstated.)
RP-04 catalog-family coverage YES RESOLVED reference_contract + operand_column_contract + structural_literal_class are exact-set families inside the sealed code-catalog root; both-EXCEPT coverage; unclassified literal → readiness FAIL; family count data-driven via code_catalog_set.expected_family_count.
RP-05 item_payload operational-read ban YES RESOLVED item_payload descriptive-only; operational values only from named typed columns/operands; expected adapter→column edges are sealed dependency_manifest rows bound by analyzer_contract_manifest.allowed_input_set_sha256; any operational edge to item_payload / undeclared input / missing edge / unclassified literal blocks readiness. New surface avoided.
RP-07 retirement-evidence FK YES RESOLVED Deferred ALTER … fk_code_catalog_item__retired_evidenceevidence_registry(evidence_id) RESTRICT/RESTRICT/NOT DEFERRABLE; existing CHECK (active→NULL, retired→non-NULL); in consolidated order group 5 + sealed expected-constraint set; fake UUID rejects at FK.

Advisory RP (also applied):

RP Status Basis
RP-06 same-human slot scope RESOLVED Blanket UNIQUE(activation_id,human_identity_id) rejected; slot-scoped UNIQUE on signoff_binding/quorum_vote; manifest-driven separation via principal_separation_manifest; non-separated roles allowed. (Hash-binding of the slot is via scope_hash → see P-02.)
RP-08 Directus read-contract RESOLVED Sealed read-contract = ACTIVE Directus SELECT subset in privilege_set_manifest #21 with observation_max_age_seconds; both-EXCEPT (observed/expected/stale); no hardcoded window; Directus gets no control-plane authority.

Supertrack A conclusion

Five of six blocking RP are RESOLVED. RP-01 is PARTIAL: the table-definition half is resolved, but the hash-binding half (the explicit "H04/H05/H02 byte-implementable" acceptance gate) carries one internal contradiction and two unpinned-determinism gaps. These are surgical and confined to CP-06 doc 07. No RP is STILL_OPEN; one CONTRADICTION (P-01) is present and must be corrected.

Back to Knowledge Hub knowledge/dev/reports/architecture/t1-fix7-rp-corrected-design-short-review-2026-06-07/01-rp-blocking-resolution-review.md