Skip to content

fix(enforcement): refuse live-ledger replay after record loss - #805

Merged
antropos17 merged 2 commits into
masterfrom
codex/live-ledger-replay-refusal-20261008
Oct 8, 2026
Merged

antropos17 merged 2 commits into
masterfrom
codex/live-ledger-replay-refusal-20261008

Conversation

@antropos17

Copy link
Copy Markdown
Owner

If an operation effect deletes its spent record before settlement, the same live ledger could dispatch that operation again under a newly issued capability. Retain hashes of successfully consumed operation IDs in private bounded memory, refuse replay before filesystem admission, and report missing persisted history as unavailable.

Failed consumption does not reserve an ID. History has the existing 256-entry ceiling, with no eviction. This guarantee applies to the same live ledger; restart after complete record erasure, rollback and power-loss qualification still require protected durable ownership.

Validation: 68 tests across the affected ledger/broker and four direct-caller suites passed after integration; scoped ESLint and formatting passed. Independent Astra requirements, engineering and integration binding reviews passed. Required GitHub contexts must pass on this PR head before merge.

@antropos17
antropos17 merged commit 13c2074 into master Oct 8, 2026
5 checks passed
@antropos17
antropos17 deleted the codex/live-ledger-replay-refusal-20261008 branch October 8, 2026 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant