Add M10.6c probe-marker prediction traces and close M10.6
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m54s
Foundation / checks (postgres) (push) Canceled after 0s
Foundation / checks (tsan) (push) Canceled after 0s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 12m33s
Foundation / checks (network) (push) Canceled after 10m23s
Foundation / checks (client) (push) Canceled after 12m33s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m54s
Foundation / checks (postgres) (push) Canceled after 0s
Foundation / checks (tsan) (push) Canceled after 0s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 12m33s
Foundation / checks (network) (push) Canceled after 10m23s
Foundation / checks (client) (push) Canceled after 12m33s
evo-motion-trace drives the engineering client's own session code through the owned impairment relay against a real-time 50 ms loopback region: exact without loss, 94-99 % exact at 60-200 ms RTT with 2-5 % loss, every profile converging after stopping, restart resync about 2-3 s (docs/networking/M10_PREDICTION_TRACES.md). The CTest motion-trace-smoke checks convergence, bounds and a majority of exact predictions. The relay lets a new sender take over after the current client has been silent for 1 s (reconnects); the client counts refusal receipts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
+1
-2
@@ -531,8 +531,7 @@ probe) with process evidence done; 10.5c engineering client switched to M10 sess
|
||||
10.6 split (ADR-0094, EXPERIMENT probe marker, not an organism movement rule): 10.6a shared
|
||||
probe-motion-v1 rule, server markers, session protocol v3 marker records and the client
|
||||
predictor done; 10.6b wiring (sessions, evo-server, probe, GUI marker) done; 10.6c impaired
|
||||
traces follow.
|
||||
10.6-10.9 planned.
|
||||
traces done (networking/M10_PREDICTION_TRACES.md). 10.7-10.9 planned.
|
||||
|
||||
**Entry:** M9 client/session evidence and M7/M8 dev/stage durability. Read
|
||||
NETWORK_ARCHITECTURE, PERSISTENCE_ARCHITECTURE and ADR-0017. The M9 transport is
|
||||
|
||||
+4
-1
@@ -57,7 +57,10 @@ protocol v3 marker records (v2, deployed, is frozen and refused), and the client
|
||||
(bounded replay from the authoritative marker, corrections, smoothing, adaptive input lead).
|
||||
M10.6b wires it: evo-server gives every session a marker in the habitat area, the probe
|
||||
prints it, and the engineering client predicts and draws it (WASD), following it with
|
||||
camera and interest. Next: 10.6c impaired traces and the correction report.
|
||||
camera and interest. M10.6c traces it through the impairment relay: exact without loss,
|
||||
94-99 % exact at 60-200 ms RTT with 2-5 % loss, convergence after stopping and a restart
|
||||
resync of about 2-3 s (networking/M10_PREDICTION_TRACES.md). M10.6 is complete. Next: M10.7
|
||||
interpolation and session loss.
|
||||
|
||||
## Previous gate - 2026-10-02
|
||||
|
||||
|
||||
@@ -96,3 +96,22 @@ rules. Session protocol v2 was deployed to evolution-dev on 2026-10-06 and is fr
|
||||
intention moves the predicted marker and the authority confirms it with zero error.
|
||||
- The real-process test: the probe's marker moved +x with its intention applied, and
|
||||
evo-server reported the motion area.
|
||||
|
||||
## M10.6c traces and close (2026-10-06)
|
||||
- `evo-motion-trace` drives the client's own session code through the impairment relay
|
||||
against a real-time 50 ms loopback region; the figures are in
|
||||
[M10_PREDICTION_TRACES](../networking/M10_PREDICTION_TRACES.md).
|
||||
- Prediction is exact without loss.
|
||||
- With 2-5 % loss and 60-200 ms RTT, 94-99 % of samples are exact. Errors stay within the
|
||||
motion of the lost or late inputs (at most about 1.4 m) and are corrected by the resend.
|
||||
- All profiles converge on the authority when stopped.
|
||||
- A restart resyncs in about 2-3 s (the reconnect pause).
|
||||
- The CTest `motion-trace-smoke` (labels client, quic-session) runs 6 s of rtt60-loss2 plus
|
||||
a restart. It fails unless both converge, the input list stays within its bound and most
|
||||
predictions are exact.
|
||||
- The owned UDP relay now lets a new sender take over once the current client has been
|
||||
silent for 1 s, so a reconnecting client (new source port) can be traced. Concurrent
|
||||
senders are still dropped.
|
||||
- The client now counts refusal receipts (`refused`) separately from inputs the predictor
|
||||
removed; the unused `PredictionStats::refused_inputs` field is gone.
|
||||
- M10.6 is complete. Sub-tick presentation and remote-marker interpolation belong to 10.7.
|
||||
|
||||
@@ -4562,3 +4562,44 @@ clang-format 19 was applied to the changed files.
|
||||
Not done:
|
||||
- impaired traces (10.6c);
|
||||
- a GUI run against evolution-dev, which needs a v3 server.
|
||||
|
||||
## 2026-10-06 — M10.6c prediction traces (ADR-0094)
|
||||
|
||||
Implemented:
|
||||
- `evo-motion-trace` (the client's own session code through the impairment relay against
|
||||
a real-time 50 ms loopback region);
|
||||
- the CTest `motion-trace-smoke`;
|
||||
- the relay takeover by a new sender after the current client has been silent for 1 s;
|
||||
- a refusal count in the client status, replacing the unused predictor field.
|
||||
|
||||
Figures are in docs/networking/M10_PREDICTION_TRACES.md. Linux, one run of each profile:
|
||||
- clean and lan: 100 % exact;
|
||||
- rtt60-loss2: 97.9 %;
|
||||
- rtt120-loss2: 99.3 %; restart resync 2,946 ms;
|
||||
- rtt200-loss5: 94.1 %; p99 500 mm, max 989.9 mm.
|
||||
|
||||
Every profile converged after stopping. Windows was similar, with a maximum of 1,399.8 mm
|
||||
at rtt200-loss5. The smoke profile passed 3 times in a row on Linux.
|
||||
|
||||
Found and fixed during development:
|
||||
- the relay ignored a reconnecting client (new source port), so restart resync timed out;
|
||||
- refusals were undercounted when an input had already been dropped;
|
||||
- a clang-tidy widening-cast finding.
|
||||
|
||||
Executed:
|
||||
- **Linux GCC 14**
|
||||
- preset `client-network`: CTest 15/15, including motion-trace-smoke and
|
||||
client-remote-session;
|
||||
- preset `quic`: 4/4, including quic-transport with the changed relay.
|
||||
- **Linux Clang 19:** clang-tidy 19 on the trace tool, client app, remote test, predictor
|
||||
and relay.
|
||||
- **Windows MSVC 19.44** (fresh binaries):
|
||||
- preset `quic`: 4/4;
|
||||
- preset `client-network`: 13/13, including motion-trace-smoke;
|
||||
- a full trace run.
|
||||
|
||||
The Postgres suite was not rerun: no server code changed since 10.6b.
|
||||
|
||||
Not done:
|
||||
- traces over the dev route (a v3 server must be deployed first);
|
||||
- many-client load (10.8).
|
||||
|
||||
@@ -0,0 +1,64 @@
|
||||
# M10.6c probe-marker prediction traces (2026-10-06)
|
||||
|
||||
Development reference for ADR-0094 (EXPERIMENT: a probe marker, not organism movement).
|
||||
Tool: `evo-motion-trace` (tools/network/motion_trace.cpp, preset `client-network`).
|
||||
|
||||
## Setup
|
||||
- The engineering client's own session code (`apps/evo-client/remote_session.hpp`: the
|
||||
predictor, adaptive lead, resend, smoothing).
|
||||
- A loopback region simulating at 50 ms in real time, with RegionSessions and probe
|
||||
markers.
|
||||
- The owned UDP impairment relay with the same impairment in both directions (seed 0xE6).
|
||||
- Script: a new direction every 0.4-1.1 s from 9 choices (including stop) for 20 s. Then
|
||||
stop and require convergence: nothing in flight and the presented (smoothed) marker
|
||||
exactly on the authoritative position.
|
||||
- The `rtt120-loss2` profile then advances the epoch: the session reconnects with its next
|
||||
grant after the client's 2 s pause, and resync is measured until the prediction matches
|
||||
the respawned marker.
|
||||
- Error: one sample per authoritative snapshot of the own marker. It is the distance
|
||||
between what the client predicted for that tick and what the authority reported.
|
||||
Corrections are the jumps that rebasing made to the presented position.
|
||||
|
||||
## Results (Linux GCC 14 release, WSL2, one run)
|
||||
|
||||
| Profile | RTT ms | Jitter ms | Loss | Samples | Exact | p95 mm | p99 mm | max mm | Corrections | Refused | Dropped | Resends | Final lead | Max pending | Converged |
|
||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||
| clean | 0 | 0 | 0 % | 400 | 100 % | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 1 | yes |
|
||||
| lan | 20 | 2 | 0 % | 400 | 100 % | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 1 | yes |
|
||||
| rtt60-loss2 | 60 | 5 | 2 % | 378 | 97.9 % | 0 | 369.5 | 799.9 | 3 | 2 | 3 | 3 | 4 | 1 | yes |
|
||||
| rtt120-loss2 | 120 | 10 | 2 % | 279 | 99.3 % | 0 | 0 | 200.0 | 1 | 2 | 2 | 2 | 2 | 1 | yes |
|
||||
| rtt200-loss5 | 200 | 20 | 5 % | 358 | 94.1 % | 100.0 | 500.0 | 989.9 | 6 | 5 | 7 | 6 | 7 | 2 | yes |
|
||||
|
||||
Windows MSVC 19.44 (same tool, one run):
|
||||
- clean and lan: 100 % exact.
|
||||
- rtt60-loss2: 99.5 % exact, max 200 mm.
|
||||
- rtt120-loss2: 98.6 %, max 500 mm; resync 2,498 ms.
|
||||
- rtt200-loss5: 94.3 %, p95 100 mm, p99 600 mm, max 1,399.8 mm, lead 7, max 2 pending.
|
||||
- All profiles converged.
|
||||
|
||||
Restart (rtt120-loss2): resync took 2,946 ms, almost all of it the client's reconnect pause
|
||||
(2 s) and login. The smoke profile (6 s of rtt60-loss2 plus a restart) passed three runs in a
|
||||
row: 95.9-98.3 % exact, resync 2,241-2,248 ms.
|
||||
|
||||
## Reading
|
||||
- Without loss every prediction is exact: the rule is shared and integer-exact, and inputs
|
||||
are scheduled far enough ahead.
|
||||
- Errors come from inputs that did not take effect: lost datagrams (dropped) or arrivals
|
||||
after their tick (refused, which also raises the lead). Each costs at most the motion
|
||||
until the resend lands: 100 mm per tick, so up to about 1.4 m at 200 ms RTT with 5 % loss
|
||||
(two losses in a row). Smoothing hid
|
||||
every correction (no snaps above 2 m).
|
||||
- The input list stayed tiny (at most 2 pending), far below its bound of 32. Replay depth
|
||||
equals the lead plus the snapshot age.
|
||||
- The lead adapts upward on refusals (7 at 200 ms RTT) and back down when receipts show
|
||||
spare ticks. At 120 ms it ended at 2 after recovering; occasional refusals stay bounded
|
||||
by the resend rule.
|
||||
- Figures are single runs on one machine with wall-clock pacing: indicative, not
|
||||
acceptance thresholds. The CTest `motion-trace-smoke` checks only convergence,
|
||||
boundedness and a majority of exact predictions.
|
||||
|
||||
## Not measured
|
||||
- Remote-entity interpolation (10.7).
|
||||
- Many clients at once (10.8).
|
||||
- Real links (dev route); deferred until a v3 server is deployed.
|
||||
- Sub-tick presentation: the marker steps at 20 Hz.
|
||||
Reference in New Issue
Block a user