feat(manager-server): add verifiable usage snapshot protocol - #456
Closed
bc19sam-afk wants to merge 2 commits into
Closed
feat(manager-server): add verifiable usage snapshot protocol#456bc19sam-afk wants to merge 2 commits into
bc19sam-afk wants to merge 2 commits into
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
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\n\n- add a versioned, machine-verifiable usage snapshot protocol\n- freeze membership at a SQLite event-id high-water mark\n- provide authenticated expiring cursors, row count, digest, and stable event IDs\n- preserve existing v0 usage and export clients\n\n## Current status\n\nDraft implementation in progress. The first commits contain RED contract tests for:\n- more than 50,000 rows\n- stable pagination and concurrent inserts\n- same-shaped distinct events\n- replay, cursor tampering, expiry, and snapshot drift\n- authorization and v0 compatibility\n\n## Safety boundaries\n\n- no deployment or production access\n- no real credentials or user data\n- no changes to the downstream consumer repository\n- do not merge while Draft\n\n## Verification\n\nPending implementation and GREEN/full-suite evidence.\n