docs: document involvement gate design#950
Merged
Merged
Conversation
Adds a dedicated Involvement Gate section to docs/messaging.md explaining: - Design principle (humans are gatekeepers) - How a bot becomes involved (thread owner or has participated) - Gate evaluation order (ASCII flow diagram) - Why bot-to-bot cannot break the gate (resource control, human authority, loop prevention) - Practical impact table - Workarounds for bot-to-bot handoff Updates docs/discord.md Multi-Bot Setup > Known limitations: - Expands thread ownership bullet into full Involvement Gate subsection - Adds ASCII example showing the drop/pass behavior - Cross-references messaging.md for full details Addresses confusion raised in #949 where the involvement gate behavior was not documented, leading users to believe bot-to-bot @mention drops were a bug rather than an intentional design constraint. Refs #949
|
All PRs must reference a prior Discord discussion to ensure community alignment before implementation. Please edit the PR description to include a link like: This PR will be automatically closed in 3 days if the link is not added. |
thepagent
approved these changes
May 29, 2026
This was referenced May 31, 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.
Summary
Documents the involvement gate — the pre-dispatch check that prevents bots from processing messages in threads they haven't joined yet.
This addresses confusion raised in #949 where the behavior was not documented, leading users to believe bot-to-bot @mention drops were a bug rather than an intentional design constraint.
Changes
docs/messaging.md
docs/discord.md
Known limitations > Thread ownershipbullet into a full Involvement Gate subsectionContext
The involvement gate is an intentional safety constraint:
allow_bot_messagessettingsRefs #949