id: design: region-seam handoff format — journaled export/import for hot-world region shards (from #2059) #2818

Activity

1. dezren39

   added

   app/idPackage/app: id (pkgs/ or apps/ in this repo)Package/app: id (pkgs/ or apps/ in this repo)

   on Oct 30, 2026
2. github-actions

   assigned

   dezren39

   on Oct 30, 2026
3. dezren39

   added

   kind/designA design proposal (design-architect): multi-step, phased, decision-bearingA design proposal (design-architect): multi-step, phased, decision-bearing

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   priority/normalOrdinary priority (the default)Ordinary priority (the default)

   effort/lLarge: multi-day or open-ended; expect staged check-insLarge: multi-day or open-ended; expect staged check-ins

   on Oct 31, 2026
4. dezren39 commented on Oct 31, 2026

   

   dezren39

   on Oct 31, 2026

   MemberAuthor

   More actions

   Intake review

   Related: parent #2059; sibling #2819.

   Notes: design-stage issue spun out of #2059; body already carries an acceptance section, so none was appended. No merged PR or commit found this run that implements this design — verified still live.

   Risks: design drift if the sibling design lands first and changes shared assumptions (hot-world sharding seams) — the two designs should be read together before either is implemented.

   Suggested approach: keep as design; when picked up, the design output should land as a linked implementation issue per the standing "a design is not finished work" rule.

   🤖 Agent note · filed

   • Agent: fleet monitor
   • Session / ID: repo-fleet-monitor run 2026-10-30 23:12 CDT
   • Found via: monitor reconciliation
   • Task: intake enrichment (protocol §5) for this issue
   • Expectation: labels normalized; body unchanged (acceptance section already present)
   • Links: id: investigate: hot-world sharding — when one world outgrows one Durable Object #2059, id: design: native-spill write lease protocol for hot worlds (from #2059) #2819
5. dezren39

   added

   meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   on Oct 31, 2026
6. dezren39 commented on Nov 1, 2026

   

   dezren39

   on Nov 1, 2026

   MemberAuthor

   More actions

   🤖 Agent note · picked up

   • Agent: queue worker (repo-worker-code), lane F (repo-queue-worker-shift-f)
   • Session / ID: queue task 5744 (triage), claimed 2026-11-01T16:45Z
   • Found via: queue claim
   • Task: Triage id: design: region-seam handoff format — journaled export/import for hot-world region shards (from #2059) #2818: verify the design claims against current main (investigation doc for id: investigate: hot-world sharding — when one world outgrows one Durable Object #2059, pkgs/id journal patterns, sibling id: design: native-spill write lease protocol for hot worlds (from #2059) #2819), post a decision-ready design record, and route the implementation as phased packets.
   • Expectation: m — design record + enqueued packet(s) listed on this issue this shift; no Drew-blocking question left silent.
   • Links: queue task 5744; parent id: investigate: hot-world sharding — when one world outgrows one Durable Object #2059; sibling id: design: native-spill write lease protocol for hot worlds (from #2059) #2819; consumer id: design: ID serverless edition v1 (Cloudflare Workers) #2046; epic epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056
7. dezren39 commented on Nov 1, 2026

   

   dezren39

   on Nov 1, 2026

   MemberAuthor

   More actions

   🤖 Agent note · triaged — CONFIRMED; design record below; design production routed as one packet (task 5802)

   • Agent: queue worker (repo-worker-code), lane F (repo-queue-worker-shift-f)
   • Session / ID: queue task 5744 (triage), claimed 2026-11-01T16:45Z
   • Verified against main a9e976ac245d94682ff7ada8dd5562cc58c9b00f (gh api contents + code search, 2026-11-01):
     • ✅ The id: investigate: hot-world sharding — when one world outgrows one Durable Object #2059 investigation doc exists (doc/2026-10-30T19-35-00Z_investigation_hot_world_sharding/). Its §3 rung 2 (doc lines 161–170) settles the model: sibling shard-worlds under a thin coordinator; a boundary crossing is a journaled export from region A + import to region B — a two-step handoff, not a distributed transaction. Its §5 (lines 247–252) bounds the coordinator journal to membership, the region map, and handoffs and requires the seam to stay visible (an entity mid-handoff is in transit, visibly). Its §9 (lines 298–300) files this issue as the handoff-format design. The model is decided; the record format is genuinely undesigned.
     • ✅ The in-tree pattern the format must follow exists: JournalEntry enum at pkgs/id/src/world/mod.rs:475 — typed serde variants with replay semantics documented per variant; CrossWorldWrite at world/mod.rs:580 is the precedent for a policy-adjacent journal record; WorldLimits at world/mod.rs:59 is the configurability precedent.
     • ✅ The durability contract: WorldActor::persist at pkgs/id/src/world/actor.rs:376 appends + fsyncs and turns the world read-only on failure; set_cross_world_write at actor.rs:882 shows the journal-before-apply ordering (persist first, then mutate core state) every handoff step must follow.
     • ✅ Family state: id: investigate: hot-world sharding — when one world outgrows one Durable Object #2059 closed, id: design: ID serverless edition v1 (Cloudflare Workers) #2046 open (consumer synthesis), id: design: native-spill write lease protocol for hot worlds (from #2059) #2819 open (sibling rung-3 lease design), epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056 open (epic). This issue carries only the fleet-monitor intake note — no prior design record, no merged PR implements it, no fix packet existed before this triage (queue searched).

   Design record (the record the design doc must produce)

   • Decision to be made: the concrete journaled export/import record pair for a rung-2 region seam — fields, ordering, idempotency — plus the client-observation semantics and failure recovery, concrete enough to implement against actor.rs's journaled-entry patterns.
   • Options for the record shape: (1) dedicated JournalEntry variants on both sides (export record in A, import record in B) plus coordinator handoff open/close records; (2) handoff payloads carried inside generic Committed events; (3) coordinator-only records, shards journal nothing.
   • Recommendation: option 1. It is the only shape that keeps replay semantics explicit per variant (the world/mod.rs:475 convention), lets each shard's journal be the source of truth for its side (required for the coordinator-dies walk), and matches the CrossWorldWrite precedent. Option 2 buries a state machine inside opaque payloads; option 3 contradicts §5 and makes coordinator loss unrecoverable.
   • Invariants the design must hold: no entity duplication; no silent loss; journal-before-apply at every step; duplicate import is an idempotent no-op keyed by handoff_id; the seam stays visible (in-transit is a client-observable state, never papered over); the coordinator journals only membership, region map, and handoffs — no entity state, no cross-region transaction emulation.
   • Pinned questions for the design doc (each decided there, with trade-offs): record fields for export/import/coordinator pair; handoff_id derivation; transfer payload (full snapshot vs snapshot + journal reference) and its bounds; completion (import journaled in B and coordinator closure journaled) vs stuck (policy window after export) with a named recovery owner per state; the client state table (owned-by-A / in-transit / owned-by-B × legal reads/writes); the four failure walks from this issue's body; shared coordinator-journal conventions with sibling id: design: native-spill write lease protocol for hot worlds (from #2059) #2819, read together before writing (the intake review's drift warning).
   • Phasing — explicit one-packet statement: implementation packets are not enqueued now; before the format exists they would be speculative packet defects. The design production is one packet (below); buildable fallout gets filed as its own issues + packets by that packet, per this issue's acceptance. This issue stays open until the design doc lands.
   • Routing: packet packets/task5744-2818-region-seam-handoff-design.json, enqueued as queue task 5802, dedupe key repo-health:v1:fix:developing-today/code:issue:2818, queue repo-health-code-pilot, status queued.
   • Questions for Drew: none blocking. One deferred decision, named rather than stalled: shard re-merge/de-escalation is out of scope here — the investigation (§5) leaves it an open question for the id: design: ID serverless edition v1 (Cloudflare Workers) #2046 synthesis; recommendation is the handoff format must not preclude a later state-import design but does not design it. The design packet proceeds on that basis.
8. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   and removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 1, 2026
9. 37 remaining items

   Load more
10. dezren39

    added

    queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

    source/creatorFiled by the new-issue-creator jobFiled by the new-issue-creator job

    status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

    task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

    on Nov 3, 2026
11. developing-today commented on Nov 3, 2026

    

    developing-todayBot

    on Nov 3, 2026 – with developing.today

    Contributor

    More actions

    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
12. dezren39

    added

    work/assignedQueue worker lifecycle stateQueue worker lifecycle state

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    and removed

    status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

    queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

    on Nov 3, 2026
13. developing-today commented on Nov 3, 2026

    

    developing-todayBot

    on Nov 3, 2026 – with developing.today

    Contributor

    More actions

    🤖 Agent note · picked up

    • Agent: queue worker (repo-worker-code), lane M shift
    • Session / ID: queue task 7986 (triage, coverage pass 2026-11-03)
    • Found via: queue claim · coverage join
    • Task: Triage id: design: region-seam handoff format — journaled export/import for hot-world region shards (from #2059) #2818 at current main: confirm the region-seam handoff design is still owed, or route/close with evidence.
    • Expectation: effort/xs for the triage itself — done = verdict with fresh-main evidence; no competing design work if a canonical deliverable exists
    • Links: issue id: design: region-seam handoff format — journaled export/import for hot-world region shards (from #2059) #2818 · PR design(id): #2818 region-seam handoff format #3875 · issue id: implement: journaled region-seam export/import #3870 · issue id: design: ID serverless edition v1 (Cloudflare Workers) #2046
14. developing-today commented on Nov 3, 2026

    

    developing-todayBot

    on Nov 3, 2026 – with developing.today

    Contributor

    More actions

    🤖 Agent note · done (triage verdict: design deliverable ALREADY DONE; issue stays open for consumer adoption)

    • Agent: queue worker (repo-worker-code), lane M shift
    • Session / ID: queue task 7986 (triage, coverage pass 2026-11-03)
    • Found via: queue claim · coverage join
    • Task: Re-verify id: design: region-seam handoff format — journaled export/import for hot-world region shards (from #2059) #2818 at current main without duplicating the canonical design work

    Evidence (fresh, 2026-11-03):

    • The design this issue asks for was produced by queue task 5802 and merged as PR design(id): #2818 region-seam handoff format #3875 ("design(id): id: design: region-seam handoff format — journaled export/import for hot-world region shards (from #2059) #2818 region-seam handoff format", merged 2026-11-02T15:49:21Z, merge commit 198ace8af109ce7d53acd5af342fb981b1e752c2).
    • The deliverable is on current main: doc/2026-11-01_design_id2818.md (44,787 bytes, blob e26a45cea8) — dedicated EntityExported/EntityImported journal variants plus coordinator open/close records, record fields and ordering/idempotency rules, client transit semantics, failure-recovery walks, and five sequentially mergeable implementation packets. That covers this issue's "Design to produce" list and its doc-under-doc/ acceptance item.
    • "Anything buildable filed as its own issue" is also satisfied: implementation follow-up id: implement: journaled region-seam export/import #3870 ("id: implement: journaled region-seam export/import") is OPEN and queued.
    • Why this issue itself stays OPEN: task 5802's closing note recorded the deliberate decision that id: design: region-seam handoff format — journaled export/import for hot-world region shards (from #2059) #2818 remains open for consumer adoption / fallout tracking, and the consumer — id: design: ID serverless edition v1 (Cloudflare Workers) #2046 (ID serverless edition v1 synthesis) — is still OPEN. The 2026-11-03 coverage pass independently re-verified the issue as still live on that basis. Closing it now would erase the adoption tracking before the consumer lands.

    Routing: none new — #3870 owns the implementation, #2046 owns adoption. No branch, worktree, or competing design created. This coverage triage (task 7986) completes as triaged / already_done for the design deliverable.
    (Note: posted via the developing.today GitHub App — the user-token content-creation secondary rate limit is still active this shift.)
15. dezren39

    removed

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    work/assignedQueue worker lifecycle stateQueue worker lifecycle state

    on Nov 3, 2026