Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m1s
Foundation / checks (network) (push) Successful in 12m13s
Foundation / checks (client) (push) Successful in 14m28s
Foundation / checks (tsan) (push) Successful in 7m56s
Foundation / checks (checks) (push) Successful in 32m49s
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 40m58s
EXPERIMENT (ADR-0094), not an organism movement rule: one non-biological marker per session, moved by admitted intentions with a shared integer rule (probe-motion-v1, 100 mm per tick, clamped to the area), held in region memory only. - ProbeMarkers: spawn, area, bounded per-marker schedule, catch-up bound - session protocol v3: marker records in snapshot chunks; the own marker is always sent with its applied sequence and area; v1 and v2 are refused - MotionPredictor (bounded replay from the authoritative marker, corrections, error samples), CorrectionSmoother and InputLead - tests: exact prediction with enough lead, refusal and lead adaptation, lost inputs, bounds, marker records through the codec Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.6 KiB
1.6 KiB
M10 session protocol, version 3
Version 3 is version 2 with two more snapshot record kinds for the M10.6
probe-motion experiment (ADR-0094). Message types, lengths and rules are those of v2. The
header version is 3. Versions 1 and 2 were deployed to evolution-dev and are frozen; both
are refused (unsupported_version). Once v3 is deployed it is frozen like them.
Snapshot records (in addition to v2 kinds 1-4)
| Kind | Body |
|---|---|
| 5 marker upsert | id u64, x, y (i64 um), z (i64 cell slice), move_x, move_y (i16), own u8 (0 or 1); when own = 1: applied_sequence u64, area min_x, min_y, max_x, max_y (i64 um) |
| 6 marker remove | id u64 |
- A marker is a non-biological engineering marker, one per session (ADR-0094). The receiving session's own marker has own = 1 and is sent whatever its interest, with the newest applied intention sequence and the inclusive area (min <= max) it moves in. A snapshot holds at most one own marker. Other sessions' markers have own = 0, no sequence or area, and pass the spatial filter (z equals the interest slice, cell within the square).
- id is nonzero; the vector's norm is at most 1000. A marker's z is not bound to slice_z.
Anything else is malformed and closes the session (
protocol). - The marker state is the state after the snapshot's tick: the client restores it, drops inputs with sequence <= applied_sequence or tick <= the snapshot tick, and replays the rest with probe-motion-v1 (position += vector x 100,000 / 1,000 um per tick per axis, clamped to the area; an intention for tick T sets the held vector from T's step on).