VerisGov
Get started

SOURCE / DOCUMENTS

Documents. The written record government runs on.

Rules, guidance, waivers, and manuals: the prose that decides what a program funds and who qualifies. The engine reads it, pins each claim to the page it came from, and tells you when it changes.

Sources documents

Get started All sources

What it is

A government document is the written instruction set behind every program: the regulation, the guidance, the waiver, the manual that says what is allowed, who qualifies, and how the money is spent. Most of the answers people need are already written down. They are just spread across thousands of pages, on dozens of agency sites, in language built for filing rather than reading.

The challenge

Documents are published to be archived, not queried. A single rule can run hundreds of pages, reference a dozen others, and get quietly revised months later. The version you read today may differ from the one you cited last quarter. The engine keeps the exact text you saw, with the date and the source, so the claim still holds when someone checks it.

What the engine pulls from documents

  • Regulations and final rules that set what a program funds
  • Agency guidance, manuals, and program instructions
  • Waivers and state plan amendments that change the rules per jurisdiction
  • Eligibility and conditions language that decides who qualifies
  • Public memos and decisions that move money or set policy
  • The exact passage behind every claim, kept at the version you saw

In practice

An advisor needs the eligibility language for a waiver. The engine returns the exact passage, the document it lives in, and the date it was last changed, so the advice rests on the rule as written, not a summary of it.

How the engine handles it

Every source runs the same five auditable stages, so what reaches you carries the record of where it came from and when it was checked.

  1. find
  2. store
  3. retrieve
  4. verify
  5. productize

Other sources the engine ingests

Datasets Tables, open data, and APIs: the numbers. Filings Audits, disclosures, and reports: what was done. Notices Opportunities and deadlines: the clock. Portals Lookup tools and dashboards: data behind a form.

Questions

What counts as a government document?

The written instruction set behind a program: regulations and final rules, agency guidance and manuals, waivers and state plan amendments, and the public memos that set how money moves. If it is published prose that decides what is allowed or who qualifies, the engine treats it as a document source.

How does VerisGov keep a document current?

A document is watched at its government source. When the text changes, the engine captures the new version alongside the old one, so you can see what moved and when. The exact passage you cited stays retrievable even after the page is rewritten.

Can I trace a claim back to the document it came from?

Yes. Every claim drawn from a document links to the passage and the source it came from, at the version that was read. You can confirm any fact at its origin in one click.

Which products are built from documents?

Documents feed navigators, reports, and dashboards, anywhere a program's rules and eligibility need to be stated precisely and traced to the page that governs them.

From this source to a verified product.

Tell us the source and the question. You get a working product, every fact pinned.

Get started See what you can build

Every document source the engine holds

Every document behind the programs the engine covers: statutes, regulations, agency guidance, fact sheets and research reports. Where the tier reads held and sealed, the bytes are on disk with a SHA3-256 you can recompute against the published file.

  • 442sources
  • 133held and sealed
  • 251on a .gov domain
  • 202distinct domains
  • 12.9Mcharacters held
  • 3we could not hold

Showing all 442