Legal Data Infrastructure: Provenance, Freshness, and Change
What separates a legal text API from legal infrastructure: where each section came from, how often it refreshes, how a change is detected and delivered, how a citation resolves, and what the response schema guarantees.
13 posts in this cluster
Legal Data Provenance: How to Tell Where a Statute Actually Came From
A five-question provenance test for any legal data API: source URLs, government publishers, retrieval dates, currency statements and declared gaps.
Legal Data Freshness: What Refresh Cadence Actually Means, Source by Source
A per-source refresh cadence table for US primary law, why 24 jurisdictions can be pulled whole, the Colorado case, and a cron to verify freshness yourself.
Why Legal Data Cannot Refresh Faster Than Its Publisher
The four things that decide how fast a US primary law corpus can refresh, why polling faster than the publisher is theater, and how to verify any claim free.
How We Know a Law Changed: Boards, Diffs, and the False Positives Nobody Talks About
How change detection over government legal sources works: the refresh and reconcile loop, the boards registry, per-section diffs, and the false positives.
Law Change Alerts API: Webhooks for When a Statute or Rule Actually Moves
How a law change alerts API works: boards, watches, per-section diffs, webhook delivery, and why you still poll the changes endpoint as your source of truth.
Amendment History and Point-in-Time Law: What a Legal API Can and Cannot Tell You
Point-in-time law comes in two forms with different guarantees: a published edition you can cite, and a reconstruction you cannot. How to tell them apart.
Legal Citation Resolution: Turning a Cite Into the Right Section, Every Time
How legal citation resolution works: state style manuals, colloquial names, renumbered codes, why one regex fails, and what to return when it does not know.
Parsing Legal Citations in Code: Bluebook Forms, State Variants, and the Ones You Must Refuse
How to parse US legal citations in code: the real shape classes, five traps that silently break resolution, and why refusing an ambiguous form beats guessing.
What a Legal Data API Should Guarantee: The Schema Contract
A legal data API becomes infrastructure when it states which fields are always present, which are corpus-specific, and what each means. Here is that contract.
128 Fields on One Statute: What Rich Legal Metadata Actually Buys You
A field-by-field walk through 128 metadata fields on a US primary law API response, and the product feature each family unlocks that text alone cannot.
Hybrid Search Over 12 Million Legal Passages: Why Semantic Alone Fails on Law
Pure vector search breaks on statutes in three ways. The diagnosis, the hybrid plus rerank plus citation fast-path fix, and a test protocol you can run today.
From a State Website to an API Response: Every Layer a Legal Corpus Passes Through
The path a US primary law document takes from a government site to an API response: eleven layers, nine gates that default to fail, and four audit ledgers.
Evaluating a Legal Data Vendor: The Security and Deployment Questions to Ask
Eight questions to ask any US primary-law data vendor, in the order that actually reduces risk, with what a good answer and a bad answer sound like on each.