Questions posed and not answered, listed at full weight because a residual that is hard to read is a residual that gets forgotten. These are the eight from the worked case; the collective-bound exhibit carries its own.
A12
A hostile actor running as the same user
An actor who can run code as this user edits the target directly and needs no permit at all; equally, they can append a well-formed start permit to the ledger. The successor does not create an unforgeable token.
Explicitly out of scope. Not weakened or strengthened by the repair.
OPENCRASH-WINDOW
At-most-once is argued, not demonstrated
No process has been killed between the consumption commit and the write. The ordering argument is sound and untested.
It is the cheapest remaining test and it has not been run. A scheduled consumer runs unattended, which is exactly the regime where a killed process matters.
OPENA-LOCK
The file lock is advisory
Every writer must use the ledger transaction. That is convention, not enforcement.
A writer that ignores the lock defeats the at-most-once guarantee. The auditor detects the resulting sequence disagreement after the fact; it does not prevent it.
OPENA-CLOCK
Freshness depends on the system clock
A moved clock moves the time-to-live window.
Carried as an assumption in the trusted base, named there rather than tested.
OPENA-FS
Filesystem atomicity and durability are assumed
Atomic replace and durable flush are assumed, not tested.
A crash must leave the original intact. That property rests on the platform and is carried as an assumption.
OPENNO-LIVE-DEMO
No live eligible-condition demonstration
The successor has never executed anything outside a sandbox.
Manufacturing a live eligible condition means deliberately corrupting a real scheduled job. Not done, not worked around.
OPENN-4
A latent defect left unrepaired by design
The sequence double-count in the frozen ledger transaction is measured, understood and deliberately not fixed.
Editing it would break the freeze that makes the predecessor citable evidence. The successor refuses on detecting it instead.
OPENONE-TRANSFORM
One transform is in the closed table
Nothing establishes that the property generalises to a transform that is not idempotent and not byte-derivable from a backup.
The bound is real and it is narrow. The narrowness is the finding, not a caveat on it.
OPEN