Repository navigation
id(phase-14): Hosted worlds & always-on hosting — v4 — outline: public-server operation #6286
Description
Hosted worlds & always-on hosting — v4 — outline: public-server operation
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)
Operating a large public host: sharding worlds across backend iroh/id servers behind the public endpoint, private tunnels between tiers, abuse controls, cost model and operator tooling.
Entry condition
The previous step (v3 — outline: many nodes) 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-1852
dezren39 commentedon Nov 6, 2026
Intake review
Fleet monitor intake (§5 pass), 2026-11-05 run.
dezren39 commentedon Nov 6, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 6, 2026
🤖 Agent note · done
Triage findings (task 11058)
Verdict: valid Phase 14 step, correctly sequenced, NOT yet actionable — entry condition unmet. Hold at outline; do not start the refined outline yet.
Evidence, verified fresh 2026-11-06 ~12:25–12:28 UTC:
priority/low,effort/s, no hard-stop labels (held,user/owned,do-not-merge,do-not-auto-editall absent). No merged PR implements it; the only prior comments are the Kaneo link and the 2026-11-05 fleet-monitor intake review.status/needs-triage, no design posted) → issue id(phase-14): Hosted worlds & always-on hosting — v2 — outline: custody & lifecycle #6284 (v2 custody & lifecycle outline, open, stillstatus/needs-triage, no design posted) → issue id(phase-14): Hosted worlds & always-on hosting — v3 — outline: many nodes #6285 (v3 many-nodes outline, open) → issue id(phase-14): Hosted worlds & always-on hosting — v4 — outline: public-server operation #6286 (this, v4).Routing: triage complete. The issue stays open at outline stage; work resumes when issue #6285's design is posted with questions answered or deferred here. No follow-up fix task is enqueued — the predecessor chain's own queued tasks own the sequencing.