The engine, end to end
Government data in. Verified product out.
VerisGov runs every source through the same five stages. Each one is auditable, and every fact that reaches you carries the record of how it got there.
-
Government publishes the answer first and announces it almost never. The engine continuously locates the programs, datasets, reports, dashboards, and software across federal, state, and local sources, and notices the moment any of it moves.
What happens
- Sweep federal, state, and local sources on a schedule, not in a one-time crawl.
- Track the five source kinds: documents, datasets, filings, notices, and portals.
- Watch known sources for change, so a quiet revision does not slip past.
- Surface what is new, what moved, and what was retired, with the date each was seen.
FIND on the record - scope
- federal / state / local
- cadence
- continuous
- signal
- new / changed / retired
The answer is usually already public. The work is knowing where it lives and noticing when it changes, before it costs you a deadline.
-
Everything found is captured into a durable, content-addressed corpus. Each record is held with its origin and a fingerprint, so the version you cited is still there when someone checks it months from now.
What happens
- Capture the artifact as published, not a summary of it.
- Fingerprint every record, so identical content is provable and duplicates collapse.
- Keep prior versions beside the current one, with the date each was seen.
- Hold the origin and the retrieval time on every record.
STORE on the record - addressing
- content-addressed
- history
- point-in-time
- origin
- source + timestamp
Government pages move and get rewritten. A point-in-time record is what makes a claim defensible long after the page behind it has changed.
-
Ask a question the way you would ask a colleague. Retrieval is grounded in the stored corpus, so what comes back is the exact record with its context, and the source travels with the answer.
What happens
- Query in plain language across the whole corpus.
- Get the exact passage or field, not a paraphrase of it.
- Every answer arrives with its source and version attached.
- Grounded in stored records, so there is nothing to invent.
RETRIEVE on the record - input
- plain language
- grounding
- stored corpus
- output
- record + source
An answer you can trace is worth more than an answer you have to re-check. Retrieval that carries its source turns a search result into something you can act on.
-
Every fact is checked against its government source and sealed with a provenance record: where it came from, when it was checked, and whether it has changed since. The one stage you cannot skip and stay trusted.
What happens
- Check each fact against the live government source it claims.
- Seal it with a provenance record: source, time of check, and status.
- Flag anything that has changed since it was last confirmed.
- Keep the check reproducible, so anyone can confirm it at the origin.
VERIFY on the record - source
- government origin
- checked
- timestamped
- status
- current / changed
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.
-
Turn the verified corpus into navigators, dashboards, reports, datasets, and software, all drawing from one source of truth, every fact still pinned to where it came from.
What happens
- Shape one verified corpus into the product your team already uses.
- Choose a navigator, dashboard, report, dataset and API, or a custom build.
- Keep every number traceable to its government origin.
- Update as the source updates, so the product never quietly drifts.
PRODUCTIZE on the record - outputs
- five product types
- source
- one verified corpus
- trace
- every field
See everything you can buildInsight pays off when it reaches the people doing the work, in the form they already use. Productize is where verified intelligence stops being a corpus and starts being leverage.