SDK Client Read-Path Lifecycle

SDK Client Read-Path Lifecycle A lifecycle diagram generated by Archify. 01 / Read path 02 / Recovery 03 / Opt-in and terminal Cold · constructed · Read path · no I/O yet 01 Cold constructed no I/O yet Refreshing · single-flight read · Read path · If-None-Match 02 Refreshing single-flight read If-None-Match Warm · snapshot + ETag · Read path · atomic swap 03 Warm snapshot + ETag atomic swap Serving · local decision · Read path · sub-millisecond 04 Serving local decision sub-millisecond Steady · toggles land next check · Read path · in sync 05 Steady toggles land next check in sync Backoff · failure_backoff = 5s · Recovery · recoverable Backoff failure_backoff = 5s recoverable Rejected · AuthorizationError · Opt-in and terminal · terminal Rejected AuthorizationError terminal transport error window elapsed key rejected Legend start active state terminal success failure / exit

Reads as it evaluates

  • • Construction performs no I/O, so the client can be built at import time without a network call.
  • • Every check sends the current ETag as If-None-Match, which is what makes a dashboard toggle visible on the very next check.

Failure is absorbed on purpose

  • • A flag check sits inside someone else's request, so a read failure degrades to the last good snapshot instead of raising.
  • • A failed read opens a failure_backoff window, so an unreachable API costs one timeout per window rather than one per check.