Legal changes, linked to the documents they affect.
The registry contains 15,307 legal targets across 187 jurisdiction IDs. On the configurable scheduled run, targets with a source URL are fetched and analysed. Confirmed, actionable changes can flag affected documents with grounded source evidence.
- 15,307Registry entries
- 187Jurisdiction IDs
- 27Registry-referenced adapters
- 04:00 UTCDefault daily run
How the Watchdog works
Mapped source adapters
The codebase implements 32 adapter classes; 27 are currently referenced by registry entries. Only entries with a configured source can be fetched during a sync run.
Five-part analysis with evidence gates
The analysis checks relevance, actionability, concrete updates, applicability scope and verbatim evidence. Actionability is removed if no grounded quote or usable summary survives validation.
Conditional document flagging
A confirmed, actionable change can move affected documents to REVIEW_NEEDED. Unaffected documents stay untouched.
Guarded regeneration
Regeneration is protected against duplicate triggers and falls back to REVIEW_NEEDED if the operation fails.
What the registry does — and does not mean
Inventory, source retrieval and document action are separate stages. The published figures describe the registry and its currently wired adapters, not universal real-time coverage.
- Registry coverage
- The 15,307 targets across 187 jurisdiction IDs are inventory records. A jurisdiction ID is a technical reference, and a record without a source URL cannot be fetched.
- Scheduled source checks
- Configured targets are checked on the scheduled run when a source URL and compatible adapter are available. This does not imply continuous monitoring of every registry entry.
- Evidence-gated outcome
- A fetched change must survive relevance, actionability and evidence validation before affected document types can be marked. Otherwise the workflow leaves documents unchanged.
Evidence before action
A change is actionable only when the analysis identifies a concrete document impact and at least one verbatim quote is grounded in the fetched source. An empty summary or unverified evidence downgrades the result.
Confirmed changes. Traceable next steps.
When a source-backed change affects a document, the workflow records what changed, which document types are involved and why review is needed.