← Back to Daily Builds

Daily build note · June 3, 2026

Data Center Docket Watch

A local-first civic tracking kit for AI data center zoning, utility, tax incentive, and public-comment decisions.

Civic / Political Tracking Tools Build note published Public demo coming soon

What shipped

Data Center Docket Watch is a local-first Python CLI that creates a deterministic civic packet from docket-input.json, jurisdiction-profile.json, and optional notes.md.

Implemented commands:

  • python -m data_center_docket_watch init --path ./workspace
  • python -m data_center_docket_watch sample --path /tmp/data-center-docket-watch-demo --force
  • python -m data_center_docket_watch generate --path /tmp/data-center-docket-watch-demo
  • python -m data_center_docket_watch validate --path /tmp/data-center-docket-watch-demo

Generated artifacts:

  • docket-brief.md
  • hearing-calendar.json
  • ordinance-risk-map.md
  • public-comment-pack.md
  • utility-and-tax-questions.md
  • stakeholder-map.md
  • decision-receipts.md
  • docket-watch.json

Architecture

  • Reused the parent build's smallest stable pattern: standard-library Python package, CLI commands, seeded sample, deterministic renderers, validator, unit tests, and root verify.sh.
  • Rebuilt the domain model around civic dockets instead of copying MCP/tooling logic.
  • Kept source URLs as references only; the generator never fetches them.
  • Used field and keyword-based risk tagging so results are deterministic and inspectable.
  • Kept a stable docket-watch.json core for future dashboard, diff, or watch-service layers.

Trimmed scope

  • No web app or dashboard.
  • No live scraping of civic systems.
  • No API keys, OAuth, browser automation, or LLM calls.
  • No legal, engineering, environmental, utility, lobbying, or compliance advice.
  • No public-comment submission or outbound notifications.

Limitations

  • The seeded BL2026-1391 workspace is Nashville-like demo data, not a live official record.
  • Risk tags depend on provided local text and may miss issues not represented in the input.
  • Validation proves structure and required language, not the factual accuracy of the docket.
  • Calendar and decision receipts must be updated manually as official records change.

Suggested next steps

  • Add a second sample for another jurisdiction to test portability.
  • Add optional local CSV import for calendar events and decision receipts.
  • Add a diff command to compare packet revisions before and after meetings.
  • Add a manual source checklist for Legistar, planning agendas, utility boards, and incentive bodies.
  • Create a client handoff template for the $1,500 Data Center Docket Scan.