This repository was archived by the owner on Mar 26, 2026. It is now read-only.
spec(collab): second revision pass on CollaborationProtocol#297
Open
spec(collab): second revision pass on CollaborationProtocol#297
Conversation
…-setup.sh Aligns scripts with CLAUDE.md docs (PR #290). MCP server name changed from boss-dev to odis-dev in the generated JSON config, allowed tools list, and output messages. BOSS_API_TOKEN/BOSS_MCP_URL env vars kept as fallbacks for backward compatibility (prefer ODIS_API_TOKEN/ODIS_MCP_URL going forward). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…our Conversations Root cause: both 'boss' (legacy) and 'operator' agents have agent_type='human' in the DB. operatorName computed returned whichever was found first via Object.entries, which is insertion-order. In spaces where 'boss' was created first, operatorName='boss'. Consequences when operatorName='boss' but messages use 'operator': - Conversations with 'operator' participant went to Agent Conversations section - composeRecipient was null for those conversations (no compose box shown) - Unread acks used wrong agent name Fix: collect ALL human agents into humanAgentNames Set. Use it for: - isOperatorConversation: any participant that is a human agent - composeRecipient: any participant that is NOT a human agent - unreadCount / ackOperatorMessages: any human-agent recipient - operatorName: prefer 'operator' (canonical) over legacy 'boss' Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…tion threads When agents use different capitalizations (e.g. "CEO" vs "ceo"), messages were stored with the raw sender name, creating separate conversation threads in the UI for what should be a single conversation. Both handleAgentMessage (HTTP) and send_message (MCP tool) now call resolveAgentName on the sender after the space is loaded, mapping to the canonical stored name if the sender is a known agent. Unknown senders keep their original name unchanged. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Address remaining boss feedback after PR #134 (CLOSED): - Remove [?BOSS] tag syntax from docs/AGENT_PROTOCOL.md questions field example and description; replace with plain language - Replace wall-clock status cadence with milestone-based language in AGENT_PROTOCOL.md (Pattern A work loop + non-tmux checklist) - messaging-protocol.md: remove 'manager can explicitly forbid' qualifier from peer-to-peer section; peer messaging is always allowed, no authorization needed - messaging-protocol.md: reframe escalation to walk up the chain rather than hardcoding a 'boss' message target with 30-minute wall-time rule - organizational-model.md: remove 'manager can restrict' qualifier from information-flow principle; direct messaging is always allowed - ignition-prompts.md: remove 'boss agent channel for boss-level decisions' from hierarchy section; add blocked task status to blocker flow - ignition-prompts.md: soften org chart note — position set by spawning agent, not a warning about org instability - team-formation.md: remove time-based threshold (~30 min); replace with action-based criteria (multiple focused actions = non-trivial); strengthen the default-to-team recommendation Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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
Second revision of CollaborationProtocol spec docs addressing boss feedback on TASK-061. This supersedes CLOSED PR #134.
docs/AGENT_PROTOCOL.md[?BOSS]tag syntax fromquestionsfield example and description.spec/CollaborationProtocol/messaging-protocol.mdbossmessage target with wall-time rule.spec/CollaborationProtocol/organizational-model.md.spec/CollaborationProtocol/ignition-prompts.md.spec/CollaborationProtocol/team-formation.mdBoss feedback addressed
[?BOSS]/[?MANAGER]tag antipattern removed from all agent-facing spec docsblockedtask status explicitly mentioned in the blocker flowTest plan
[?BOSS]or[?MANAGER]tags remain in any spec or protocol doc🤖 Generated with Claude Code