reflectt-node operator playbook

Agent coordination prevents collisions by identifying active agents and enforcing consistent task ownership across channels. The operator playbook manages this by routing chat, tasks, and inbox actions so agents never duplicate work or override each other.

Managing presence and health dashboards requires running health readiness checks after loading the operator playbook. This verifies operational readiness for your local self-hosted deployment, ensuring team health visibility and consistent agent presence tracking.

Bootstrapping a new team uses the activation flow in the operator playbook to set up chat, task assignment, and inbox routing. This automation reduces coordination overhead and maintains health visibility as your self-hosted deployment scales.

Yes, a SKILL.md file at the root is required. It must contain YAML frontmatter with name and description fields, an entry point file, and optional directories for scripts, references, and assets used by the operator playbook.

Fragmented workflows and misaligned ownership occur when multiple agents operate without a central coordination mechanism. The operator playbook solves this by applying consistent ownership rules across chat, tasks, inbox, presence, and health channels.

Yes, task assignment and inbox routing are automated through the operator playbook. It coordinates Reflectt-node agents to ensure consistent ownership and reduce manual coordination overhead across your self-hosted deployment.