notary/cloud
ProductHow it worksChainsSecurityFAQFor partnersTrust
Scope a pilot
For RegTech OEM partners

Evidence integrity under AI compliance agents.

Notary Cloud records the decision event your AI compliance agent produces, bound to the design surface it ran under. Your product handles runtime decisioning. Notary Cloud produces the externally verifiable record that survives examination.

Scope a pilotIntegration notesPilot pricing
Where compliance evidence breaks

Audit-ready inside does not mean verifiable outside.

AI compliance vendors can produce useful in-product audit trails. The harder question comes later, when a bank customer, examiner, or model-risk reviewer asks for evidence that can be inspected outside the vendor runtime.

Notary Cloud records the event underneath the partner product and binds it to timestamp, design-surface state, and cryptographic custody. The partner keeps the decisioning surface. Notary Cloud gives the decision an external evidence layer.

WHAT NOTARY CLOUD RECORDS
  • Decision event fields selected during pilot scoping, including model_version, rule_set, inputs_hash, decision label, and authority reference when present.
  • Server-side proof metadata: proof_id, pack, intent, timestamp, signing algorithm, key ID, and signature.
  • Optional evidence deposit and final proof after execution, when the partner wants a plan-to-result chain.
  • Optional daily batch anchoring through a configured RFC 3161 TSA endpoint.
EVIDENCE CLAIM SCOPE

This is a missing-control argument. VERIFIED means structural properties, not semantic content.

What a Notary Cloud record asserts:

  • The server created the record at the stated timestamp.
  • The record binds the supplied model_version, rule_set, and inputs_hash to that decision event.
  • The signature and append-only sequence make alteration after creation detectable under the configured key custody model.

What it does not assert:

  • The OEM agent made the correct decision.
  • The record satisfies a specific regulatory bar in every matter.
  • The OEM product or customer is certified compliant.
Where it sits

The decision layer stays yours.

Notary Cloud receives a decision event after your agent has decided. This static sample verifier is published under /r/prf_b2db1741f051443e.

01

OEM AI agent decides

Your agent decides the alert, case, or compliance action inside your product.

decision layer stays yours
02

Event is recorded

Your backend posts the scoped decision event to the lifecycle API.

/v1/enforce/{pack}/{intent}
03

Signed proof returns

Notary Cloud returns proof metadata bound to the submitted event.

proof_id + key_id + signature
04

Verifier can open

The static verifier page can be shared when policy allows access.

/r/:proof_id

Pilot deployments default to ECDSA-signed records. Internal-only signing modes do not produce externally-verifiable evidence.

Boundary

Evidence integrity, not decision logic.

  • Does not decide alerts.
  • Does not screen transactions, customers, or sanctions lists.
  • Does not replace your decisioning product.
  • Does not store customer PII by default. Pilot schemas should use hashes and metadata.
  • Does not certify regulatory compliance.
  • Does not make legal claims about audit sufficiency.
  • Does not assert absolute immutability. The claim is tamper-evident custody.

Structurally aligned with US FinCEN NPRMs FINCEN-2026-0034 AML/CFT and FINCEN-2026-0100 PPSI, and with EU AI Act Articles 11(1), 12, 26(1), and 26(6) deployer evidence obligations.