# Arlington deployment and verification

Verified on November 17, 2026 in America/Chicago.

- The existing `parker-crime-api.service` restarted at 00:12:43 CST under its original Caddy route. The service drop-in enables Arlington snapshots on a 15-minute minimum interval and Parker-area collection daily.
- The automated startup cycle stored **20 Arlington Police dispatch calls** and reported the newest source call at **November 16, 23:05:57 CST**. It stored **150 additional Parker-area records**, including one county alert. At verification the database contained **404 incidents**, with **384 in Parker County** and **20 in Arlington/Tarrant County**.
- Weatherford's collector parsed **149** records from its current release index and reached **November 15, 15:03 CST**. Some release entries lack a recognized incident time. Source health reports partial collection. Parker County Alert Center was reachable, while NOAA returned an empty active-alert snapshot.
- A read-only SQLite comparison against the pre-change backup found **zero changed or missing rows** in all three 234-row incident, normalized-event, and raw-evidence tables. SQLite `quick_check` returned `ok`.
- The original API contract script and 12 added civic tests passed under Python 3.11. The independent router suite passed under its service's Python 3.10 runtime. The full repository discovery under Python 3.11 could not import the unrelated router test because its `_cffi_backend` was unavailable.
- A live StatePlane point transformed independently with PROJ agreed with Arlington's WGS84 response within about one meter. Public positions use the coarser documented 0.01-degree resolution.
- Headless Chromium verified all three scopes against the public URL, with incident labels, source coverage, report text, and scoped exports. Public HTML, JavaScript and CSS matched the deployed bytes. Incident JSON, GeoJSON, CSV, summary, sources, source health, aircraft, daily reports and raw signals returned HTTP 200. The public WebSocket returned its expected hello. The tested public responses omitted private case identifiers and residence information.
- Arlington Fire remains archive-only or manual. Arlington scanner transcription has no verified authorized capture. Initial collection and the scheduling configuration were verified during rollout.

The crime directory is outside the GitHub Pages managed manifest. Deployment used its existing Caddy-served workspace paths. An early draft briefly occupied the live static path during editing. The original assets were restored, staging checks passed, and the final assets were published at 00:13:26 CST. The installed random worktree's Git metadata was unavailable to Git discovery, so these are local source changes with a deployed service and no Git commit.

The verified pre-change database and files are in `/srv/sol/archives/civic-expansion-2026-11-16/original/`. For a rollback, restore the three static files and API from that backup, remove the collector drop-in, reload systemd, and restart the service. The additive data can be retained. A database backup kept on the archive mount should be copied to a local filesystem before opening it in SQLite WAL mode.

[Public dashboard](https://sol.system42.one/crime/index.html) · [Public source diagnostics](https://sol.system42.one/api/crime/sources/health)
