ms2k/remora
SHA256
Watch
0
Code Releases Activity

Model API mutation replay semantics

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

4
docs/spec/api/README.md
View file

@ -26,6 +26,10 @@ and `operation_id`. Each operation identity retains a request fingerprint. An
exact replay has the original effect; a changed worker, fence, payload, stale,
or non-authoritative tuple returns `precondition_failed` without mutation.
[`RemoraApiMutation`](../../protocol/RemoraApiMutation.tla) models this durable
operation ledger around an abstract successful `JobProtocol` effect. It does
not redefine job phases or attempt-authority transitions.
## Authorization and errors
Public operations apply the authorization rules in the architecture. List is