← OMEGA Protocol Specification v1

P14 Predicate Commitment

Status: OMEGA v1.4.1 primitive. P14 is evaluated first. Every other primitive claim in a governed record is a claim of satisfaction against the predicate P14 commits to.

The durability problem

Governed records must remain verifiable after OMEGA evolves. Without predicate commitment, an old record can be read against whatever the current predicate happens to be. That makes the record ambiguous across protocol versions. P14 fixes the predicate at the moment of decision.

Required fields

"predicate_commitment": {
  "predicate_version": "Governed-v1.4.1",
  "predicate_hash": "ac8918ba454f22e7b00091de8d367909fd5740c258a75968666d2e0570e07b2b",
  "attestation_method": "SafeVerify-Lean4",
  "attestation_hash": "7ebc0ee0f53198a1df51934e0e04cfbf064d76a81063e69b1ba5acbba884a90a"
}

predicate_version is the human-readable predicate identifier, such as Governed-v1.4 or Governed-v1.4.1.

predicate_hash is the SHA-256 hash of the canonical Lean predicate definition file.

attestation_method names the verification method. For OMEGA v1.4.1 the method is SafeVerify-Lean4.

attestation_hash is the SHA-256 hash of the attestation report.

Verification protocol

  1. Read the P14 commitment block.
  2. Resolve predicate_hash against omegaprotocol.org/registry/predicates/<hash>.
  3. Resolve attestation_hash against omegaprotocol.org/registry/attestations/<hash>.
  4. Verify that the attestation references predicate_hash exactly.
  5. Verify the record's primitive claims satisfy the resolved predicate definition.

Canonical registry paths

Governed-v1.4 predicate: /registry/predicates/a4df73b484245495989c9b674f89fc5ed9a0d71b4afd04df96646a9346a183fb/

Governed-v1.4.1 predicate: /registry/predicates/ac8918ba454f22e7b00091de8d367909fd5740c258a75968666d2e0570e07b2b/

v1.4 SafeVerify attestation: /registry/attestations/833f22004780b8a6060b9a8356a61a195bfc67e9bb1356a4e6d7afce1aa622af/

v1.4.1 local Lean attestation: /registry/attestations/7ebc0ee0f53198a1df51934e0e04cfbf064d76a81063e69b1ba5acbba884a90a/

Registry design

Canonical copies live at omegaprotocol.org with content-addressed paths. The registry is mirror-friendly. Future versions can migrate to distributed sovereign registries without changing the record format because the record already commits to hashes, not to mutable locations.