Skip to main content

Policy Intelligence Team

Module: insight:policy | Role: Any member | Licence: Pro+ Dispatch tools: ask_policy_explorer, ask_policy_librarian, ask_policy_navigator, ask_policy_analyst, ask_policy_steward

The Policy Intelligence team is a built-in agent team gated behind the insight:policy module. It provides five specialized agents for regulatory intelligence across US, UK, Canadian, and Dutch jurisdictions.

Team Agents​

AgentPatternRoleKey Capabilities
Policy ExplorerExplorerMonitor external signalsWeb search for regulatory developments, scan entity portals, fetch specific URLs
Policy LibrarianLibrarianStore and retrieve knowledgeManage the regulatory knowledge vault, store/update notes, search findings
Policy NavigatorNavigatorTrack and flagTeam interests, personal alert prefs, watchlist management, entity portal tracking
Policy AnalystAnalystSynthesize and reportGenerate digests, collect feedback, accept user-submitted findings, preview drafts
Policy StewardStewardWatch and defend the vaultMine team chat for coverage gaps, scan the vault for anomalies (dead URLs, new-source domains, duplicates), flag or remove unreliable findings, post a daily summary to #policy

Tools by Agent​

Policy Explorer (Researcher)​

ToolDescriptionCost
researcher_searchSearch the vault for existing findingsFREE
researcher_scanSystematic scan of entity portals and jurisdiction-specific sourcesMODERATE
researcher_fetchFetch and clean content from a specific URLFREE
web_searchAnthropic server-side web searchFREE

Policy Librarian​

ToolDescriptionCost
librarian_querySearch and retrieve from the knowledge vault (by text, category, tags, or note_id). Call with no args for vault summaryFREE
librarian_storeStore a verified finding in the vault (with dedup checking + jurisdiction-aware routing)FREE
librarian_deleteRemove a note by IDFREE
librarian_indexFast snapshot of vault contents grouped by folder, with aggregate breakdowns by category, relevance, and top tags. No content bodiesFREE
librarian_updatePatch metadata (tags, relevance, category, title, source, source_url) on an existing note without re-submitting contentFREE

Policy Navigator​

ToolDescriptionCost
policy_configRead/write team interests (jurisdictions, topics, cadence), personal alert prefs, entity portal tracking, chat mining toggleFREE
tracker_addAdd a specific item to the watchlist (proceeding, legislation, etc.). Also stores a vault note so the Librarian can find itFREE
tracker_listList watchlist items, filter by status/jurisdiction/typeFREE
tracker_updateUpdate priority, keywords, status, or close a watchlist itemFREE

Policy Analyst​

ToolDescriptionCost
analyst_digestRead latest digest, generate a fresh one, or preview the next draftFREE (read/preview) / EXPENSIVE (generate)
digest_feedbackSubmit feedback signals on findings: relevant, irrelevant, outdated, misclassified, correction, mute_topic, mute_sourceFREE
submit_findingSubmit a policy news item for inclusion in the next digest. Queued, then merged into the next digest and stored in the vault permanently.FREE

Policy Steward​

ToolDescriptionCost
steward_mine_signalsMine recent team chat messages for coverage gaps and regulatory topicsMODERATE
steward_query_signalsRetrieve signals from the most recent chat mining runFREE
steward_mine_vault_anomaliesScan the vault for anomalies (dead URLs, duplicates, future-dated events, new source domains). Flags or removes unreliable findings within a per-run rate limit; every mutation is git-auditedMODERATE

Knowledge Vault​

The Policy Librarian maintains a structured knowledge vault with:

CategoryContains
RegulatoryPer-jurisdiction frameworks, proceedings, findings (append-only ledgers)
ReportsExternal research reports and industry studies
Positionsev.energy company positions on policy topics
Case StudiesUtility program case studies

Querying Knowledge​

Ask the policy librarian in conversation:

"Ask the policy librarian about FERC Order 2222 in California"

Eve dispatches to the librarian, which searches the vault and returns matching notes with sources and metadata.

Vault Gardening​

