Repository navigation
id(phase-14): Hosted worlds & always-on hosting — v3 — outline: many nodes #6285
Description
Hosted worlds & always-on hosting — v3 — outline: many nodes
Part of the Phase 14 core topic #6276 (Hosted worlds & always-on hosting), filed from the next-horizons discussion #1240 per Drew's 2026-11-05 decision. The Phase 14 epic links the whole map.
Scope (rough outline — the core topic's research refines it)
World migration between hosts (move a live world laptop → home server → public host); replication via F12.13 read replicas; hosted worlds joining multi-node sessions (F12.11).
Entry condition
The previous step (v2 — outline: custody & lifecycle) has its design written, with open questions answered or explicitly deferred to this step.
Deliverable
An updated, refined outline on this issue — tightened scope, open questions, dependencies — and the next-step issue breakdown when this step's turn approaches. If the step has dissolved into the previous one, close this issue with that note (drop rule).
Drew's Phase 14 principles (#1240) govern this step: local-first always; hostable by anyone at any scale; p2p behavior identical to hosted behavior; our hosted instance is the public backstop, never a requirement.
Acceptance criteria
- Entry condition verified on this issue: the previous step's design is written, with its open questions answered or explicitly deferred to this step.
- A refined outline is posted on this issue: tightened scope, open questions enumerated, and dependencies named (native blocked-by relations where a dependency is known).
- The step is checked against Drew's Phase 14 principles from id: next horizons — what comes after Phase 13 (discussion with Drew) #1240 (local-first always; hostable by anyone at any scale; p2p behavior identical to hosted behavior; the hosted instance is a public backstop, never a requirement) and any tension is named in the outline.
- Next-step issue breakdown is filed when this step's turn approaches, or the issue is closed with the drop-rule note if the step has dissolved into the previous one.
Activity
developing-today commentedon Nov 5, 2026
CODE-1851
dezren39 commentedon Nov 6, 2026
Intake review
Fleet monitor intake (§5 pass), 2026-11-05 run.
dezren39 commentedon Nov 6, 2026
Triage (task 11057, lane code-f, direct execution lane): issue #6285 is a valid Phase 14 step in the #6276 core-topic chain, correctly sequenced but NOT yet actionable — its entry condition is unmet.
Findings: