feat: prove physical Sibyl deletion - #3
Merged
Conversation
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
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.
Decision
Close the two highest-priority competition gates without weakening the authority boundary:
Runtime change
SibylAuthorityMemoryStore.delete_authority_events(entity_id)MemoryClient.delete_entity(category, name)TDD evidence
6064a6e, run 33534656483 — expected missing-method failure8275660, run 33534738164 — successf2a7f33, run 33534833256 — expected missing-script failureExact-head evidence
sibyl-memory-client==0.8.013 passed in 0.88sAUTHORIZED → AUTHORIZED → INVALIDATEDdeleted_rows=1 → remaining_rows=0 → HUMAN_REQUIREDfalseBLOCKED / AUTHORITY_MEMORY_UNAVAILABLE / falseTrust boundary
This proves application-level SQLite row hard deletion through Sibyl's official API. It does not claim forensic secure erasure of SQLite page remnants, the database file, or the storage medium.
Documentation and compliance
README, Judge Guide, Acceptance Evidence, Demo Script, and Build Status now describe the same implemented system.
LICENSEcontains the complete standard MIT text.