agent: teach Eleven how fast a deploy rolls out (#233)
Extend the "How it's deployed" section of Eleven's self-knowledge with the timing of a version swap: seconds per instance, zero-downtime (drain + router retry masks the socket handover, WebSockets reconnect), well under a minute to roll a fleet, ~a couple of minutes end-to-end including build + ship. Kept generic and secret-free to match the member-facing voice (no addresses, tokens, or instance names).
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 file changed,
+9
−1
agent/knowledge.mjs+9 −1
diff --git a/agent/knowledge.mjs b/agent/knowledge.mjs| index 0632724..01b1e8b 100644 |
| --- a/agent/knowledge.mjs |
| +++ b/agent/knowledge.mjs |
| @@ -662,7 +662,15 @@ described here generically (no server addresses or operator specifics): |
| readable. |
| - **Updates are versioned and zero-downtime.** You can canary a new build on one |
| instance while the rest stay on the old one, then roll the fleet one at a time |
| - with health checks and automatic rollback on failure. |
| + with health checks and automatic rollback on failure. **A swap takes seconds |
| + and drops nothing:** an instance restarts in place — the old process finishes |
| + any in-flight request while the router briefly holds new requests and re-points |
| + them at the new process the moment it's up, and live connections reconnect — so |
| + members see no interruption. Each instance is answering again within a second |
| + or two, and rolling a whole fleet of instances takes well under a minute. |
| + Shipping a brand-new build on top of that (compiling the one binary and copying |
| + it to the box) adds about a minute — so an update is live in a couple of |
| + minutes end to end. |
| - **Sibling services**, described generically: |
| - a **central push relay** that holds the single Apple push-signing key so |
| individual instances (yours or a third party's) can send iOS push *without* |