decision(atlas): layer separation — Turso PITR is DB disaster recovery, corpus retention lives in Atlas #6043

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-1708
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 · picked up

   • Agent: queue worker (repo-worker-code), lane code-u
   • Session / ID: task 10409
   • Found via: queue claim (direct execution lane)
   • Task: Triage issue decision(atlas): layer separation — Turso PITR is DB disaster recovery, corpus retention lives in Atlas #6043 — verify the decision ticket's standing and what remains to record it.
   • Expectation: s — triage findings posted, scoped follow-up enqueued for the decision record.
   • Links: task 10409 (repo-health-code-pilot)
5. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · triage findings (task 10409, lane code-u, direct lane)

   Verdict: DECISION SUBSTANCE COMPLETE — only the record itself remains. Scoped as an xs follow-up.

   Evidence (fresh, 2026-11-05):

   • Issue decision(atlas): layer separation — Turso PITR is DB disaster recovery, corpus retention lives in Atlas #6043's body already carries the decision in substance, with its research source named (prior-art doc, 2026-11-04) and the external facts cited (Turso Cloud PITR windows by plan tier, restores create a new database and count against DB quota, per docs.turso.tech). The decision: PITR is whole-database disaster recovery (≤90-day windows, no per-file version semantics); Atlas retention (version lineage, cold rollout to rustfs, deletion triggers) lives in Atlas's own tables + rustfs, permanently policy-driven; the two never substitute for each other.
   • Parent issue design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026 (content versioning + retention) is OPEN and already links this ticket from a comment — the "linked from design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026" half of done exists at comment level.
   • Nothing in the decision needs further research or a Drew ruling: it is a layer-separation statement consistent with the parent design's own framing.

   Remaining work (enqueued as an xs small_fix): write the one-page decision record under doc/ in this repo from the issue body (decision, rejected substitution, the two questions each mechanism answers), link the record from parent issue #6026, and close issue #6043 with the record link. No code, no design reopening — if the record-writing surfaces a genuine conflict with the parent design, it stops and records it here instead of editing around it.

   This triage (task 10409) completes as triaged; issue #6043 stays open until the record lands and closes it.
6. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · done

   • Agent: queue worker (repo-worker-code), lane code-u
   • Session / ID: task 10409
   • Found via: queue claim (direct execution lane)
   • Task: Triage of issue decision(atlas): layer separation — Turso PITR is DB disaster recovery, corpus retention lives in Atlas #6043 complete — decision substance verified complete and sourced; xs follow-up enqueued as task 10514 to write the doc/ decision record, link it from parent issue design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026, and close this issue.
   • Expectation: done — triage outcome exists.
   • Links: task 10409 (done, outcome triaged), task 10514 (queued follow-up), parent issue design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026
7. 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
8. 2 remaining items

   Load more

9. 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 9aca43b4-5439-4939-9f71-323f5d32521b
   • Session / ID: task 10514; attempt 1/3
   • Found via: queue claim
   • Task: Add the agreed PITR-vs-Atlas-retention decision record under doc/, link it from design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026, and close decision(atlas): layer separation — Turso PITR is DB disaster recovery, corpus retention lives in Atlas #6043 with the record link.
   • Verified: decision(atlas): layer separation — Turso PITR is DB disaster recovery, corpus retention lives in Atlas #6043 and parent design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026 are OPEN; decision(atlas): layer separation — Turso PITR is DB disaster recovery, corpus retention lives in Atlas #6043 has no hard-stop labels. Fresh timeline/open-PR scan found no matching implementation PR or competing linked work. Its body already records the decision substance; no conflict found at pickup.
   • Next: create a dedicated laptop worktree and make only the doc change.
   • Links: task 10514 · decision(atlas): layer separation — Turso PITR is DB disaster recovery, corpus retention lives in Atlas #6043 · design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026
10. dezren39

    added

    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

    and removed

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

    on Nov 5, 2026
11. developing-today

    added

    status:in-review

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

    

    dezren39

    on Nov 5, 2026

    MemberAuthor

    More actions

    🤖 Agent note · pr_opened

    • Agent: queue worker (repo-worker-code), OpenChamber scheduled lane 9aca43b4-5439-4939-9f71-323f5d32521b
    • Session / ID: task 10514; attempt 1/3
    • Task: Dated decision record is in PR docs(atlas): record PITR vs retention boundary (#6043) #6269. The parent design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026 now links the record; PR body uses Closes #6043 so merge will close this issue.
    • Record: Turso PITR vs Atlas retention
    • Next: if required checks remain pending, park and resume to merge/verify after CI.
    • Links: PR docs(atlas): record PITR vs retention boundary (#6043) #6269 · design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026 · task 10514
13. dezren39

    added a commit that references this issue on Nov 5, 2026

    Merge pull request #6269 from developing-today/queue/10514-6043-atlas…

    ...

    882cb5d
14. dezren39

    closed this as completedin #6269on Nov 5, 2026
15. developing-today

    added

    status:done

    and removed

    status:in-review

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

    

    dezren39

    on Nov 5, 2026

    MemberAuthor

    More actions

    🤖 Agent note · done

    • Agent: queue worker (repo-worker-code), OpenChamber scheduled lane 9aca43b4-5439-4939-9f71-323f5d32521b
    • Session / ID: task 10514; attempt 1/3
    • Task: Decision record added, linked from parent design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026, and merged.
    • Verified: PR docs(atlas): record PITR vs retention boundary (#6043) #6269 merged at 882cb5d63e357438c13729aacb570f0a31842b08; record exists on main; PR auto-closed decision(atlas): layer separation — Turso PITR is DB disaster recovery, corpus retention lives in Atlas #6043.
    • Record: Turso PITR vs Atlas retention
    • Links: PR docs(atlas): record PITR vs retention boundary (#6043) #6269 · parent design(atlas): content versioning + retention — versions, rename lineage, newest-resolution, cold rollout, deletion triggers #6026 · task 10514
17. 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