RP-04 And RP-05 - Catalog Coverage And Descriptive-Only Payload

Status: RESOLVED_BLOCKING

RP-04

reference_contract, operand_column_contract, and structural_literal_class are exact-set families inside the sealed code-catalog root. They do not create authority surfaces.

• discovered catalog-typed FK columns vs reference_contract: both EXCEPT, exactly one row each;
• ACTIVE operand types vs operand_column_contract: both EXCEPT, exactly one physical column each;
• numeric literals in every hash-bound adapter/function source vs structural_literal_class: every literal classified; unclassified means readiness FAIL.

The count remains data-driven by code_catalog_set.expected_family_count.

RP-05

code_catalog_item.item_payload is descriptive-only. Operational values may come only from named typed columns/operands. Expected adapter-to-column edges are sealed dependency_manifest rows; analyzer_contract_manifest.allowed_input_set_sha256 binds their exact set. Analyzer observations must match expected edges in both EXCEPT directions.

Any operational edge to code_catalog_item.item_payload, undeclared input column, missing expected edge, or unclassified numeric literal blocks readiness.

Codex did not create a separate adapter_input_contract table because that would risk an uncounted authority surface. Existing counted dependency/analyzer surfaces provide the same PG-driven enforcement.