The Librarian can audit and maintain vault health using librarian_index and librarian_update:

  1. Run librarian_index to get a snapshot of all notes with metadata quality indicators
  2. Identify notes with missing tags, wrong relevance, stale categories, or no source URL
  3. Use librarian_update to patch metadata without re-submitting the full note content
  4. Use librarian_delete to remove duplicates or obsolete notes

Workflows​

Nightly Regulatory Scan​

The Explorer runs nightly to scan for new regulatory developments, appending findings to jurisdiction-specific findings files with unique IDs (e.g., CA-20260401-001).

On-Demand Research​

Ask Eve: "What's the latest on VPP policy in New York?" — Eve dispatches to the Explorer for web research and the Librarian for vault context.

Regulatory Digests​

The Analyst generates periodic jurisdiction digests summarizing recent findings, upcoming deadlines, and recommended actions. Digests have four sections:

  • Headlines — breaking regulatory events this period
  • Proceeding Updates — new activity on tracked dockets
  • Watch List — upcoming implementation deadlines
  • Tracked Items — status of each watchlist item (update found or no activity)

Digests enforce a freshness ceiling: items whose real-world event is older than the team's configured maximum age (default 30 days) are suppressed rather than re-surfaced, and the digest preamble reports how many were suppressed. Admins can tune this with policy_config(max_finding_age_days=...).

Preview Before Sending​

Use analyst_digest(preview=true) to see what the next digest would contain — vault findings, user submissions, and applied feedback — without generating or storing anything.

Digest Feedback​

Users can improve future digests by providing feedback signals:

SignalUse when...Required field
relevantA finding was usefulfinding_id (optional)
irrelevantA finding wasn't relevantfinding_id (optional)
outdatedA finding is stale (deadline passed, info old)finding_id
misclassifiedWrong jurisdiction, topic, or typefinding_id + correction fields
correctionFactual error (wrong date, detail)finding_id + correction fields
mute_topicStop showing a topictopic
mute_sourceStop showing a sourcesource

Feedback is applied automatically: outdated/irrelevant findings are excluded, muted topics/sources are filtered, and corrections are passed to the Analyst for the next digest.

Submit Missing Findings​

When the digest misses something, users can submit policy news directly:

"Add this to the next digest: CalChoice is launching DERMS for VPP support"

The finding is:

  1. Queued in the submission table (status: pending)
  2. Merged into the next digest generation automatically
  3. Stored in the vault permanently so the Librarian can find it in future searches

Watchlist Tracking​

The Navigator maintains a watchlist of proceedings and deadlines, flagging items that need attention. When a tracking item is added via tracker_add, it is:

  1. Created in the tracking database (for nightly scan prioritization and digest reporting)
  2. Stored as a vault note (so the Librarian can find it in knowledge searches)

After adding a tracked item, the Navigator checks if its jurisdiction is in the team's scan scope and prompts to add it if not.

Configuration​

Workspace admins configure the policy module via workspace settings:

  • Jurisdictions: Which states/countries to monitor
  • Topics: Filter for relevant policy areas (DR, VPP, DER, rate design, etc.)
  • Digest delivery: Recipients and frequency
  • Personal alerts: Per-user topic preferences (controls @-mentions in digests)
  • Entity portals: Custom URLs for the Explorer to check on each scan
  • Chat mining: Automatic weekly analysis of team chats to discover coverage gaps (default: on)
  • Digest style: Workspace-specific tone, section ordering, and phrasing preferences for the digest. The platform default applies unless an override is saved on the Digest Style tab. Hard rules — every finding must appear, no fabrication, no jurisdiction collapsed — are enforced in code and cannot be turned off via the override.

Data Flow​

User submits finding ──→ policy_user_findings (DB queue)
│
Navigator: tracker_add ──→ tracking_items (DB) + vault note (git)
│
Nightly: Explorer scans ──→ Librarian stores ──→ vault (git)
│
┌────────────────────┘
▼
Analyst: collect_findings (vault) + pending submissions (DB)
→ exclude outdated/irrelevant (feedback)
→ merge user submissions
→ Claude synthesis
→ store digest (DB) + mark submissions included
→ store user submissions in vault (permanent)
→ deliver (in-app, email, Slack)

Module Requirement​

Requires insight:policy module. Available on Pro and Enterprise licence tiers. Contact your account manager for access.