When someone creates or assigns a work item in a shared namespace, the other person has no way to know without leaving WCP (e.g., checking Slack). The signal should stay in the system.
- Every WCP user gets a persistent inbox — a stream of activity from shared namespaces and assignments
- Entries get delivered automatically on your next MCP tool call. Claude sees them and says something like: "Emerson created ATLAS-26 for you and commented on ATLAS-14. Want me to pull either up?"
- Entries are delivered once (won't repeat on every tool call), but they're always searchable via a new
wcp_inboxtool - "What did Emerson do today?" / "What's new in ATLAS?" / "Show me everything unread" — all just natural language queries
| Event | Who gets notified |
|---|---|
| Item created in shared namespace | All other namespace members |
| Item assigned to you | The assignee |
| Comment on an item you created or are assigned to | All involved parties (except commenter) |
| Status change on an item you're involved with | All involved parties (except actor) |
Your own actions never generate entries for yourself.
The Slack messages that are really just about work coordination — "hey can you look at PROJ-12", "I updated the spec", "FYI I'm blocked." Those messages are about work items that already exist in WCP. They should travel through WCP, not Slack.
What stays in Slack: real conversation, brainstorming, social stuff, anything synchronous.
Gameplan is approved, ready to build. Would love to hear if this matches pain you're feeling — or if there are notification types that would matter most to you.