Repository navigation
A service may let a holder forget content it sent or was told: the envelope stays on every read path, and the completing event names what stays - #115
Closed
riccardone wants to merge 1 commit into
Closed
riccardone wants to merge 1 commit into
riccardone wants to merge 1 commit into
Conversation
…velope stays on every read path, and the completing event names what stays Entry 46 of #37. Commands are facts and the event log is the record, and nothing says how a holder removes content it sent or got, or what a service keeps. best-peer's forget removes a holder's prompts and answers and keeps each event's envelope on the page, the stream, a replay and after a restart; Forgotten names what was removed and what was kept. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
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.
Entry 46 on #37 (#37), proven by best-peer.
Why
The spec has commands as facts and an event log as the record. Nothing says how a holder removes content it sent or was told, or what a service keeps when it does, though a person may need their words gone. best-peer's
forgetnames one prompt's correlation, a deployment's prompts or those before a time; each matching event loses its content (the messages, the answer, the engine's words) and keeps its id, type, time and correlation, with the counts the meter reads, markedforgotten. The log is rewritten in place, so a page, a replay withLast-Event-IDand a restart all serve the envelope without the content, andForgottenlists what was removed and what was kept. On a workspace, each member that answered is asked to forget its own copy.What
Events gains Forgetting Content: a service may offer it; a forgotten event keeps its envelope on every read path; the completing event names what was removed and what was kept.
Nothing changes in the conformance list: the sentence is a clarification.
No version bump and no release notes here: the PRs from #37 do not collide that way, and the release that gathers them does both.
🤖 Generated with Claude Code