Expose IFC policy to external agent harnesses - #6176
Draft
jmecom wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Jordan Mecom <jm@squareup.com>
jmecom
force-pushed
the
jm/acp-audience-broker-poc
branch
from
August 18, 2026 23:57
809c039 to
8944041
Compare
This was referenced Aug 18, 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
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
buzz-ifc-broker, a bounded JSON-RPC process that exposes the sharedbuzz-ifcrules to non-Rust agent harnesses such as kgoose. It supports domain derivation, worker entry and retirement, input observation, call checks, publication checks, and structured decision logging over stdio.The executable is the policy process inside a larger trusted gateway, not the complete Buzz broker. Its caller must still verify signed events and authoritative membership, control worker lifecycle and publication, and provide any required credential or OS confinement.
The protocol includes bounded request frames, stable error responses, a golden domain fixture, and stdio conformance coverage. This commit adds no new enforcement to
buzz-acp; it exposes the policy already established by the lower layers.Testing:
cargo test -p buzz-ifc -p buzz-ifc-broker -p buzz-acp(835 tests)cargo clippy -p buzz-ifc -p buzz-ifc-broker -p buzz-acp --all-targets -- -D warningsjust cipassed.Stack: