DEA Scheduling Monitor

The problem. Controlled-substance scheduling moves through the Federal Register in several document types at once, and the ones that decide anything — final rules, proposed rules, temporary orders, quotas — arrive mixed in with registrations and routine notices. Reading it raw means sorting signal from filing traffic by hand.

What it does. Pulls DEA documents from the Federal Register API over a rolling 180-day window and sorts them into high-signal actions, final rules, proposed actions open for comment, and quota and temporary orders. Registrations and general notices stay available as reference categories, and the counts across views reconcile to the same document set rather than being computed separately.

Built on. Scheduled collection against federalregister.gov, the primary source, with a source-health panel that reports the refresh cadence so a stale feed shows as stale.

What it does not establish. Automated document discovery, not legal analysis. It tells you a document exists and what type it is; it does not tell you what it means for any particular substance, registrant, or programme.

This record is generated from the same inventory as the complete build index: the production URL was checked at the last regeneration, and the status line above repeats what the build reports about itself rather than restating an intention.