Operations
How UseAgent ships, how it proves a release, and the invariants production runs on.
Operations in UseAgent are built around one principle: a release must prove itself before it ships, and roll back cleanly if it cannot.
Deployment lanes
The guarded release and the provider-connection bootstrap, both ending in the atomic frontend swap.
Verification
The test and parity arsenal, from isolated-database unit suites to real engine journeys.
Invariants
Single backend per database, write-only secrets, a restricted gateway role, and immutable-source releases.
Backups and restore
A daily encrypted snapshot with verify and restore lanes, and the off-host requirement.
The shape of a safe change
Type-check everything
bun run typecheck covers the frontend, backend, and shared packages, and
must pass before a change is done.
Verify in isolation
Suites run against a throwaway database so they never disturb a live one.
Certify a candidate
The guarded release runs fail-closed gates and per-engine parity canaries against a candidate before it can ship.
Roll back on any failure
Source, environment, Caddy configuration, and services all restore to the prior state if any preflight or parity journey fails.