Extract reusable IFC policy and classify worker placement - #6275
Draft
jmecom wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Jordan Mecom <jm@squareup.com>
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.
Extracts the deterministic label, domain, capability, publication, declassification, and process-reuse rules from
buzz-acpinto the zero-I/Obuzz-ifccrate. The ACP harness remains responsible for verifying Buzz events and membership and for acting on the resulting policy decisions.This layer also makes worker placement explicit. Public channels in one community use
shared_publicand may reuse the same public-bound pool. Restricted channels, DMs, group DMs, and owner-private work usedomain_confinedand require an exact domain match. The experimental enforcement mode is namedroute;isolateremains accepted as a compatibility alias.The behavior remains off by default.
domain_confinedis a placement requirement for a future launcher or sandbox, not a claim that this PR provides OS confinement.Testing:
cargo test -p buzz-ifc -p buzz-acp(828 tests)cargo clippy -p buzz-ifc -p buzz-acp --all-targets -- -D warningsStack: