Operations

Update model

Acquisition runs are scheduled outside web requests. Fetched artifacts, retrieval observations, parsed items, normalized truth, derived projections, and activation are distinct. A failed candidate leaves the prior active generation intact.

Freshness

Every provider boundary carries its own cutoff, record count, gap count, and freshness state. A stale optional enrichment is shown as stale; it does not freeze or erase unrelated current truth.

Recovery

Each release is immutable and retains an N−1 application rollback. Public cutover requires an application-consistent logical backup, an isolated restore, restart/reboot proof, and operator-confirmed automatic Lightsail snapshots.

This page never starts a refresh or reveals infrastructure identifiers, secrets, raw payloads, or private logs.