Ingestion & Normalisation
The interaction enters the pipeline. Payload validated, canonicalised under RFC 8785, hashed under SHA-256, timestamped at ingestion.
interaction_hash = SHA-256(payload_canonical)
VERIDOM · OPERATING MODEL PROTOCOL — OMP™
Evidence infrastructure for regulated industries. Every interaction resolves to one of three accountable outcomes — and the proof is sealed at the moment of decision, verifiable by any third party without access to your systems or ours.
THE PREMISE
01 — THE PROBLEM
The institution has the right policies. Its agents and systems do not consistently follow them.
The practice happens — but the evidence trail is incomplete, reconstructed, or missing entirely.
The evidence exists, but cannot be produced in the form a regulator requires, when the regulator requires it.
The dominant market response is observational — monitoring, dashboards, retrospective reports. It addresses the third layer at best. OMP closes the gap architecturally, at the point of decision: the wrong outcome cannot be produced without a sealed, externally verifiable record of why it was produced and under whose authority.
02 — WHAT YOU GET
When the question comes — from a regulator, an auditor, a court — what you need is the record. Veridom installs the layer that produces it, and hands you the proof.
A structured assessment of where your institution's evidence gap is widest — decision by decision, system by system. You see exactly what you can and cannot prove today.
ENGAGEMENT · THE STARTING POINTThe protocol installed above your existing stack — any model, any vendor. Deterministic routing, named accountability, and sealed evidence on every AI-mediated decision.
INFRASTRUCTURE · YOURS, NOT RENTEDA sealed, regulator-ready evidence pack covering every AI-mediated interaction in the period — produced in under 30 seconds, verifiable by anyone.
DELIVERABLE · EXAMINER-READY03 — THE PROTOCOL
The Decision Engine determines what the system does. The Evidence System proves what the system did.
The interaction enters the pipeline. Payload validated, canonicalised under RFC 8785, hashed under SHA-256, timestamped at ingestion.
interaction_hash = SHA-256(payload_canonical)
Hash integrity re-verified — any mismatch escalates immediately. The interaction is classified to a registered Intent Class with its own routing threshold θ.
mismatch → ESCALATED · ESC-09
Domain-specific enforcement rules evaluated in priority order. Every Watchtower's verdict is recorded — whether or not it fired.
severity ∈ { HARD_BLOCK, FORCE_ASSISTED }
The deterministic routing function assigns exactly one outcome state. For ASSISTED and ESCALATED, a named accountable human is bound to verifiable authority — or execution is refused.
R(C, W, θ, φ) → { AUTONOMOUS · ASSISTED · ESCALATED }
The complete Audit Trace is sealed: content hash, RFC 3161 trusted timestamp, institutional signature, Merkle chain entry. Appended to the append-only ledger.
H_content → TST → signature → H_c
04 — THREE STATES. NO FOURTH OPTION.
Adjust the inputs below. The outcome is computed, not judged — identical inputs always resolve to the identical state.
Confidence clears the threshold. The system dispatches without human review — and the full trace is still sealed.
Confidence clears θ. No Watchtower objection. Dispatched without review; trace sealed.
A named accountable human must approve, edit, or reject before dispatch — under bound authority.
Direct human handling under SLA. Hard blocks, policy violations, ambiguous intent, low confidence.
05 — THREE INVARIANTS
Given canonicalised inputs — payload, source-state hashes, pinned model configuration — the routing outcome is deterministic. Identical inputs produce identical outcomes.
Every decision is sealed at the moment of decision: SHA-256 over canonical JSON, RFC 3161 trusted timestamp, institutional signature, Merkle-chained ledger.
Every ASSISTED or ESCALATED decision binds a named accountable human to verifiable authority at the moment of decision — or execution is refused, and the absence itself is sealed.
06 — VERIFIABLE WITHOUT TRUST
Below is a sealed Audit Trace. Verification recomputes the SHA-256 content hash live in your browser — the same check a regulator, court, or auditor runs. Then tamper with it, and watch the seal break.
SHA-256 over the canonical trace, recomputed from the record itself.
TimeStampToken checked against the accredited TSA's public certificate.
The institution signs with its own key. Verification is independent of any vendor.
Each trace incorporates the previous trace's hash. History cannot be rewritten quietly.
07 — FOUR REGULATED DOMAINS. ONE CONSTRAINT SET.
Vertical configurations change — Watchtowers, thresholds, authority anchors. The protocol does not.
Lending Decisions
Per-decision evidence for digital lenders under FCA supervision — affordability, creditworthiness, and limit decisions. Watchtowers tuned to lending failure modes; accountability anchored to SM&CR responsibilities.
Retail Financial Services
Board-defensible outcome evidence for AI-mediated pricing, lending, and support decisions. Accountability anchored to SM&CR Statements of Responsibility.
Payments — Agent Distribution
Eliminates principal-agent blindness across distribution networks. Fully automated Watchtowers; accountability anchored to the principal firm's delegation matrix.
Citation Verification
Two-gate citation verification with a supervisory compliance manifest. Court-filing consequence demands θ ≥ 0.992. Accountability anchored to the supervising attorney.
08 — BUILT FOR BOTH SIDES OF THE TABLE
09 — THE OPEN LAYER
The full OMP™ specification is published for anyone to read, implement, and test against — twelve Internet-Drafts at the IETF, covering the core protocol and vertical profiles from UK Consumer Duty to the EU AI Act.
That openness is the point. Your auditors, your regulators, and your counterparties can check OMP™ evidence without asking Veridom — or anyone else — for permission. No proprietary formats. No gatekeepers.
READ IT · IMPLEMENT IT · VERIFY AGAINST IT
The core OMP™ protocol — routing architecture, authority binding, cryptographic evidence standard.
IETF DATATRACKER ↗ INTERNET-DRAFTUK FCA Consumer Duty profile — outcome evidence for retail financial services.
IETF DATATRACKER ↗ INTERNET-DRAFTEU AI Act profile — Article 14 human oversight evidence for high-risk AI systems.
IETF DATATRACKER ↗ SPECIFICATIONThe full specification — published with a permanent DOI on Zenodo (CERN).
DOI 10.5281/zenodo.19140948 ↗Initial engagements are diagnostic — a structured assessment of where your institution's evidence gap is widest. Share the institution, context, and gap you need to resolve, and we will determine whether a Veridom diagnostic is the right next step.