HOW IT WORKS

The verification engine.

The engine sits between the model and the tool. Everything that enters becomes a typed fact with a citation. Everything that leaves carries the chain that produced it. This is the substrate that lets an agent take consequential action without inheriting the model’s failure modes. Verification is not a layer on top. It is what the engine does.

DATA FLOW

Inputs in, verified artifacts out, chain attached.

Every fact in the substrate sits in one of four states: extracted, computed, unverified, or in disagreement. The state determines what the engine will do with it. The verdict colors in the substrate below map directly to these states.

01 · INGEST
02 · SUBSTRATE · TYPED FACT STORE
PDFmsa.pdf
doc_extractor
APIstripe.api
feed_extractor
CSVcrm.csv
schema_extractor
PDFinvoice.pdf
doc_extractor
CSVaccounts_payable.csv
schema_extractor
DBcert_db.postgres
schema_extractor
specialised extraction agents route by data type. one verification loop downstream.
acme_corp · plan · billing
Enterprise
stripe.api
acme_corp · plan · contract
Enterprise
msa §4.1
acme_corp · plan · crm
Pro
crm.csv
acme_corp · mrr
$4,800
stripe.api
invoice_417 · amount_due
$487,000
invoice.pdf
ap_record_89 · amount_due
$486,200
ap.csv
vendor_217 · soc2_current
TRUE
cert_db
vendor_412 · iso27001
27d expiry
cert_db
order_4821 · refund_amount
$124.50
computed
po_2841 · amount
$48,200
po_request
vendor_88 · lead_time
14 days
schedule.xlsx
ledger_4198 · balance
$2.14M
computed
form_adv · regulatory_aum
$4.83B
adv §8
credit_C44 · tier
A
credit.pdf
supplier_88 · delivery_eta
5 days
schedule
acme_corp · renewal_date
2026-07-01
msa §5
vendor_217 · spend_ltm
$284K
computed
invoice_418 · amount_due
$12,400
invoice.pdf
vendor_53 · approval_status
approved
vendor_master
policy_v4 · tolerance
$100
policy.docx
FACTS184,302
RULES412
CONFLICTS7
sample engine state · illustrative·engine · running
FOUR VERIFICATION PASSES

What the engine does, every run.

When a workspace runs, the engine executes the four passes over its typed facts. Each pass is independent. The results compose into the proof chain for every output.

01

Source verification

Does the value actually appear in the source at the cited coordinate.

This is the check that catches extraction errors. OCR misreads, table parser drift, model fabrication. Run mechanically by comparing the extracted value to the source text at the citation.

EXAMPLE
value · S p.X · ✓ matches source text
02

Identity verification

Do the rules in the rule library hold against the facts.

Definitional identities and constraints are formulas. The engine plugs the workspace facts into them and checks the result. A failed identity is a hard finding.

EXAMPLE
A + B = C · ✓ holds across workspace
03

Cross-source verification

Do the sources agree on facts more than one of them speaks to.

Facts are paired on (entity, metric, period) triples and compared. Disagreements are classified by severity. Detailed on the cross-source page.

EXAMPLE
source A vs source B · paired · agree | drift | conflict
04

Independent computation

For every value that can be derived, derive it and compare.

Two paths to the same number is a stronger guarantee than either path alone. If extraction and re-derivation agree, the value is verified in a way no single reading can match.

EXAMPLE
extracted V vs computed V · ✓ equal
DISAGREEMENT SEVERITIES

Disagreements are findings, not errors.

The engine’s job is to find them, classify them, and present them. The user’s job is to adjudicate. The system records the decision and the decision becomes part of the chain.

ADVISORY

Small delta. Informational.

Rounding, restatement, presentation convention. Surfaced as informational. The user sees it. The output is not blocked.

MATERIAL

Large enough to require a decision.

The user must adjudicate before the output is produced. Surfaced as a blocking gate. The decision is recorded as part of the chain.

STRUCTURAL

An identity cannot hold under any reading.

The balance sheet cannot balance. The system cannot pick a side. Surfaced as a hard finding. Output blocked until the underlying conflict is resolved.

The engine your agent posts to.

Every proposed action goes through the four passes. The verdict comes back with the full chain attached. Wire this in once and your agent stops acting on facts it cannot defend.