omega-verification-kit

Independently verify the Atomadic Omega engine's published closure receipt.

This kit lets anyone — investor, researcher, customer, skeptic — verify the Ed25519 signature on the closure receipt that Atomadic publishes at https://mcp.atomadic.tech/.well-known/atomadic-closure.json and read the exact claims that the engine signed.

You do not need an Atomadic account. You do not need an API key. You do not need to trust the marketing.

What is "the closure receipt"?

The Omega engine periodically runs a verification routine against itself — checking ten internal invariants (byte-parity, callable surface, entitlements, imports, ledger consistency, lobe presence, schema validity, single-writer locks, validation, wisdom feed) plus a Banach contraction proof — and signs the result with an Ed25519 key. The signed result is the receipt.

The receipt is not a claim about the engine's IQ, sentience, or any other fuzzy property. It is a cryptographic attestation that the engine, at the moment of signing, met its own definition of "closed" — every defect counter at zero, contraction ratio < 1, validation green.

If anything in the published receipt has been altered after signing, the verification fails. If the published pubkey doesn't match the key that signed, the verification fails.

Run it

pip install pynacl requests
python verify_closure_receipt.py

That's it. The script fetches the receipt + the issuer pubkey manifest, performs one Ed25519 verification, and prints the claims.

Sample output

PASS — Ed25519 signature verifies against the published Atomadic issuer pubkey.
  receipt:     https://mcp.atomadic.tech/.well-known/atomadic-closure.json
  pubkey:      https://mcp.atomadic.tech/.well-known/atomadic-issuer-pubkey.json
  pubkey_b64u: SLPpE_veMjDqfLG8sB5KjFHrdnceF-S07AtsqJASSes
  key_id:      141863afc6f7a6f1
  schema:      atomadic.closure_attestation.v1
  issuer:      atomadic

Receipt claims (signed):
  closure_met:           True
  closure_score:         1
  contraction_ratio:     0.533064582142828
  banach_condition:      True
  mode:                  deterministic_no_llm_zero_parameter
  defects (10 axes, all 0 means 'closed'):
     - byte_parity_defect            0
     - callable_surface_defect       0
     - entitlement_defect            0
     - import_defect                 0
     - ledger_defect                 0
     - lobe_defect                   0
     - schema_defect                 0
     - single_writer_defect          0
     - validation_defect             0
     - wisdom_defect                 0

Engine snapshot at signing time:
  engine:                ALIVE
  dna_count:             7830
  emitted_count:         7830
  schema_count:          179
  validation_green:      True

Flags

Flag	Purpose
--receipt-url	override default URL (e.g. point at a self-hosted copy)
--receipt-file	verify a local copy of the receipt (e.g. one you saved last week)
--pubkey-url	override the issuer pubkey URL
--pubkey-b64	pass the pubkey on the command line (skip the fetch entirely)
--quiet	only print PASS or FAIL

What this does NOT prove

• It does not prove the engine is "smart" or "useful". It proves the engine signed the exact claims you can read in the receipt.
• It does not prove Atomadic hasn't lost custody of the private key since signing. (The key rotation story is in the issuer pubkey manifest's key_id history; rotate-and-publish is the standard signal.)
• It does not prove the engine's current state matches the receipt — receipts are snapshots. The measured_at_utc field tells you when.

Reproducing the claims yourself

If you want to verify not just the signature but the substance of the defect counts, the underlying atom is verify_closure_receipt_pure (lb:t0:verify_closure_receipt_pure:a44771318ede). Its source is in the Atomadic engine and is run by the same script the engine uses to sign. If you hold an Atomadic entitlement key, you can invoke it via the public MCP at mcp.atomadic.tech.

Reporting

If you find a verification failure that you believe is real (not a transient network issue, not a stale clone), open an issue at https://github.com/atomadictech/atomadic-sdk/issues with the raw receipt and pubkey bytes attached. We will rotate keys and republish if necessary.

License

This verification kit is MIT-licensed. The receipt schema (atomadic.closure_attestation.v1) and the issuer pubkey manifest schema (atomadic.issuer_pubkey_manifest.v1) are specified at https://atomadic.tech/docs.html.