Get Regulatory Intelligence Status
get_regulatory_intelligence_statusReport what this service actually monitors and how current each source is: the enrolled sources, their publisher, channel kind and jurisdictions, when each last synced successfully, its freshness state (current / stale / critical / unfetched / baseline-only), how many records it holds, and when its baseline backfill ran. Also reports the state of the signed licensing verdict that governs which sources may be fetched at all.
Read this before concluding anything from an empty search: a source that is not enrolled, or whose state is critical, is not covered, and this tool says so plainly. enrolled means the current verdict clears the source AND its acquisition proof is verified.
Also reports the state of the curated obligations calendar behind get_regulatory_deadlines: obligations.dataset_state is ok (the newest signed dataset is what serves), degraded (a newer dataset exists that this service could not read, so the previous one is still serving — resolution_reason says why, anomalous_release names the release, degraded_since says when that was last confirmed), or unavailable (none ever loaded, so the deadlines tool refuses). It also reports how many curated rows and pending-instrument rows are held, when the curators last changed the dataset, and which signed generation this service consumed. That is the free surface for a premium tool — a caller whose deadlines request refused, or came back degraded, can find out here why, without a tier.
The lane_f block reports the fleet-derived event lane: publications detected on the official indexes the corpus fleet itself watches, consumed only when THREE gates pass — the signed licensing verdict clears the fleet source (with verified acquisition), a signed per-target eligibility decision exists at the detection's exact target configuration digest, and a current signed events artifact verified. It carries the events-artifact state, the inbox counts (pending / stored / invalid), and suppressed_duplicates — publications observed by both an enrolled registry source and a fleet target are served ONCE, by the registry lane, and every suppression is counted here rather than silently dropped.
The verdict block also carries disposition_summary: the disposition-class counts exactly as the consumed signed artifact delivered them, or null. Null is 'this service has no counts to report' and never 'the register is empty' — the consumed generation carried none, no verdict has been consumed yet, or this server is running ahead of the migration that stores them. Its keys are exactly enrolled_event_feed (fleet event-feed sources in the signed launch set), cleared_event_feed (how many of those the verdict clears) and register. register is one of exactly two shapes: the projection, whose keys are exactly generated_at, fleet_sha, total_rows, by_disposition (keys exactly event_feed, signal_only, blocked) and unclassified; or unavailable_reason alone, which says the register could not be read when the artifact was published. The register numbers project a separate artifact generated at its own time — read its generated_at and fleet_sha before comparing them with anything else here, and read unclassified before treating the classes as complete.
Example: "Using Ansvar, which regulatory sources are you monitoring and how fresh are they?"
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||