Skip to content

docs: document involvement gate design#950

Merged
thepagent merged 1 commit into
mainfrom
docs/involvement-gate
May 29, 2026
Merged

docs: document involvement gate design#950
thepagent merged 1 commit into
mainfrom
docs/involvement-gate

Conversation

@chaodu-agent
Copy link
Copy Markdown
Collaborator

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

  • Adds a dedicated Involvement Gate section after the Quick Reference
  • Explains the design principle (humans are gatekeepers)
  • Documents how a bot becomes involved (thread owner or has participated)
  • Provides gate evaluation order as an ASCII flow diagram
  • Explains why bot-to-bot cannot break the gate (resource control, human authority, loop prevention)
  • Includes practical impact table and workarounds

docs/discord.md

  • Expands the Known limitations > Thread ownership bullet into a full Involvement Gate subsection
  • Adds ASCII example showing the drop/pass behavior
  • Cross-references messaging.md for full details

Context

The involvement gate is an intentional safety constraint:

  • Only humans can pull a bot into a thread (via @mention)
  • Bot-to-bot @mention of a non-involved bot is silently dropped
  • Once a bot is involved (has replied), bot-to-bot communication works per allow_bot_messages settings

Refs #949

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
@chaodu-agent chaodu-agent requested a review from thepagent as a code owner May 29, 2026 22:40
@github-actions
Copy link
Copy Markdown

⚠️ This PR is missing a Discord Discussion URL in the body.

All PRs must reference a prior Discord discussion to ensure community alignment before implementation.

Please edit the PR description to include a link like:

Discord Discussion URL: https://discord.com/channels/...

This PR will be automatically closed in 3 days if the link is not added.

@github-actions github-actions Bot added the closing-soon PR missing Discord Discussion URL — will auto-close in 3 days label May 29, 2026
@github-actions github-actions Bot added pending-maintainer and removed closing-soon PR missing Discord Discussion URL — will auto-close in 3 days labels May 29, 2026
@thepagent thepagent merged commit 7ab6fc4 into main May 29, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants