ms2k/remora
SHA256
Watch
0
Code Releases Activity

Define durable target cleanup boundaries

Browse source
This commit is contained in:
ms2k 2026-07-13 14:03:23 +09:00
commit 797d971b61
1 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/spec/architecture.md
View file

@ -106,6 +106,13 @@ flowchart TD
- Raw target listing is operational storage visibility, not result resolution. Clients with independent target credentials may observe uncommitted attempt objects. - Raw target listing is operational storage visibility, not result resolution. Clients with independent target credentials may observe uncommitted attempt objects.
- A stable user-chosen object key or atomically visible raw target prefix is not part of a job result. Providing one requires a separate export contract. - A stable user-chosen object key or atomically visible raw target prefix is not part of a job result. Providing one requires a separate export contract.
## Target Cleanup
- `DurableStore` retains exact attempt ownership and pending cleanup work so cleanup can recover independently of `CoordinationStore`.
- Ambient cleanup processes are stateless and idempotent. Worker-local cleanup may reduce latency but is not the only cleanup path.
- Cleanup revalidates authority in `DurableStore` and addresses exact attempt object or multipart identities. Missing coordination state, target-object age, and raw prefix membership do not grant cleanup authority.
- Target lifecycle rules are storage hygiene only. They do not determine result publication or cleanup eligibility and must not expire completed attempt objects that Remora may still protect.
## Requirements ## Requirements
### Functional Requirements ### Functional Requirements