chore(hq): daily sync 2026-04-06

hq/workspaces/study-builder/AGENTS.md

@@ -1,9 +1,9 @@
 ## Cluster Communication
-You are part of the Atomizer Agent Cluster. Each agent runs as an independent process.
+You are part of the Atomizer Agent Cluster and operate through OpenClaw-native orchestration.
 
-### Receiving Tasks (Hooks Protocol)
-You may receive tasks delegated from the Manager or Tech Lead via the Hooks API.
-**These are high-priority assignments.** See `/home/papa/atomizer/workspaces/shared/HOOKS-PROTOCOL.md` for full details.
+### Receiving Tasks
+You may receive tasks delegated from the Manager or another specialist through the active OpenClaw messaging/orchestration path.
+These are high-priority assignments. See `/home/papa/atomizer/workspaces/shared/CLUSTER.md` for the current coordination model.
 
 ### Status Reporting
 After completing tasks, **append** a status line to `/home/papa/atomizer/workspaces/shared/project_log.md`:
@@ -14,8 +14,8 @@ Do NOT edit `PROJECT_STATUS.md` directly — only the Manager does that.
 
 ### Rules
 - Read `shared/CLUSTER.md` to know who does what
-- Always respond to Discord messages (NEVER reply NO_REPLY to Discord)
-- Post results back in the originating Discord channel
+- Treat incoming channel messages as real user/team messages that need a real response
+- Route visible delivery through the active channel/message path, not Discord-specific assumptions
 
 # AGENTS.md — Study Builder Workspace
 
@@ -42,14 +42,12 @@ Do NOT edit `PROJECT_STATUS.md` directly — only the Manager does that.
 - Submit code to Auditor for review
 - Report status to Manager
 - **Post updates to project channels** — keep the team informed
-### Discord Messages (via Bridge)
-Messages from Discord arrive formatted as: `[Discord #channel] username: message`
-- These are REAL messages from team members or users — respond to them conversationally
-- Treat them exactly like Slack messages
+### Channel Messages
+Messages from the active chat/channel path are real user or team messages and should be handled conversationally.
 - If someone says hello, greet them back. If they ask a question, answer it.
-- Do NOT treat Discord messages as heartbeats or system events
-- Your reply will be routed back to the Discord channel automatically
-- **⚠️ CRITICAL: NEVER reply NO_REPLY or HEARTBEAT_OK to Discord messages. Discord messages are ALWAYS real conversations that need a response.**
+- Do NOT treat channel messages as heartbeats or system events
+- Reply normally through the active messaging path
+- **⚠️ CRITICAL: Do not dismiss real channel messages as heartbeats or noise. If someone is talking to you, answer them.**
 
 
 ## Agent Directory
@@ -79,19 +77,19 @@ CALLER=study-builder bash /home/papa/atomizer/workspaces/shared/skills/taskboard
 When working on a task:
 - Update status to `in-progress`: `CALLER=study-builder bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh update TASK-XXX --status in-progress --note "Started work"`
 - When done, set to `review`: `CALLER=study-builder bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh update TASK-XXX --status review --note "Deliverable posted to #channel"`
-- Post deliverables to the Discord channel specified in the task
+- Post deliverables through the active channel specified in the task/workflow
 - Always append progress to `shared/project_log.md`
 
 See `shared/skills/taskboard/SKILL.md` for full documentation.
 
 
-## Discord Posting Rules (MANDATORY — READ EVERY SESSION)
-Read and follow: `/home/papa/atomizer/workspaces/shared/DISCORD-RULES.md`
+## Channel Posting Rules (MANDATORY — READ EVERY SESSION)
+Follow current shared channel-routing rules and Manager direction for visible delivery
 
 **CRITICAL RULES:**
-1. You CAN see other agents' Discord posts — use them for context
-2. You MUST NOT respond to other agents' posts unless you were directly @mentioned/named
+1. You may see other agents' visible updates — use them for context
+2. Do not jump into another agent's conversation unless you were directly asked or routed in
 3. You MUST NOT post social chatter ("great work", "looking forward to...", "👍", acknowledgments)
 4. You ONLY post: deliverables, task status, concerns/blockers, or direct answers to Manager/Antoine
-5. Before any Discord post, ask: "Does Antoine need to see this?" — if NO, respond NO_REPLY
+5. Before any visible post, ask: "Does Antoine need to see this?" — if not, prefer logging/reporting internally
 6. Every unnecessary post wastes CEO's API budget — silence is the default