ms2k/remora
SHA256
Watch
0
Code Releases Activity

Define source resumption proof boundaries

Browse source
This commit is contained in:
ms2k 2026-07-13 14:15:02 +09:00
commit 6b6e315776
1 changed files with 8 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/spec/architecture.md
View file

@ -113,6 +113,14 @@ flowchart TD
- 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.
## Source Identity and Resumption
- A reusable checkpoint binds an immutable `Source` identity, an exact completed boundary, and validated destination state. If any proof is absent or changed, the replacement restarts that member from the beginning.
- HTTP identity includes the resolved final URL, a strong representation validator as defined by `RFC 9110`, representation length, and identity content encoding. Resume requires a conditional byte-range response whose validator, URL, encoding, and range exactly match the checkpoint. Weak validators, length, or modification time alone do not qualify.
- Object-store identity includes endpoint, bucket, key, size, and an immutable version ID when available. Without a version ID, resume requires a matching conditional range read. Destination multipart reuse additionally requires the same endpoint, bucket, key, upload ID, and exact re-listed completed parts.
- A Hugging Face branch or tag is resolved once to a full commit. The source identity includes repository type and ID, that commit, and the exact file inventory with Git blob or LFS identities. Retries and cache reuse remain pinned to the stored commit and member identities.
- A checkpoint never authorizes best-effort concatenation. An unavailable explicitly pinned or resolved snapshot produces a structured source-changed outcome rather than silently resolving a newer snapshot.
## Requirements
### Functional Requirements