Conversation
A stream with an id and no owner gets its own keys: a hash for the policy and the seal, and a log per topic. One append script reads the policy, refuses a sealed stream, and trims by count, age and a per-topic byte total.
The Redis case now declares that it hosts standalone streams, bounds their bytes and trims an open stream by age, so the conformance suite holds it to all three.
This was referenced Oct 3, 2026
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.
This PR hosts standalone streams, streams with an id and no owner, on the Redis provider.
What changed?
create_standalone_stream()writes a policy hash once and refuses a different policy for the same id.get_standalone_stream_handle()reaches it, and the handle'sclose()seals it.Part of AI-198 (epic AI-37).
Why?
The interface lets a client create a stream nobody owns, with a retention policy, and seal it on purpose. Redis has no byte trim of its own. So each entry carries the size the policy counts, and the hash keeps a running total per topic.
How did you test it?
Link to a test plan if any -
poe lintis clean. The streams suite withSTREAMS_LIVE=redis, now including the standalone conformance cases, passes against a channel server and a local Redis.