Bound durable outbox storage and enforce process writer exclusion
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a140c4-354a-7823-8f0d-8f717397f786
This commit is contained in:
parent
2b064eee51
commit
0a05383195
14 changed files with 733 additions and 26 deletions
|
|
@ -272,3 +272,14 @@ the issued claim; registry drift/refreshed facts cannot silently rebind it.
|
|||
Retained-registry HTTP and production serve proofs and negative joins pass.
|
||||
R3 preserves precise notbefore pending separate Approval-owner timestamp fidelity
|
||||
repair; no rounding waiver, copied registry algorithm or empty-registry workaround.
|
||||
|
||||
2026-10-16 native admission prerequisite: fresh metadata confirms no namespace
|
||||
PVC exists, and current outbox had neither OS writer exclusion nor a byte/startup
|
||||
bound. Prepared existing-outbox hardening on exact canonical R3 base2b064ee:
|
||||
nonblocking Linux flock held through Close/process lifetime before recovery,
|
||||
64MiB source journal ceiling,2MiB record/atomic-batch bounds, streaming startup,
|
||||
4KiB cursor, all-effect commit refusal and fenced unconfirmed rollback. Actual
|
||||
process contention/crash release, capacity/prefix/restart and ENOSPC/fsync failure
|
||||
proofs are part of the owner package. No new service, live mount, deletion or
|
||||
custody grant; exact published successor, new PVC/PV retention/managed-package
|
||||
owner disposition and independent consumer admission remain prerequisites.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue