internal/

Package app is the assembly point: it reads configuration from the environment, picks the Postgres or SQLite repositories, builds the domain services and HTTP handlers, registers the routes behind the auth, token scope, rate limit and audit middleware, and owns the server's lifecycle.

Package audit records every mutating admin request against the control plane.

Package buildinfo carries the identity of the binary: which version, which commit it was built from, and when.

Package database opens and bounds the connection pool, and hides the two drivers behind one surface: PostgreSQL (github.com/jackc/pgx/v5, driven through database/sql by its stdlib shim — the production source of truth) and SQLite (modernc.org/sqlite, the local test stack).

Package flagsconfig owns feature flags: the flag definitions themselves and their per-environment values.

Package localization owns translation bundles: one JSON document per microservice, environment and locale, published to the LOCALIZATION KV bucket at key "{envID}.{microserviceID}.{locale}".

Package messaging is the distribution plane: the NATS connection, the JetStream KV buckets (FLAGS, SERVICESETTINGS, LOCALIZATION), the key layout consumers watch, the write-through publisher, and the reconciler.

Package obs is the instrumentation tier: ECS-shaped structured logging and a standard-library metrics registry rendered in Prometheus text format.

Package servicesettings owns per-service appsettings: one JSON tree per microservice and environment, published to the SERVICESETTINGS KV bucket at key "{envID}.{microserviceID}".

Package web holds the HTTP request and response plumbing shared by every domain handler: JSON encoding with a uniform error envelope, and decoding that is bounded before it is parsed.