Repository navigation
id(transport): transport designs #536
Description
What and why
Designs and research for how frames and journals move between nodes and clients: delta frames, replication, SSH as a frame transport, SSH/iroh tunnelling and multi-server topology. Ticked when the design or research package is committed and an implementation issue exists.
Items
Each box is done when the design (or research package) is committed and an implementation issue is linked here.
- D1-029 — F12.11 Delta and binary frames with resume tokens (L, design)
Screen patches as cell runs, optional binary encoding and compression, and resume tokens so a reconnecting client gets a patch; target: a typical redraw under 10% of the F11.9 full-frame size, plus a parity test.- Status: not started.
grep -rn 'resume_token\|delta' pkgs/id/src/world_session.rs pkgs/id/src/web/world_ws.rsfinds no frame-patch code; F11.9 baseline missing (D1-009). Overlaps the presentation-tier proposals in the uncommitted reports (see that section). - Source: .opencode/plans/phase-12-platform-flexibility.md:50; .opencode/plans/phase-12-platform-flexibility.md:22
- Prerequisites: id(world): F11.9 bytes-per-frame baseline table #542 — D1-009 F11.9 Bytes-per-frame baseline table
- Status: not started.
- D1-031 — F12.13 Journal replication to signed read replicas (XL, research package)
Read replicas follow a single-writer world journal over a signed stream, serve spectators and survive writer downtime; tampered streams are refused; the F11.12 format rules apply.- Status: not started. The
MirrorandDownloadworld commands (cli.rs:1388 enum) copy modules and records, but there is no journal-follow stream:grep -rn 'replica' pkgs/id/src/world*.rsfinds nothing. - Source: .opencode/plans/phase-12-platform-flexibility.md:55
- Prerequisites: Define rollback compatibility for world profile journal entries #227 — D1-012 F11.12 Journal format version header, check and backup commands, id: Phase 12 designs to run through the research workflow #534 (tracking issue) — D1-024 F12.6 Structured audit log with OpenTelemetry export
- Status: not started. The
- D1-050 — SSH as a transport for the frame protocol (
id world join --via ssh) (L, research package)
Run the ClientFrame/ServerFrame JSON protocol over an SSH exec channel for constrained networks and jump hosts. Today SSH is only a human presentation adapter, and the CLI speaks frames over iroh QUIC.- Status: delivered. Implemented by id: Phase 13 F13.2 SSH as a transport for the frame protocol (id world join --via ssh) #784 (F13.2, CLOSED/COMPLETED) via PR id: Phase 13 first slice — shell contract (F13.1), SSH transports (F13.2/F13.3), F13.7 design #842 (merged):
--via sshat pkgs/id/src/cli.rs:1774 and pkgs/id/src/commands/world.rs:921; ssh-exec transport at pkgs/id/contract/shell-contract.v1.json:19;WORLD_EXEC_COMMANDaccepted at pkgs/id/src/world_ssh.rs:369 (evidence at main 1e3763f, verified 2026-11-03). - Source: RPT §13 'How id connects today'; RPT §16 Q5
- Prerequisites: D1-049 Two SSH channels on one connection (game stream + command channel) (dropped, not filed)
- Status: delivered. Implemented by id: Phase 13 F13.2 SSH as a transport for the frame protocol (id world join --via ssh) #784 (F13.2, CLOSED/COMPLETED) via PR id: Phase 13 first slice — shell contract (F13.1), SSH transports (F13.2/F13.3), F13.7 design #842 (merged):
- D1-051 — SSH-over-iroh reachability (and iroh-over-SSH fallback) (L, research package)
Give third-party SSH clients reachability to NAT'didhosts by tunnelling SSH over iroh (tailnet-like); iroh-over-SSH only where UDP is blocked but port 22 is open. RPT asks whether this is a Phase 12/13 task.- Status: delivered. Implemented by id: Phase 13 F13.3 SSH-over-iroh reachability (and iroh-over-SSH fallback) #785 (F13.3, CLOSED/COMPLETED) via PR id: Phase 13 first slice — shell contract (F13.1), SSH transports (F13.2/F13.3), F13.7 design #842 (merged):
SSH_TUNNEL_ALPN/id-ssh-tunnel/1at pkgs/id/src/world_ssh.rs:88, accepted at pkgs/id/src/commands/serve.rs:1194, dialled at pkgs/id/src/commands/world.rs:964 (evidence at main 1e3763f, verified 2026-11-03). - Source: RPT §13 'Tunnel combinations'; RPT §16 Q5
- Prerequisites: none
- Status: delivered. Implemented by id: Phase 13 F13.3 SSH-over-iroh reachability (and iroh-over-SSH fallback) #785 (F13.3, CLOSED/COMPLETED) via PR id: Phase 13 first slice — shell contract (F13.1), SSH transports (F13.2/F13.3), F13.7 design #842 (merged):
- D1-056 — Multi-server, multi-client topology; client-only mode always supported (L, research package)
Clients connect to several worlds and servers and to other clients at once, andidis often client and server simultaneously; a client-only mode must always exist (cheap web load, SSH-only clients). SSH servers inidstay opt-in.- Status: delivered. Implemented by id: Phase 13 F13.8 multi-server, multi-client topology; client-only mode always supported #790 (F13.8, CLOSED/COMPLETED 2026-11-03): design record PR design(id): #790 multi-server client topology #3907 (
doc/2026-11-01_design_id790.md); concurrent multi-world client sessions via PR feat(id): coordinate concurrent world sessions (#3845) #3896 (WorldSessionscoordinator, pkgs/id/src/world_net.rs:1726-1830, closes id: implement F13.8 concurrent multi-server world sessions #3845); client-only boundary documented and pinned by PR docs(id): specify and test the F13.8 client-only boundary (#3846) #3862 for docs(id): specify and test F13.8 client-only boundary #3846 (pkgs/id/README.md:110-127, pkgs/id/src/cli.rs:1103-1115,4251-4286). All three PRs verified MERGED 2026-11-03. - Source: RPT §15 'Multi-server, multi-client'; RPT §15 'SSH servers in id - rare and opt-in'
- Prerequisites: none
- Status: delivered. Implemented by id: Phase 13 F13.8 multi-server, multi-client topology; client-only mode always supported #790 (F13.8, CLOSED/COMPLETED 2026-11-03): design record PR design(id): #790 multi-server client topology #3907 (
Source
.opencode/plans/phase-12-platform-flexibility.md:22.opencode/plans/phase-12-platform-flexibility.md:50.opencode/plans/phase-12-platform-flexibility.md:55- RPT §13 'How id connects today'
- RPT §13 'Tunnel combinations'
- RPT §15 'Multi-server, multi-client'
- RPT §15 'SSH servers in id - rare and opt-in'
- RPT §16 Q5
RPT = doc/2026-10-18T18-40-00Z_report_platform_world_state/2026-10-18T18-40-00Z_report_platform_world_state.md, REF = doc/2026-10-18T00-00-00Z_reference_platform_state/2026-10-18T00-00-00Z_reference_platform_state.md. Both are uncommitted reports in the platform-world-apps-migration worktree.
Size
XL overall (items L to XL)
Prerequisites
Listed per item above.
Acceptance criteria
- Every item listed above has its design (or research package, where marked) committed to the repo
- Every item has a linked implementation issue, and its checkbox above is ticked only once both are true
- No item is closed out on the basis of a plan or report reference alone — the committed artifact is the evidence
Metadata
Metadata
Assignees
Labels
Package/app: id (pkgs/ or apps/ in this repo)Large: multi-day or open-ended; expect staged check-insNew feature or capability requestIntake review done: acceptance criteria, links, and normalized labels addedFully doable remotely: design, config, code, cloudOrdinary priority (the default)Filed directly by a humanQueue packet kind: verify, reproduce, and route this item
Activity
dezren39 commentedon Oct 24, 2026
id train triage (2026-10-24): needs-decision — project owner: D1-050/051/056 are now designed in #791 (F13.2 #784 / F13.3 #785 / F13.8 #790); D1-029/D1-031 (F12.11/F12.13) are Phase 12, owned by Session C.
dezren39 commentedon Oct 26, 2026
Intake review
Verified still live on main
14dd66b6(2026-10-26, fleet monitor). Transport design tracker (F12.11 delta frames, F12.13 journal replication, and further items in the body). Spot-verified the lead item: there is noresume_tokenor frame-patch code inpkgs/id/src— delta frames have not been designed or built. No acceptance-criteria section existed, so one has been appended (original body preserved verbatim above it), following the per-item rule the body states.Related: item D1-029 is blocked on #542 (F11.9 bytes-per-frame baseline — enriched this same run; the delta target is stated as a percentage of that baseline); D1-031 names #227 as a prerequisite.
Risks / suggested approach: sequence matters — land #542's baseline first, then the F12.11 design has a concrete number to target. Each item closes only with a committed design/research package plus a linked implementation issue.
14 remaining items
dezren39 commentedon Nov 3, 2026
agent: repo-worker-code
state: done
found_via: queue task 7576
at: 2026-11-03T13:05:00Z
Triage task 7576 completed (outcome: triaged). Re-verified the tracker at main
1e3763faf; the verdict above stands and the tracker stays OPEN.Routing produced by this run:
small_fix, deduperepo-health:v1:fix:developing-today/code:issue:536) for the body close-out only: tick D1-050 (id: Phase 13 F13.2 SSH as a transport for the frame protocol (id world join --via ssh) #784) and D1-051 (id: Phase 13 F13.3 SSH-over-iroh reachability (and iroh-over-SSH fallback) #785), annotate D1-056 as partly delivered with id: Phase 13 F13.8 multi-server, multi-client topology; client-only mode always supported #790 as the remainder, leave D1-029 and D1-031 untouched. No code change.Queue labels cleared on this issue (work/assigned, queue/claimed, status/in-progress removed);
status/needs-triagewas already removed at pickup.queue/queuedwill be set by the enqueue for 7649.dezren39 commentedon Nov 3, 2026
agent-note:v1
state: triaged (coverage pass)
Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 40 (priority/normal). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
Found via: coverage pass 2026-11-03
dezren39 commentedon Nov 3, 2026
Agent note — task 7649 done (lane L shift): tracker close-out for D1-050 / D1-051 / D1-056
Body of this issue (#536) edited 2026-11-03; no other issue edited, tracker stays OPEN.
1e3763faf:--via sshatpkgs/id/src/cli.rs:1774andpkgs/id/src/commands/world.rs:921; ssh-exec transport atpkgs/id/contract/shell-contract.v1.json:19;WORLD_EXEC_COMMANDaccepted atpkgs/id/src/world_ssh.rs:369.SSH_TUNNEL_ALPN/id-ssh-tunnel/1atpkgs/id/src/world_ssh.rs:88, accepted atpkgs/id/src/commands/serve.rs:1194, dialled atpkgs/id/src/commands/world.rs:964.WorldSessions,pkgs/id/src/world_net.rs:1726-1830), client-only boundary PR docs(id): specify and test the F13.8 client-only boundary (#3846) #3862 MERGED for docs(id): specify and test F13.8 client-only boundary #3846. Per the runbook rule that current GitHub state wins over the packet, D1-056 was ticked with that evidence instead of annotated as still-remaining.