Skip to content

Update docs for coordinator drop and Slack/Teams direct messages#68

Open
playerzero-ai[bot] wants to merge 1 commit into
mainfrom
drop-coordinator-docs-updates
Open

Update docs for coordinator drop and Slack/Teams direct messages#68
playerzero-ai[bot] wants to merge 1 commit into
mainfrom
drop-coordinator-docs-updates

Conversation

@playerzero-ai

@playerzero-ai playerzero-ai Bot commented Jul 19, 2026

Copy link
Copy Markdown
Contributor

Retires the "Coordinator" entity from customer-facing concept pages and documents the July 2026 Channel & Workflow UX drop (Slack/Teams).

Changes

  • connector/slack.mdx — new direct-question DM capability bullet; Workflow Stage Approvals now covers the already-handled state; new Send direct messages toggle + scope under Notification Configuration.
  • connector/microsoft-teams.mdx — same treatment (What You Can Do + Receive Notifications extended; already-handled note; Send direct messages block).
  • features/workflows.mdx — light touch: names the controlling thread; relates valid next steps to the sidebar Possible next stages. Approvals config + Workflow Inbox untouched.
  • features/ai-player.mdx — Coordinator bullet -> controlling-thread wording; thread-to-thread messaging bullet no longer attributes relay to a coordinator (capability preserved).
  • how-playerzero-works.mdx — Coordinator bullet -> controlling-thread wording.
  • features/hive-mode.mdx — single coordinator sentence rephrased.

Scope notes

  • Workflow Inbox docs intentionally left out (separate later pass).
  • Collaboration concept uses "Collaboration question" / "Direct question", never "escalation".
  • Follow-up (not in this PR): the Documentation Style Guide canonical-nouns list still lists "Coordinator" and should be updated to match the retired entity.

@jblase @playerzero-agent
Update docs for coordinator drop and Slack/Teams direct messages
2dbcf77 
Retire the "Coordinator" entity from customer-facing concept pages,
replacing it with the controlling-thread model, while preserving
thread-to-thread context sharing. Document the reworked Slack/Teams
stage-approval messaging (already-handled state) and the new per-project
Send direct messages toggle and scope.

Co-authored-by: PlayerZero <player@playerzero.ai>
@playerzero-ai
playerzero-ai Bot requested a review from Klasens July 19, 2026 21:07
@mintlify

mintlify Bot commented Jul 19, 2026 •
edited
Loading

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
player-zero 🟢 Ready View Preview Jul 19, 2026, 9:08 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@playerzero-ai

playerzero-ai Bot commented Jul 19, 2026

Copy link
Copy Markdown
Contributor Author

For reference, this PR came out of the following PlayerZero thread (research, drafting, and review context): https://playerzero.ai/pz/pzdocs/player/6a5d365902e8da64a27692e5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Klasens Klasens Awaiting requested review from Klasens

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jblase