Track legislation, regulatory actions, and legal developments affecting prediction markets, crypto, and AI agents
If ${var} is set, narrow the search to that specific regulatory area.
Read memory/MEMORY.md for context on current positions and interests. Read the last 2 days of memory/logs/ to avoid repeating items.
Search for recent regulatory developments. Use WebSearch to find legislation, enforcement actions, regulatory guidance, and legal developments from the last 7 days across these domains:
Primary domains (always search):
Secondary domains (include if relevant hits):
Run these searches (use the current year dynamically — date +%Y):
WebSearch: "prediction market regulation OR legislation OR ban $(date +%Y)"
WebSearch: "CFTC prediction market OR Polymarket OR Kalshi $(date +%Y)"
WebSearch: "crypto regulation OR legislation OR SEC enforcement $(date +%Y)"
WebSearch: "stablecoin bill OR regulation $(date +%Y)"
WebSearch: "AI agent regulation OR autonomous agent legislation $(date +%Y)"
If ${var} is set, replace the above with 2-3 targeted searches for that specific topic.
Filter and deduplicate. From all results:
Rank by impact. Score each item on:
Enrich top items. For the top 3-5 items:
Format and send via ./notify (keep under 4000 chars):
*Reg Monitor — ${today}*
*HIGH PRIORITY*
- [Bill/Action name](url) — jurisdiction
what changed. who's affected. timeline.
prediction market angle: [if applicable]
*NOTABLE*
- [Bill/Action name](url) — jurisdiction
one-line summary. stage: [introduced/committee/passed/enacted]
*WATCH LIST*
- brief mention of developing stories not yet actionable
${count} regulatory developments tracked
Log to memory/logs/${today}.md. Record which items were included and their current stage.
If nothing found, log "REG_MONITOR_OK" and end.
Include:
Exclude:
The sandbox may block outbound curl. Use WebFetch as a fallback for any URL fetch. For auth-required APIs, use the pre-fetch/post-process pattern (see CLAUDE.md).
No environment variables required — uses WebSearch and WebFetch.