The Gate · Financial Services
Financial services.
The model proposes. The file proves.
Banks are putting agents inside the work — in the model, in the queue, in the refund flow. When one of those agents is wrong, the question that arrives is never what the model said. It is what the bank can prove: who ran it, on what inputs, under whose instruction, decided by which rule. Verity keeps that file — a sealed, independent record of every proposal, decision, and rule, held by a party that is neither the vendor nor the bank.
The argument, in full: What Bankers Need (It Isn’t a Model) — our dispatch on the banker-agent market, and on the line item nobody has priced.
The Record · Live
A chain you can check, not a claim you have to take
Every verdict the gate returns is sealed into a hash-linked chain, and the chain’s head is periodically timestamped by DigiCert’s public timestamp authority. The panel below is that ledger, read from the same public endpoint anyone can fetch — no key, no account.
This record’s age is countersigned by DigiCert’s clock — not asserted by Verity.
Snapshot · verified 17 November 2026The first anchor — № 1 · 3 Nov 2026 · 04:00:10 UTC · sealing record 13 — was countersigned on 3 November 2026. The record has been growing, in public, ever since.
| Anchor | Seals record | DigiCert time (UTC) | Status |
|---|
Fetch the ledger
GET https://api.verityverdict.com/api/v1/chain/anchors — public, no key, no account. What this panel shows is what that address returns.
Pick any anchor
Its imprint is the hash of the chain head at that moment; its token hash is the fingerprint of the timestamp token DigiCert issued for it.
Verify the token
DigiCert’s timestamp service (timestamp.digicert.com, RFC 3161) is public. The signed time inside the token is DigiCert’s, and it either verifies or it doesn’t — a record backdated after the fact cannot produce a token carrying an earlier time.
Use Case 01 · The Desk
A trade submission, crossing the gate
A banker’s agent drafts a trade and proposes it. Nothing reaches the market until the gate has answered — and the proposal, the verdict, and the rule that decided it are sealed together. Run both examples.
The submission, exactly as the agent proposes it — the prompt the gate judges:
—
In production, this record folds into the chain and is countersigned at the next DigiCert anchor. The chain’s latest anchor: № 32 · 17 Nov 2026 · 00:00:16 UTC · sealing record 374.
Example submissions and an example threshold — no real order, account, or customer is shown. The seal in step 3 is computed in your browser from the example text. The anchor in step 4 is the live chain’s real latest anchor.
Use Case 02 · The Support Queue
An agent that refunds — inside thresholds it cannot cross
A support agent with refund authority and no human in the loop is a liability with a smile. Behind the gate, the same agent works inside bands the bank sets for itself: small refunds it completes alone, larger ones it prepares for a human signature, and a class of refunds it is not permitted to propose at all. Every band leaves the same thing behind — a sealed record.
Example configuration — a bank sets its own bands
An example configuration, drawn to show the shape. Each bank sets its own bands, accounts, and rules — these thresholds are illustrative, not product defaults, and the seal shown is computed in your browser from the example.
The Pilot
Model ML is valued at $1.5 billion; Rogo at $2 billion — $3.5 billion priced into banker agents. The amount of it assigned to an independent record of what those agents do: $0. The first scandal in this market will not be a wrong answer. It will be an unrecorded one.