Skip to content

docs: point agent policy work at the information flow vision #3118

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
loganj wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

docs: point agent policy work at the information flow vision #3118

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4fe8a8b
docs: point agent policy work at the information flow vision
loganj Nov 9, 2026
4ceceaf
docs: point visibility and owner-authority work at the vision too
loganj Nov 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,11 @@ callers, and relevant design docs; preserve documented product decisions and
ownership boundaries. Resolve answerable questions from evidence; ask before
deviating from agreed scope or product behavior.

Before planning a change to who can add an agent to a channel, an agent's
channel role, DMs that include an agent, what an agent publishes, channel
visibility or admission rules, or tools that let an agent act with its owner's
authority, read block/buzz's [`VISION_INFORMATION_FLOW.md`](https://github.com/block/buzz/blob/main/VISION_INFORMATION_FLOW.md) and follow it.

For cross-host changes, follow [shared logic and host boundaries](docs/contributing.md#shared-logic-and-host-boundaries).
Name the existing feature owner/current callers, preserved behavior or approved
host differences, and which host the validation actually exercises. Keep shared
Expand Down
2 changes: 2 additions & 0 deletions docs/ifc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# Information-flow control

> **Status:** these crates implement the broker design, an alternative considered. Buzz follows the channel-based design in block/buzz's [`VISION_INFORMATION_FLOW.md`](https://github.com/block/buzz/blob/main/VISION_INFORMATION_FLOW.md) instead.

The policy library is ported from `block/buzz` at
`c94c7128dd6c5cf12486cad0ed767b4ac21ca56a` (PR #8226).

Expand Down
2 changes: 2 additions & 0 deletions docs/practical-information-flow-for-buzz-agents.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# Practical information-flow for Buzz agents

> **Status:** alternative considered. Buzz follows the channel-based design in block/buzz's [`VISION_INFORMATION_FLOW.md`](https://github.com/block/buzz/blob/main/VISION_INFORMATION_FLOW.md) instead.

Author: Jordan Mecom

Draft
Expand Down
Loading