Skip to content

id(phase-14): Hosted worlds & always-on hosting — v2 — outline: custody & lifecycle #6284

New issue
New issue
Open
Open
id(phase-14): Hosted worlds & always-on hosting — v2 — outline: custody & lifecycle#6284
Labels
app/idPackage/app: id (pkgs/ or apps/ in this repo)effort/mMedium: expected under 1 day of workkind/featureNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/lowNice to have; do when convenientqueue/claimedQueue worker lifecycle statesource/humanFiled directly by a humanstatus/in-progressQueue worker lifecycle statetask/triageQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle state

Description

@dezren39
dezren39
opened on Nov 5, 2026

Hosted worlds & always-on hosting — v2 — outline: custody & lifecycle

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)

Snapshots and export/import of hosted worlds; backup/restore drills; lifecycle automation (auto-sleep idle worlds, wake on join); per-world resource limits wired to F12.10 quotas.

Entry condition

The previous step (v1 — first-iteration design) 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

  1. dezren39
    added
    kind/featureNew feature or capability request
    status/needs-triageNot yet triaged; needs a first look
    source/humanFiled directly by a human
    priority/lowNice to have; do when convenient
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    effort/mMedium: expected under 1 day of work
    on Nov 5, 2026

  2. developing-today commented on Nov 5, 2026

    @developing-today
    developing-todayBot
    on Nov 5, 2026 – with developing.today
    Contributor

    CODE-1850

  3. dezren39
    added
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Nov 6, 2026

  4. dezren39 commented on Nov 6, 2026

    @dezren39
    dezren39
    on Nov 6, 2026
    MemberAuthor

    Intake review

    Fleet monitor intake (§5 pass), 2026-11-05 run.

    • Still live: yes — issue open, filed 2026-11-05/06; merged-PR search for an explicit resolving reference found none (the few merged PRs whose text contains this issue's number are unrelated cross-references — e.g. PR titles fixing other issues — not implementations of this ticket). Nothing to close.
    • Related: Phase 14 core topic id(phase-14): Hosted worlds & always-on hosting — core topic (research + design) #6276 (Hosted worlds & always-on hosting); principles in id: next horizons — what comes after Phase 13 (discussion with Drew) #1240; previous step is the v1 first-iteration design issue in the same series.
    • Notes: Outline step, not an implementation ticket: custody & lifecycle (snapshots, backup/restore drills, auto-sleep/wake, per-world resource limits wired to F12.10 quotas). It stays inert until the v1 design lands — the entry condition is the gate, not the calendar.
    • Risks: Sequence risk only: refining this outline before v1 exists invites rework. No code or user impact at this stage.
    • Suggested approach: Leave queued behind the v1 step; when v1's design is written, refine this outline against it and file the next-step breakdown then.
  5. dezren39
    added
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 6, 2026
  6. dezren39
    marked this as blocking on Nov 6, 2026
  7. dezren39
    added a parent issue on Nov 6, 2026
  8. dezren39
    added
    queue/claimedQueue worker lifecycle state
    and removed
    status/needs-triageNot yet triaged; needs a first look
    on Nov 6, 2026

  9. 32 remaining items

  10. dezren39
    added
    queue/claimedQueue worker lifecycle state
    status/in-progressQueue worker lifecycle state
    and removed
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    on Nov 8, 2026

  11. dezren39 commented on Nov 8, 2026

    @dezren39
    dezren39
    on Nov 8, 2026
    MemberAuthor

    🤖 Agent note · handed off

  12. developing-today commented on Nov 8, 2026

    @developing-today
    developing-todayBot
    on Nov 8, 2026 – with developing.today
    Contributor

    🤖 Agent note · handed off

  13. dezren39
    added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    queue/claimedQueue worker lifecycle state
    status/in-progressQueue worker lifecycle state
    and removed
    queue/claimedQueue worker lifecycle state
    status/in-progressQueue worker lifecycle state
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    on Nov 8, 2026

  14. dezren39 commented on Nov 8, 2026

    @dezren39
    dezren39
    on Nov 8, 2026
    MemberAuthor

    🤖 Agent note · handed off

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    app/idPackage/app: id (pkgs/ or apps/ in this repo)effort/mMedium: expected under 1 day of workkind/featureNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/lowNice to have; do when convenientqueue/claimedQueue worker lifecycle statesource/humanFiled directly by a humanstatus/in-progressQueue worker lifecycle statetask/triageQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle state

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions