Ratify M10.1 timing and workload budgets with session traces
Foundation / checks (deploy) (push) Successful in 1m0s
Foundation / checks (ecs) (push) Successful in 3m34s
Foundation / checks (network) (push) Successful in 8m8s
Foundation / checks (client) (push) Successful in 14m49s
Foundation / checks (tsan) (push) Successful in 7m35s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (postgres) (push) Canceled after 16m18s
Foundation / checks (checks) (push) Canceled after 29m27s

ADR-0089 records the maintainer-ratified 50 ms tick, 1 s flush with final
outcomes p95 <= 1.5 s, responsiveness targets and reference hardware, plus
derived scheduling, sequence, identity, baseline, queue/byte/work budgets and the
exact/tolerant determinism contract (schemas/network/m10-budgets-v1.md). Adds
SessionClient traffic counters, `evo-dev-session trace` and a reproducible trace
script; development-reference results are in M10_TIMING_TRACES. Records that
genome v1 and metabolism rates are per tick, so the quantum fixes biology rates.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-03 12:29:58 -04:00
co-authored by Claude Opus 5.5
parent 6152d58fa6
commit 819137c1df
15 changed files with 557 additions and 12 deletions
+29
View File
@@ -3982,3 +3982,32 @@ selector, a port-less entry, and rendered route patches of the selector, VIP and
range; the reviewer's m98f-8a1e5ef-repro.py now exits 1 with default-deny and
session-port failures in platform/dev and platform/cluster. No cluster action. M9.8f
remains open.
## 2026-10-03 — M10.1 protocol timing and workload budgets (ADR-0089)
Maintainer ratified: 50 ms tick, 1 s flush with final outcomes p95 <= 1.5 s,
responsiveness LAN p95 <= 150 ms / 100 ms RTT p95 <= 250 ms, server budgets on one RKE2
worker and client budgets on the low-spec VM. Derived budgets and the exact/tolerant
determinism contract are in ADR-0089 and schemas/network/m10-budgets-v1.md.
Implemented: `SessionClient::traffic()` received-frame counters (additive API, checked
in network_session); `evo-dev-session trace` (continuous polling, nearest-rank
percentiles, CSV); `tools/network/session-trace.sh` (throwaway PostgreSQL, development-v1
region, evo-server with sessions and ops metrics, three loopback runs, cross-host pause).
Traces (development reference: Ryzen 7 9800X3D, 61.6 GB, Windows 11; WSL2 server):
committed-script run with Linux loopback at 250/100/1000 ms and Windows -> WSL2 at
250 ms: admission p50 0.9-1.4 ms, p99 <= 5.2 ms; durable p50 0.92-1.06 s, p95
1.37-1.41 s, max 1.46 s; outcome lead 9 ticks; view interval p50 50.1 ms, p99 <= 60 ms;
267-byte views, about 7.5 KB/s; tick debt max 0, server about 1 % CPU, 10.5 MB RSS. Two
earlier runs matched within about 1 ms. A 1 ms-sleep Windows client measured about
31 ms admission (Windows timer granularity); the trace now polls continuously.
Finding recorded in ADR-0089: genome v1 and metabolism rates are per tick, so the
quantum fixes biological rates; changing it needs a versioned rules migration (M11.1).
Executed checks: Windows MSVC network preset 1/1 (twice, after each change); Linux GCC 14
network tests and evo-dev-session build; Clang ASan/UBSan network tests; clang-tidy on
the session client, evo-dev-session and network_session tests; format check.
Not covered: emulated RTT/loss, multiple clients, the reference worker and low-spec VM,
movement/prediction; the targets are therefore not yet qualified (10.9).