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
| Agent | Pattern | Role | Key Capabilities |
|---|---|---|---|
| Policy Explorer | Explorer | Monitor external signals | Web search for regulatory developments, scan entity portals, fetch specific URLs |
| Policy Librarian | Librarian | Store and retrieve knowledge | Manage the regulatory knowledge vault, store/update notes, search findings |
| Policy Navigator | Navigator | Track and flag | Team interests, personal alert prefs, watchlist management, entity portal tracking |
| Policy Analyst | Analyst | Synthesize and report | Generate digests, collect feedback, accept user-submitted findings, preview drafts |
| Policy Steward | Steward | Watch and defend the vault | Mine 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)
| Tool | Description | Cost |
|---|---|---|
researcher_search | Search the vault for existing findings | FREE |
researcher_scan | Systematic scan of entity portals and jurisdiction-specific sources | MODERATE |
researcher_fetch | Fetch and clean content from a specific URL | FREE |
web_search | Anthropic server-side web search | FREE |
Policy Librarian
| Tool | Description | Cost |
|---|---|---|
librarian_query | Search and retrieve from the knowledge vault (by text, category, tags, or note_id). Call with no args for vault summary | FREE |
librarian_store | Store a verified finding in the vault (with dedup checking + jurisdiction-aware routing) | FREE |
librarian_delete | Remove a note by ID | FREE |
librarian_index | Fast snapshot of vault contents grouped by folder, with aggregate breakdowns by category, relevance, and top tags. No content bodies | FREE |
librarian_update | Patch metadata (tags, relevance, category, title, source, source_url) on an existing note without re-submitting content | FREE |
Policy Navigator
| Tool | Description | Cost |
|---|---|---|
policy_config | Read/write team interests (jurisdictions, topics, cadence), personal alert prefs, entity portal tracking, chat mining toggle | FREE |
tracker_add | Add a specific item to the watchlist (proceeding, legislation, etc.). Also stores a vault note so the Librarian can find it | FREE |
tracker_list | List watchlist items, filter by status/jurisdiction/type | FREE |
tracker_update | Update priority, keywords, status, or close a watchlist item | FREE |
Policy Analyst
| Tool | Description | Cost |
|---|---|---|
analyst_digest | Read latest digest, generate a fresh one, or preview the next draft | FREE (read/preview) / EXPENSIVE (generate) |
digest_feedback | Submit feedback signals on findings: relevant, irrelevant, outdated, misclassified, correction, mute_topic, mute_source | FREE |
submit_finding | Submit 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
| Tool | Description | Cost |
|---|---|---|
steward_mine_signals | Mine recent team chat messages for coverage gaps and regulatory topics | MODERATE |
steward_query_signals | Retrieve signals from the most recent chat mining run | FREE |
steward_mine_vault_anomalies | Scan 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-audited | MODERATE |
Knowledge Vault
The Policy Librarian maintains a structured knowledge vault with:
| Category | Contains |
|---|---|
| Regulatory | Per-jurisdiction frameworks, proceedings, findings (append-only ledgers) |
| Reports | External research reports and industry studies |
| Positions | ev.energy company positions on policy topics |
| Case Studies | Utility 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:
- Run
librarian_indexto get a snapshot of all notes with metadata quality indicators - Identify notes with missing tags, wrong relevance, stale categories, or no source URL
- Use
librarian_updateto patch metadata without re-submitting the full note content - Use
librarian_deleteto 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:
| Signal | Use when... | Required field |
|---|---|---|
relevant | A finding was useful | finding_id (optional) |
irrelevant | A finding wasn't relevant | finding_id (optional) |
outdated | A finding is stale (deadline passed, info old) | finding_id |
misclassified | Wrong jurisdiction, topic, or type | finding_id + correction fields |
correction | Factual error (wrong date, detail) | finding_id + correction fields |
mute_topic | Stop showing a topic | topic |
mute_source | Stop showing a source | source |
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:
- Queued in the submission table (status: pending)
- Merged into the next digest generation automatically
- 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:
- Created in the tracking database (for nightly scan prioritization and digest reporting)
- 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.