Add broker-facing IFC sessions - #7497
Open
jmecom wants to merge 3 commits into
Open
Conversation
Signed-off-by: Jordan Mecom <jm@squareup.com>
Signed-off-by: Jordan Mecom <jm@squareup.com>
Signed-off-by: Jordan Mecom <jm@squareup.com>
jmecom
force-pushed
the
jm/buzz-ifc-domain
branch
from
September 11, 2026 18:10
c5f565b to
11e7ff9
Compare
jmecom
force-pushed
the
jm/buzz-ifc-session-api
branch
from
September 11, 2026 18:10
5070cb5 to
fe75084
Compare
jmecom
marked this pull request as ready for review
September 11, 2026 18:10
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.
Adds
IfcSessionover the Buzz execution domains in #7349. The broker checks reads withread(resource), non-publishing operations withcall(operation), and publications withpublish(operation, destination, bytes).A publication authorization owns the operation, destination label, and serialized request. The sink receives those checked bytes, so an agent cannot change the request while it waits to be sent. Reads validate the audience, retained-state context, and membership epoch; they do not change the session's audience restrictions.
The broker keeps the IFC session for as long as it retains the agent's history or files. The example reuses sessions by domain key, and tests cover unknown-input restrictions surviving reuse, owner-private state staying out of ordinary conversations, and reads staying within one community.
This is library-only. The broker must authenticate facts, check current membership and destination policy, isolate retained state, and execute the complete request that was authorized. Integrity tracking, declassification, and runtime integration are not included.
Stack: #7293 (merged) → #7349 → this PR. Both open branches are rebased onto
mainat44c1cc7df.Checked: formatting, strict Clippy, documentation with warnings denied, 31 unit tests and 7 doctests across
buzz-ifcandifc-core, including frozen-request and compile-fail regressions.