KB-7C34

06 — Generated Contract v2

2 min read Revision 1
rpgenerated-contract2026-06-05

06 — Generated Contract v2 (Phase 6)

Object

v_rp_universal_node_ui_contract_generated_v2 — the corrected manifest-driven backbone, 87 rows.

Construction

  • BASE / TOPIC / TRIGGER legs: identical to the v1 generated view (those three axes already passed parity at baseline). BASE binds the pivot node contract (39), TOPIC the axis surface (7), TRIGGER the trigger surface (7).
  • AX-PROCESS: candidate (19) UNION job:cut (1) UNION workflows (2) = 22 — the fix from docs 02-03.
  • AX-PXT: live_v2 ledger (12) — the fix from docs 04-05.
  • Total 39 + 22 + 12 + 7 + 7 = 87.

Properties required by the macro

  • 87 nodes: yes.
  • Match current on node identity: yes — per-axis membership gap 0 both directions (doc 07).
  • Match current on count: yes — 0 count diffs.
  • Expose generator provenance: yes — source_view, leg_kind, is_registry_backed, is_synthetic columns.
  • No unsafe dynamic DDL: yes — it is a plain view; the generator function returns TEXT only and is never executed as DDL.

Provenance hash

Generated full-text md5 (from fn_rp_generate_universal_contract_sql_v2) = a79c9560b12c36619f8a2c3500fcf63e (v1 was 2a9c1f00f788bd3509df7512642a9829).

Replacement candidate

Also published as v_rp_universal_node_ui_contract_generated_current_candidate (a thin alias over generated_v2) — the explicit replacement candidate. NOT repointed into production current (see doc 10).

Back to Knowledge Hub knowledge/dev/reports/architecture/rp-generator-parity-fix-contract-replace-ui-deploy-standby-2026-06-05/06-generated-contract-v2.md