Skip to content

Two-Track Source Classification (Statute vs. Regulation)

Questions or comments?

Post them as a comment on the tracking issue -- requires a GitHub account with access to this repo.

Scope

A Legal Track attribute — Statute (Track 1) or Regulation (Track 2) — captured on every ingested document, distinguishing a USC statute from the CFR regulation that implements it. The track is assigned automatically at crawl time based on which government source feed a document came from (USC feed vs. CFR feed), and is confirmable/correctable by the SME reviewer during document review, alongside the document's other attributes on the Document Review screen. Per ../schema-changes.md, no field for this exists on ingested documents today (only CFR-specific cfr_title/ cfr_part metadata fields exist) — this is a net-new field.

Value

Without this distinction, the advisor risks telling a user it's citing "the law" itself when it's actually citing the implementing regulation — a meaningful error in a compliance context, not a pedantic one.

Acceptance criteria

  • Every newly ingested document is auto-tagged statute or regulation based on its source feed at crawl time.
  • The SME reviewer can view and correct the assigned track on the Document Review screen (../curator-ops-dashboard/spec.md) before Accept.
  • The tag is queryable/filterable (e.g. for the ops dashboard's coverage breakdowns), not just stored as opaque metadata.
  • Existing CFR-tagged documents (via cfr_title/cfr_part) default to regulation under this new field without requiring a full re-crawl — confirm a backfill approach at construction time.