Toggle Propagation: Dashboard to Next Read

Toggle Propagation: Dashboard to Next Read A sequence diagram generated by Archify. PATCH rollout 10% → 100% UPDATE state; version += 1 DEL snapshot key INSERT audit_logs · user 200 · ETag now version 8 is_enabled('new-checkout') GET /bootstrap · If-None-Match v7 SELECT environment → v8 GET snapshot · evicted SELECT flags + states + rules 200 · version 8 · new value The mutation The next read Dashboard · RolloutSlider · Sequence participant Dashboard RolloutSlider Flags API · PATCH /flags/{key}/env · Sequence participant Flags API PATCH /flags/{key}/env PostgreSQL · state + version · Sequence participant PostgreSQL state + version Redis · snapshot key · Sequence participant Redis snapshot key CatalystClient · long-lived · Sequence participant CatalystClient long-lived Application · next request · Sequence participant Application next request Legend request return async trace default message

One counter is the whole contract

  • • Environment.version is simultaneously the cache validation token and the weak ETag.
  • • bump_environment_versions increments the version and evicts the key inside the caller's transaction.
  • • The key was already gone, so a stale read is not merely unlikely, it is unreachable.

Ordering that is safe either way

  • • The Redis eviction happens before the database commit, and that ordering is deliberate.
  • • Evicting early is conservative: a reader may rebuild from old rows, never the reverse.
  • • The SDK's 304 short-circuit fires before the snapshot loads, so a toggle lands on the very next check.