Remote generation created a practical question: what should the product become when the network disappears? The repository's answer was not to make the entire reflective experience unavailable. It preserved a deterministic local engine and made it part of the generation architecture.
Connectivity state can force local generation before a remote attempt. Qualifying remote failures can be classified, retried, and then routed to the same local engine. The interface tells the user when local mode is active rather than quietly presenting a simpler response as if it came from the remote model.
This choice supports the local-first character of the app. Timelines, messages, and memory remain on device, and a conversation can continue without remote inference. The tradeoff is visible: deterministic replies are more limited. The fallback protects continuity, not equivalence.
Tests cover offline routing, retry policy, local fallback, state notices, and the rule that failed or cancelled streaming must not leave partial assistant messages in persistence.
← Back to AlternateYou