Wire M10.6b probe markers through sessions, evo-server, probe and client
Foundation / checks (checks) (push) Successful in 32m33s
Foundation / checks (client) (push) Successful in 12m28s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m0s
Foundation / checks (network) (push) Successful in 12m8s
Foundation / checks (postgres) (push) Successful in 40m38s
Foundation / checks (tsan) (push) Successful in 8m4s
Foundation / postgres-tools (push) Successful in 1m36s
Foundation / image (push) Successful in 2m33s
Foundation / server-image (push) Successful in 3m53s

EXPERIMENT (ADR-0094). RegionSessions owns the probe markers: admitted
intentions schedule them, each poll advances them to the simulated tick, and
snapshots carry them. evo-server sets the motion area from the region's
habitat sites; the probe prints its own marker.

The engineering client predicts its marker with the adaptive input lead,
rebases on each snapshot, resends a lost or refused intention, smooths
corrections, draws markers and follows its own with camera and interest.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-06 16:07:34 -04:00
co-authored by Claude Opus 5.5
parent ab7e26c02e
commit 96237ca10a
17 changed files with 334 additions and 27 deletions
+2 -1
View File
@@ -530,7 +530,8 @@ probe) with process evidence done; 10.5c engineering client switched to M10 sess
(snapshot views, camera interest, grant bundles, msquic.dll in the Windows package) done.
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 and 10.6c impaired traces follow.
predictor done; 10.6b wiring (sessions, evo-server, probe, GUI marker) done; 10.6c impaired
traces follow.
10.6-10.9 planned.
**Entry:** M9 client/session evidence and M7/M8 dev/stage durability. Read
+3 -1
View File
@@ -55,7 +55,9 @@ is a maintainer step. M10.6a (ADR-0094) adds the probe-motion experiment: one
non-biological marker per session moved by intentions with a shared integer rule, session
protocol v3 marker records (v2, deployed, is frozen and refused), and the client predictor
(bounded replay from the authoritative marker, corrections, smoothing, adaptive input lead).
Next: 10.6b wiring into sessions, evo-server, the probe and the GUI.
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.
## Previous gate - 2026-10-02
@@ -66,3 +66,33 @@ rules. Session protocol v2 was deployed to evolution-dev on 2026-10-06 and is fr
client resends after 10.6b's rules).
- Markers add at most 32 x 78 bytes per snapshot; their state is not durable and not part of
any checkpoint or simulation version.
## M10.6b wiring (2026-10-06)
- **RegionSessions** owns `ProbeMarkers`. Once the host calls `set_motion_area`:
- every established session gets a marker (also those open at that moment);
- an admitted intention schedules its marker;
- each poll advances markers to the simulated tick (while ready) before admitting;
- close and loss remove the marker;
- a new epoch clears all markers;
- `replicate` adds the markers and area to every source.
- **evo-server** sets the area with the default interest: the bounding cells of the
region's habitat sites in that slice, spawning at the centre of the first site. It prints
`m10 motion area`.
- **Probe:** one `marker TICK X Y APPLIED` line per snapshot holding its own marker.
- **Engineering client:**
- inputs are scheduled with the adaptive lead and recorded with the predictor;
- each snapshot's own marker rebases the prediction;
- a refusal removes the input, and `outside_window` raises the lead;
- an intention is sent again when the authority holds another vector and nothing is in
flight (after a loss or refusal);
- the predicted marker is presented at server tick + lead, with corrections smoothed.
While following, the camera and the interest follow the predicted own marker, until the
user pans or zooms. Markers are drawn as squares: own amber, others blue. The Session
panel shows the marker position, pending inputs, lead, corrections, maximum error and
snaps. There is no sub-tick interpolation: the marker steps at 20 Hz.
- Evidence:
- `client-remote-session`: the marker at the spawn, followed by camera and interest; an
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.
+36
View File
@@ -4526,3 +4526,39 @@ Not done:
- impaired traces (10.6c).
Deployed v2 servers refuse v3 clients until redeployed.
## 2026-10-06 — M10.6b probe-marker wiring (ADR-0094)
Implemented:
- `RegionSessions` markers (`set_motion_area`, schedule on admission, advance per poll,
close and loss, clear on a new epoch, markers in every snapshot source);
- the evo-server motion area (the habitat sites' bounding cells, `m10 motion area`);
- the probe's `marker` lines;
- the engineering client's prediction, adaptive lead, resend after loss or refusal,
smoothing, marker drawing, the follow camera and interest, and Session panel rows.
Evidence:
- `client-remote-session`: the marker at its spawn, followed by camera and interest; an
intention moves the predicted marker +x, and the authority confirms it with zero maximum
error and no pending inputs. Passed 3 times in a row.
- The real-process test (`region_m10_session_tests`): the probe's own marker moved +x with
its intention applied, and evo-server printed its motion area. The snapshot report is
now 8,966 bytes in 40 ticks, including the marker records.
Executed:
- **Linux GCC 14:**
- preset `client-network`: CTest 14/14;
- preset `quic`: 4/4;
- `postgres-check.sh` with QUIC: 20 suites.
- **Linux Clang 19:** build, plus clang-tidy 19 on the client app, the remote test,
RegionSessions, the probe and probe_motion.
- **Windows MSVC 19.44** (fresh binaries; built while the formatting pass ran, which
changed whitespace only):
- preset `quic`: 4/4;
- preset `client-network`: 12/12.
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.
+7 -4
View File
@@ -31,9 +31,12 @@ evo-client --connect void.aeternalisgames.com:7400 --server-name NAME --ca dev-c
- The view follows the region's default view until you pan or zoom; then the 15 x 15
cells around the camera centre are replicated (radius 7).
- W A S D send movement intentions; the Session panel lists each as sent, admitted,
rejected, simulated (final; intentions are never durable) or unknown.
- W A S D send movement intentions. They move your probe marker (amber square; others
are blue), an engineering experiment, not an organism (ADR-0094). It is predicted
locally and corrected by the server; the camera follows it until you pan or zoom.
The Session panel lists each intention as sent, admitted, rejected, simulated (final;
intentions are never durable) or unknown, plus the prediction figures.
- Each reconnect uses the next grant. A second client with a bundle for the same account
takes the session over; the first stops (do not share bundles).
- A server still on session protocol v1 refuses the client (`unsupported_version`):
deploy the v2 server first.
- A server on an older session protocol (v1, v2) refuses the client
(`unsupported_version`): deploy a v3 server first.