Repository navigation
feat(wal): attest committed source closures - #423
Merged
Merged
Conversation
40 of 47 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A catalog closure permit authorizes releasing a source pin but does not prove the source committed that closure. Add
Query::ClosedProof, issued after a safe source ReadIndex, so a consumer can verify the exact persisted closure, source cut and original catalog permit. Optional per-group Ed25519 keys keep the catalog private key off source-only replicas; missing signers are rejected before reserving read capacity.Empty source-key configurations preserve the existing policy identity. Enabling or changing keys requires an explicit policy migration. This increment provides the attestations; catalog checkpoint advancement and physical reclamation remain separate work.
Refs #378.
Testing