What shipped
Built a focused local MVP for Data Center Moratorium Watchboard. This build compounds the parent Data Center Docket Delta Watch package by adding a deterministic multi-jurisdiction packaging layer.
New runnable commands:
``bash python -m data_center_docket_watch watchboard --path /tmp/data-center-watchboard-demo --jurisdictions /tmp/data-center-watchboard-demo/jurisdictions python -m data_center_docket_watch validate-watchboard --path /tmp/data-center-watchboard-demo bash verify.sh ``
The watchboard command writes:
watchboard/regional-watchboard.mdwatchboard/jurisdiction-scorecard.csvwatchboard/jurisdiction-scorecard.jsonwatchboard/weekly-client-brief.mdwatchboard/source-gaps.mdwatchboard/prospect-shortlist.mdwatchboard/outreach-email.mdwatchboard/watchboard.json
Seeded demo jurisdiction folders are created by write_watchboard_demo_jurisdictions() for Illinois, Charlotte, and New York.
Architecture
- Kept the stack Python 3.11+ and standard library only.
- Copied the parent build into this build directory instead of modifying the immutable parent.
- Added
data_center_docket_watch/watchboard.pyfor loading, scoring, rendering, and validation. - Preserved
monthly-watch/delta-watch.jsonas the primary input contract from the parent build. - Added optional jurisdiction metadata through
jurisdiction-profile.jsonfor regional fields, source links, source gaps, prospects, and watchboard-specific signals. - Used a deterministic point model for urgency: moratorium/pause, public hearing or next action, incentive/tax signal, utility/water/environmental signals, monthly delta changes, source gaps, and buyer fit.
- Kept source gaps separate and visible instead of treating stale sources as confidence.
- Extended
verify.shto run inherited parent checks and the new watchboard flow.
Trimmed scope
- No web UI or dashboard.
- No hosted database, accounts, auth, billing, CRM, queue, or notifications.
- No live scraping of legislation, agenda, planning, utility, tax incentive, GIS, FERC, NCSL, meeting, or news systems.
- No browser automation.
- No email sending or public-comment submission.
- No legal, engineering, environmental, utility, lobbying, investment, or compliance advice.
- No Claude, Anthropic, OpenRouter, OpenAI API, or other provider/model calls.
Limitations
- The seeded data is compact demo material and must be refreshed against official sources before public use.
- The scorer is explainable but intentionally simple; it ranks review urgency, not legal or policy merit.
- The watchboard assumes each jurisdiction already has a compatible local
monthly-watch/delta-watch.json. - Source freshness is operator-supplied. The tool flags gaps but does not verify live current status.
- Prospects are local profile data, not CRM records.
Verification
bash verify.sh passes from the build root. It runs unit tests, recreates /tmp/data-center-docket-watch-demo, verifies the inherited packet, service-kit, and delta-watch workflows, recreates /tmp/data-center-watchboard-demo, runs watchboard, runs validate-watchboard, parses JSON outputs, and checks the required watchboard Markdown, CSV, and JSON artifacts.
Suggested next steps
- Run the watchboard on one real region after manually refreshing official source folders.
- Add an import helper that converts existing single-jurisdiction workspaces into
jurisdictions/<slug>/folders. - Add optional client/sender fields for
outreach-email.md. - Add a short operator notes field for why the urgency score changed week to week.
- Add regression fixtures for a low-urgency monitoring jurisdiction once real usage clarifies thresholds.