From 4fe8a8b0e0b38e1709338d1e242d6a5caf2da03d Mon Sep 17 00:00:00 2001 From: Logan Johnson Date: Mon, 9 Nov 2026 12:54:03 -0500 Subject: [PATCH 1/2] docs: point agent policy work at the information flow vision block/buzz VISION_INFORMATION_FLOW.md now owns the rules for adding agents to channels, agent roles, DMs that include agents and agent publishing. Tell agents to read it before planning such changes, and mark the broker paper and the ifc crates as the alternative considered. Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz> Co-Authored-By: Claude Opus 5.5 Signed-off-by: Logan Johnson --- AGENTS.md | 4 ++++ docs/ifc.md | 2 ++ docs/practical-information-flow-for-buzz-agents.md | 2 ++ 3 files changed, 8 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index c9acee2d6e..7c671c2382 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -99,6 +99,10 @@ 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, or what an agent publishes, 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 diff --git a/docs/ifc.md b/docs/ifc.md index 36367110c8..3ec990ab33 100644 --- a/docs/ifc.md +++ b/docs/ifc.md @@ -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). diff --git a/docs/practical-information-flow-for-buzz-agents.md b/docs/practical-information-flow-for-buzz-agents.md index 96522ab326..1880a6beab 100644 --- a/docs/practical-information-flow-for-buzz-agents.md +++ b/docs/practical-information-flow-for-buzz-agents.md @@ -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 From 4ceceafaaa47c18ede462f446eba37f2741256fd Mon Sep 17 00:00:00 2001 From: Logan Johnson Date: Mon, 9 Nov 2026 17:12:25 -0500 Subject: [PATCH 2/2] docs: point visibility and owner-authority work at the vision too Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz> Co-Authored-By: Claude Opus 5.5 Signed-off-by: Logan Johnson --- AGENTS.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 7c671c2382..4e4d36fbbf 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -100,8 +100,9 @@ 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, or what an agent publishes, read -block/buzz's [`VISION_INFORMATION_FLOW.md`](https://github.com/block/buzz/blob/main/VISION_INFORMATION_FLOW.md) and follow it. +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