Coverage map

The index starts with sources, then becomes searchable data.

This page is the public source inventory for the MVP. The important promise is not a polished search box yet; it is a durable map of which official sources HLII watches, how often they move, and what can be exposed safely through aggregate endpoints.

All 50 states Congress Federal circuits Supreme Court Areas of law

Legislatures

State + federal

Every state legislature and Congress belong in the coverage map. The source record should track URL, collector status, freshness, available fields, and known quirks.

Courts

Appellate only

Court coverage stays limited to federal appeals circuits and the Supreme Court. That line keeps collection manageable and avoids pretending trial-level data is normalized.

Topics

Plain-language tags

Topic tags should be explainable to non-specialists and useful to agents: privacy, housing, labor, firearms, education, elections, healthcare, and other stable domains.

Endpoint shape

What the first aggregate API should expose

Sources

Coverage and freshness

Jurisdiction, source URL, collector name, last successful check, last observed movement, current status, and notes about source quirks.

Movement

Aggregate legal events

Counts and recent examples by jurisdiction, topic, source type, and stage. This is useful before opening full-text legal record search.

Reports

Human-readable findings

Published reports remain the stable public artifact while collection logic matures. They also give agents a small, reliable citation surface.

MCP

Tool-safe queries

Start with bounded tools: get source status, list recent movement, summarize topic drift, and fetch report metadata. Keep writes private.

Limits

What stays out

No private user data, no legal advice, no lower-court firehose, and no expensive AI endpoint on the public path until usage justifies it.

After the model settles

Full-text search should come after the source records and aggregate event schema are boring enough to leave alone.

Current public JSON

Start with the report catalog

`/api/reports` is the only public dynamic endpoint today. That is a good MVP boundary: readable, cheap, cacheable, and safe while the source and movement endpoints are still being shaped.