design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042

Activity

1. dezren39

   added

   area/infraInfrastructure, deployment, and operationsInfrastructure, deployment, and operations

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

   on Nov 5, 2026
2. developing-today commented on Nov 5, 2026

   

   developing-todayBot

   on Nov 5, 2026 – with developing.today

   Contributor

   More actions

   CODE-1707
3. dezren39

   added

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

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

   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

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

   on Nov 5, 2026
4. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · handed off

   • Agent: queue worker (repo-worker-code), lane code-r
   • Session / ID: task 10408
   • Found via: queue claim
   • Task: Triage of issue design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042 handed off to the opencode execution lane; the laptop claimant launches the bound opencode session, which drives task 10408 to its terminal state.
   • Expectation: claimant launches bound session; triage at current main with evidence per the packet acceptance criteria.
   • Links: design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042
5. dezren39

   added

   queue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)

   status/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume condition

   and removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 5, 2026
6. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · handed off

   • Agent: queue worker (repo-worker-code), lane code-o
   • Session / ID: task 10408
   • Found via: queue claim
   • Task: Triage issue design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042 (design(atlas): cold-tier shard format) — assigned to the opencode execution lane again on re-claim (previously handed off at 2026-11-05T12:57Z, claimant had not launched before the park cycled); handed off to the laptop claimant, not worked by this lane. Issue verified OPEN this shift, no hard-stop labels.
   • Expectation: claimant launches the bound opencode session for task 10408.
   • Links: n/a
7. 1 remaining item

   Load more

8. developing-today commented on Nov 5, 2026

   

   developing-todayBot

   on Nov 5, 2026 – with developing.today

   Contributor

   More actions

   🤖 Agent note · handed off

   • Agent: queue worker (repo-worker-code), lane code-y
   • Session / ID: task 10408
   • Found via: queue claim
   • Task: Re-handoff of the triage of issue design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042 to the opencode execution lane (assigned_lane=opencode, session not yet bound); the previous handoff at 12:57Z went unlaunched. Labels already carried the parked set; verified fresh this claim.
   • Expectation: The laptop claimant launches the bound opencode session for task 10408, which drives it to its terminal state.
   • Links: issue design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042
9. dezren39

   added

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 5, 2026
10. dezren39 commented on Nov 5, 2026

    

    dezren39

    on Nov 5, 2026

    MemberAuthor

    More actions

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-i
    • Session / ID: task 10408
    • Found via: queue claim
    • Task: handing task 10408 (issue design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042) to the opencode execution lane; the laptop claimant launches the bound opencode session
    • Expectation: claimant drives task 10408 to a terminal state; parked 30 min to release this lane's claim
    • Links: issue design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042
11. dezren39

    added

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    and removed

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    status/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume condition

    queue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)

    on Nov 5, 2026
12. dezren39 commented on Nov 5, 2026

    

    dezren39

    on Nov 5, 2026

    MemberAuthor

    More actions

    🤖 Agent note · picked up

    • Agent: queue worker (repo-worker-code), OpenChamber scheduled lane 262eb403-3347-4a7c-ba6b-e7bc263ca853
    • Session / ID: task 10408
    • Found via: atomic queue claim
    • Task: Triage issue design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042, validating its cold-shard format/restore scope and dependencies against parent design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026.
    • Expectation: record whether the design remains needed and its ordering, then complete task 10408 as triaged.
    • Links: task 10408 · issue design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042 · parent design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026
13. dezren39 commented on Nov 5, 2026

    

    dezren39

    on Nov 5, 2026

    MemberAuthor

    More actions

    🤖 Agent note · triaged

    • Agent: queue worker (repo-worker-code), OpenChamber scheduled lane 262eb403-3347-4a7c-ba6b-e7bc263ca853
    • Session / ID: task 10408
    • Found via: atomic queue claim
    • Task: Triage design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042; its self-describing cold-shard format and restore design remains live and distinct.
    • Expectation: keep design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042 open as the design handoff; align the format/restore contract with parent design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026 and sibling retention policy design(atlas): retention rule engine — composite age / supersede-count / last-surfaced policy with dry-run reporter #6041.
    • Links: task 10408 · design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042 · parent design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026 · related design(atlas): retention rule engine — composite age / supersede-count / last-surfaced policy with dry-run reporter #6041 and decision decision(atlas): layer separation — Turso PITR is DB disaster recovery, corpus retention lives in Atlas #6043 / PR docs(atlas): record PITR vs retention boundary (#6043) #6269

    Triage findings (verified against current GitHub state and main, 2026-11-05)

    • design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042 is OPEN, as is parent design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026. No hard-stop labels or directly matching open PR were found. The requested self-describing rustfs shard format, provenance-preserving restore/re-import path, and explicit cold-shard addressing are a distinct design; no corresponding format/restore decision record exists on current main. Keep the issue open.
    • The related layer-boundary decision is already settled: decision(atlas): layer separation — Turso PITR is DB disaster recovery, corpus retention lives in Atlas #6043 is CLOSED by merged PR docs(atlas): record PITR vs retention boundary (#6043) #6269. Its record says Turso PITR is whole-database disaster recovery, not corpus retention; Atlas lineage, cold rollout to rustfs, and deletion policy remain Atlas-owned. Use that boundary rather than treating PITR as the cold-shard restore mechanism.
    • Parent design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026 remains the source for version identity, lineage, provenance, and query-time newest-version semantics. Sibling design(atlas): retention rule engine — composite age / supersede-count / last-surfaced policy with dry-run reporter #6041 owns the composite retention-rule/dry-run design and has its own follow-up task #10569. design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042 can proceed as its own design; coordinate the retention-state and cold-before-delete boundary with design(atlas): retention rule engine — composite age / supersede-count / last-surfaced policy with dry-run reporter #6041, and specify restore-to-hot provenance without duplicating the policy engine.
    • Route: design(atlas): cold-tier shard format — self-describing rustfs shards and the restore path back to hot #6042 itself is the design handoff, so no additional queue task was created by this triage. No code change or runtime test applies.
    • Verification base: laptop main at 00a294a; the decision(atlas): layer separation — Turso PITR is DB disaster recovery, corpus retention lives in Atlas #6043 decision record is present there.
14. 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 5, 2026