Documentation
DocumentationRelease notes & v1 boundary
DOCS / UWA V1 RELEASE CONTRACT SELF-HOSTED GATEWAY

Release notes & v1 boundary

What UWA v1 ships in source and what requires operator acceptance before production launch.

ONE GATEWAYCoordinates → eligible provider → canonical responseWhy UWA
On this page 3 sections

#UWA v1 core vs experimental scope

UWA v1 freezes the default production router (APP_RELEASE_PROFILE=lean_v1) around current weather, hourly and sampled daily forecasts, geocoding, opt-in astronomy, and the unified GET /v1/datasets multi-category endpoint. Extended products (air quality, historical ERA5 reanalysis, marine wave forecasts, and US NWS alerts) plus regional/dev adapters (Bright Sky, US NWS, public Nominatim) remain in the repository under APP_RELEASE_PROFILE=full_experimental for development and testing.

#Hardening highlights in v1

  • Multi-category orchestration: GET /v1/datasets with upfront scope checks, scoped query parameters (forecast.points=24), and 207 Multi-Status partial-failure responses.
  • Data & cache integrity: 25–50 km coordinate drift ceilings, 2-hour observation freshness limit, portable IANA timezone checks, and integrity_version: 1 cache re-validation.
  • Security & operations: All 8 scopes in uapctl create-key, offline uapctl doctor --json, retryable 503 AUTH_BACKEND_UNAVAILABLE on DB outage, direct-dial SSRF protection, and loopback Bearer-authenticated /metrics.

#Operator acceptance gates before public launch

Before declaring a live production launch, complete end-to-end acceptance on target infrastructure: genuine PostgreSQL 16 migrations and key lifecycle, two-replica Redis 7 Lua quota enforcement, authorized live provider smoke tests, reviewed country polygons, and native Linux systemd / Windows SCM service verification.

Canonical contracts: docs/openapi.yaml (lean_v1) and docs/openapi.experimental.yaml · Verify against your build before production use.

Search local documentation. No external requests.

↑↓ to move · Enter to openESC to close