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
@@ -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.