Files
dingoandClaude Opus 5.5 a7a3d12283
Foundation / checks (deploy) (push) Successful in 3m29s
Foundation / checks (ecs) (push) Successful in 2m0s
Foundation / checks (client) (push) Successful in 12m51s
Foundation / checks (network) (push) Successful in 13m0s
Foundation / checks (tsan) (push) Successful in 7m50s
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 32m4s
Foundation / checks (postgres) (push) Canceled after 19m13s
Wire M10.8c-1 region handoff: protocol v4, durable probes, crossing, ghosts
ADR-0096. Session protocol v4 (v3 is deployed and frozen) adds HandoffOffer,
SessionRedirect, close reasons handed_off and moved, and ghost marker records.
Sessions use the durable probe record: logins open it where it was saved
(redirected when it lives elsewhere), and session ends save it. A marker
crossing into a neighbour's area is frozen, prepared, its control released
and a signed ticket offered; uncommitted transfers are aborted after the
ticket's lifetime. The destination shows arriving probes as ghosts (schema
v13 incoming_probe_transfers) and opens the marker where it crossed.

Refreshes the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-06 21:24:42 -04:00

29 lines
1.7 KiB
Markdown

# M10 session protocol, version 3
Superseded by [version 4](session-v4.md) (ADR-0096): v3 was deployed to evolution-dev and is
frozen; v4 servers and clients refuse it.
Version 3 is [version 2](session-v2.md) 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).