Skip to content

ADR-0017: Connection health and sync health are separate

  • Status: Accepted
  • Date: 2026-09-10

Context

Real systems have shown healthy sockets with frozen per-environment subscriptions.

Decision

A connected client can still have stale/dead subscriptions, so Forge tracks transport and freshness independently.

Consequences

UI can represent CONNECTED + STALE and reconcile authoritative state.

Change rule

If implementation evidence proves this wrong, update the canonical architecture/product document first and then supersede/amend this ADR. The ADR is not allowed to keep current docs stale.

Forge is local-first. The docs are part of the product engineering system.