Brief P10: separate limit for waiting on a slot or a model load

Approved 2026-09-17. Evidence is in docs/decisions.md. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-17 00:38:32 -07:00
parent 27b7ff45ee
commit adab43add1
2 changed files with 5 additions and 2 deletions
@@ -113,7 +113,10 @@ ordinary outbound networking can reach the whole tailnet and the internet as the
   declared tool.
 7. **Liveness, not deadlines.** Streaming always, with `return_progress: true` so that prompt
   processing produces events. The timeout is "no bytes for N seconds", never a total-request
-   deadline. Progress events count as bytes.
+   deadline. Progress events count as bytes. Before the first byte, a request may be queued behind
+   another client on its slot or waiting for the router to load the model. A separate, longer
+   limit covers that wait, and the liveness timer starts at the first byte. M2 measures what the
+   stream sends while a request is queued.
 8. **Runaway control.** Per-turn thinking-token cap, per-turn tool-iteration cap, detection of
   repeated identical tool calls. `loopd` enforces the thinking cap: it counts streamed reasoning
   tokens and ends the block with the server's `reasoning_control` mechanism