Gateway window: performance
The Admin performance projection: the gateway aggregates only milestones its live voice path accepted, in order on one connection (an accepted final, the committed turn, the first admitted brain token and on), never trace files or browser timing.
Living doc, checked against the code 2026-11-14
The Gateway owns the Admin performance projection. It aggregates only milestones that the live voice path accepts. It does not parse trace files, ingest arbitrary JSON, or accept timing from a browser.
Correlated boundaries
A sample counts only when one live connection sees, in order:
- an accepted final STT frame;
- the committed Gateway turn it produced;
- that turn’s first admitted Brain text token;
- the first TTS request for that turn and output generation;
- the first PCM chunk for that request, sent to the Frontend Skin;
- the playback observation accepted for the same turn.
The five exported stage names name those boundaries. Session, request, playback and output-generation ids stay on the connection; the latency samples hold no id.
Truth and bounds
- The projection class is always
unknown. Vulpine does not infer cold or warm from turn position or process age. - Samples belong to one observation generation. It advances only when accepted, incomplete or rejected evidence changes.
- Each stage keeps the latest 256 accepted samples. Lifetime accepted, incomplete and rejected turn counts sit outside that window.
- Percentiles use nearest-rank over the window, computed from a snapshot outside the mutation lock.
- Missing, duplicate, out-of-order or mismatched milestones produce no sample. Stale TTS output cannot complete a newer request.
- Reading the projection never changes it.
- The projection holds no transcript text, model output, audio, private paths or secrets.
The same read also carries, each absent until it has data: the brain’s token use and cost, the desktop app’s memory
footprint, each turn leg against its budget (docs/contracts/turn-budget.v1.toml), today’s utterance records per
device (while [utterance] rows is on), the last eight accepted turns’ stage spans keyed by turn id, and accepted
turns per hour over seven days (crates/protocol/src/admin_turn_tracks.rs).
The Gateway window and local clients read it with the typed GetPerformance/Performance protocol-v6 contract over
the authenticated, owner-only Admin socket.