central/README.md

# Central

Central is the data hub spine for the Echo6 infrastructure. Adapters normalize upstream sources into a canonical event shape, publish CloudEvents to NATS/JetStream, and archive to TimescaleDB for historical query. Single-LXC deployment.

## Status

**Operational** (v0.14.6) — deployed on utility CT 104 (`central.echo6.mesh`).

~22 adapters live across traffic, wildfire, weather, space-weather, hydrology, earthquakes, avalanche, disasters, and satellite. CloudEvents published to NATS/JetStream, archived to TimescaleDB/PostGIS. FastAPI + HTMX GUI/API on :8000.

Three systemd units on a single LXC:
- `central-supervisor` — adapter lifecycle manager
- `central-archive` — NATS consumer persisting events to TimescaleDB
- `central-gui` — FastAPI + HTMX web interface / API (:8000)

## Architecture

- Python 3.12 (uv-managed)
- NATS + JetStream for live event bus
- TimescaleDB + PostGIS for archive and geospatial query
- One supervisor process managing adapter lifecycle
- One archive consumer process persisting events to TimescaleDB
- Both processes systemd-managed

## Testing

See [docs/test-database.md](docs/test-database.md) for test database setup.

## License

MIT. See LICENSE.
scaffold: initial repository structure 2026-05-15 19:16:24 +00:00			`# Central`

docs: correct stale README — central is live in production (v0.14.5), not scaffold 2026-06-18 21:09:53 +00:00			`Central is the data hub spine for the Echo6 infrastructure. Adapters normalize upstream sources into a canonical event shape, publish CloudEvents to NATS/JetStream, and archive to TimescaleDB for historical query. Single-LXC deployment.`
scaffold: initial repository structure 2026-05-15 19:16:24 +00:00
			`## Status`

v0.14.6: commit orphaned migration 036 + fix stale README/version metadata (#112) Migration 036 (avalanche_org adapter row) was code-shipped in v0.10.10 (PR #98) but the SQL file was never committed to the repo. It has been applied in production since 2026-06-18; this commit adds the file so clean rebuilds can reach the same schema state. Also bumps pyproject.toml version from the stale 0.3.0 to 0.14.6 to match the deployed tag, and updates the README Status section to reflect current reality (~22 adapters, three systemd units, operational). Co-authored-by: Matt Johnson <mj@k7zvx.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> 2026-06-28 14:13:40 -06:00			Operational (v0.14.6) — deployed on utility CT 104 (`central.echo6.mesh`).
docs: correct stale README — central is live in production (v0.14.5), not scaffold 2026-06-18 21:09:53 +00:00
v0.14.6: commit orphaned migration 036 + fix stale README/version metadata (#112) Migration 036 (avalanche_org adapter row) was code-shipped in v0.10.10 (PR #98) but the SQL file was never committed to the repo. It has been applied in production since 2026-06-18; this commit adds the file so clean rebuilds can reach the same schema state. Also bumps pyproject.toml version from the stale 0.3.0 to 0.14.6 to match the deployed tag, and updates the README Status section to reflect current reality (~22 adapters, three systemd units, operational). Co-authored-by: Matt Johnson <mj@k7zvx.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> 2026-06-28 14:13:40 -06:00			`~22 adapters live across traffic, wildfire, weather, space-weather, hydrology, earthquakes, avalanche, disasters, and satellite. CloudEvents published to NATS/JetStream, archived to TimescaleDB/PostGIS. FastAPI + HTMX GUI/API on :8000.`
docs: correct stale README — central is live in production (v0.14.5), not scaffold 2026-06-18 21:09:53 +00:00
v0.14.6: commit orphaned migration 036 + fix stale README/version metadata (#112) Migration 036 (avalanche_org adapter row) was code-shipped in v0.10.10 (PR #98) but the SQL file was never committed to the repo. It has been applied in production since 2026-06-18; this commit adds the file so clean rebuilds can reach the same schema state. Also bumps pyproject.toml version from the stale 0.3.0 to 0.14.6 to match the deployed tag, and updates the README Status section to reflect current reality (~22 adapters, three systemd units, operational). Co-authored-by: Matt Johnson <mj@k7zvx.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> 2026-06-28 14:13:40 -06:00			`Three systemd units on a single LXC:`
docs: correct stale README — central is live in production (v0.14.5), not scaffold 2026-06-18 21:09:53 +00:00			- `central-supervisor` — adapter lifecycle manager
			- `central-archive` — NATS consumer persisting events to TimescaleDB
			- `central-gui` — FastAPI + HTMX web interface / API (:8000)
scaffold: initial repository structure 2026-05-15 19:16:24 +00:00
			`## Architecture`

			`- Python 3.12 (uv-managed)`
			`- NATS + JetStream for live event bus`
			`- TimescaleDB + PostGIS for archive and geospatial query`
			`- One supervisor process managing adapter lifecycle`
			`- One archive consumer process persisting events to TimescaleDB`
			`- Both processes systemd-managed`

docs: add test database setup, restore geom to test fixture - Add docs/test-database.md with one-time setup, DSN convention, reset instructions, and explanation of why PostGIS is not in migrations - Update docs/migrations.md with "Extensions are not in migrations" section explaining superuser requirement - Restore geom GEOMETRY(Geometry, 4326) column to test fixture now that central_test has PostGIS installed - Add CREATE EXTENSION IF NOT EXISTS postgis to test fixture for self-bootstrap (central_test is superuser) - Add Testing section to README.md pointing to docs/test-database.md Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> 2026-05-17 18:26:48 +00:00			`## Testing`

			`See [docs/test-database.md](docs/test-database.md) for test database setup.`

scaffold: initial repository structure 2026-05-15 19:16:24 +00:00			`## License`

			`MIT. See LICENSE.`