Stage 04 · Verify
Anyone can hand you a list. VerisGov hands you a list you can trust, because every fact is checked against its primary government source and sealed with a tamper-evident provenance record. Verified intelligence beats unattributed data the moment it is questioned.
How the engine works verify
Verified. Provenance-sealed.
Where this sits
What Verify means here
Verified is not a label we assign by hand. Each fact is read directly from the government page that publishes it, then sealed with a tamper-evident provenance record: the source URL it came from, when it was checked, and whether it has changed since. The fact and its proof travel together, so the version you saw is always the version you can point back to.
What a provenance record contains
Take a single Rural Health Transformation Program fact, pinned to its primary source on cms.gov. Its provenance record carries four things:
The primary government page the fact is read from, captured at its exact URL.
The moment the fact was last verified against that source, as a timestamp.
Whether the source still matches: unchanged, changed, or moved.
A tamper-evident stamp that ties the fact to the exact version that was checked.
Why verified intelligence holds up
TRUST
Every claim carries the link, the time, and the seal. Nobody has to take your word for it, and you do not have to take ours.
DEFENSIBILITY
When a number is questioned, you point to the primary source and the moment it was checked. A point-in-time record is what makes a claim stand.
CITABILITY
Verified intelligence travels into briefs, dashboards, and decisions with its source attached. Sourced facts stay usable; unattributed lists age.
Why it matters
Verification is what separates intelligence from a rumor. Every other stage exists to make this one possible, and this one is what makes the answer worth trusting.
Proven in production
RHTP Navigator runs on this verification model for the Rural Health Transformation Program: a per-state, source-pinned picture where every figure traces back to its primary government source. It is the model on this page, working in production.
Visit RHTP NavigatorThe procedure, in your hands
Verify is one stage of the engine. Inside it are six checks, and this is them, running in your browser. Choose what the government host hands back, then work down the rail. Every check has a control that tries to break it, and it either catches you or it does not. Nothing here is a diagram: check two is the system's own guard, and check four is a real hash chain.
The downloader asks a government host for a primary document. Here is the part that used to be taken on faith: every one of these replies is HTTP 200. Pick the one the host returns.
Tap one. Everything below reacts, and the strip above keeps score.
The response is a held fixture, not a live request. This page makes no network call, so what follows runs on your machine and nowhere else.
Before anything is written, the body is asked whether it is the document. A refusal notice and 20 CFR part 680 arrive identically: same status, same headers, same green light. Downstream, nothing can tell them apart. This is where they are told apart.
classifying
This is the classification itself, not an illustration of it: the same signatures, the same character floors, the same order of precedence that decide whether a fetched body is ever written. It runs here in full.
A held body becomes a provenance record: what was captured, where it came from, how, and when. Those are written down in a fixed order, every time, and that exact text is fed through a one-way fingerprint. Fixed order matters: it is why the same record always produces the same fingerprint, on any machine, years apart.
Each check seals the one before it, so a record cannot be edited after the fact without breaking every check made since. Edit the record below, or alter a digit, and watch where the chain gives way.
The figure is fetched again from a different endpoint than the one that built it, and the two are diffed to the cent. Re-reading the same endpoint would only prove the endpoint is consistent with itself, which nobody doubted.
A seal proves the record has not changed. It says nothing about whether the source has moved on. So the age of every check is carried with it, and past the cadence the record is due rather than current.
That age counts from the day you are reading this, resolved in Eastern time, not from the day the page was built. A record that measures its own age against a frozen clock will report itself current forever, which is the one thing a freshness claim must never be able to do.
Six checks, and the only one that can be argued with is the first. Everything after it is arithmetic you can re-run. A control you can operate is worth more than a claim you are asked to accept.
Tell us the source and the question. You get a working product, every fact pinned to where it came from.