[loganj]

Summary

Adds VISION_INFORMATION_FLOW.md: how an agent's owner controls where information flows through the agent, using the access control Buzz already has, channel membership and roles. The AGENTS.md Product Contract makes agents read the relevant VISION_*.md before planning, so changes to agent adds, roles, DMs or agent publishing will be checked against it.

The document covers:

• the model: W (the channels the agent reads) and R (everyone who can read where the agent writes);
• the paths where the owner loses control today, checked against main at 658253009;
• a restricted disclosure level, chosen by the owner, that closes those paths in the relay, plus one rule for every channel: no private-to-open changes; public and personal are described as possible further disclosure levels;
• what this does not stop, alternatives considered, risks, and a rollout where each step only refuses actions.

It describes direction. It changes no wire format and no behavior; the wire formats for the disclosure level and the profile approval tag are left to the NIPs that own agent identity, when they are built.

Also:

• VISION.md: one line in Access that links the new document.
• docs/practical-information-flow-for-buzz-agents.md: a status line that marks the broker design as an alternative considered.
• NOSTR.md: corrects the kind 9000 row. It said only owners and admins may add people to a private channel; any member who can post may (decide_member_put in crates/buzz-core/src/channel.rs, and the "plain member may still add an ordinary member to a private channel" case in channel_authz.rs tests).

Related issue

None found. Related: #7293 added the broker paper and ifc-core; #8143 added announce channels (guests are read-only), which this design builds on.

Testing

Documentation only. Checked relative links and section anchors in the new document, and checked each claim about current behavior against the code at 658253009.

🤖 Generated with Claude Code