Antoine/Atomizer
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(hq): daily sync 2026-03-28

Browse Source
This commit is contained in:
Antoine
2026-03-28 09:00:40 +00:00
parent 540d97a7e1
commit 4341215af2
6 changed files with 78 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files

62
hq/workspaces/shared/CLUSTER.md
View File

@@ -15,56 +15,32 @@
## Inter-Agent Communication
Each agent runs as an independent OpenClaw gateway. To send a message to another agent:
Use **OpenClaw native orchestration**, not legacy hooks/curl patterns.
```bash
curl -s -X POST http://127.0.0.1:PORT/hooks/agent \
-H "Content-Type: application/json" \
-H "Authorization: Bearer 31422bb39bc9e7a4d34f789d8a7cbc582dece8dd170dadd1" \
-d '{"message": "your message", "agentId": "AGENT_ID"}'
```
### Primary methods
- `sessions_spawn` — delegate substantial work to a specialist
- `sessions_send` — steer or clarify an active session
- `subagents(action=list)` — check status only when needed
### Examples
### Messaging / delivery
- Use the `message` tool for visible updates to Slack or other configured channels
- Keep specialist-to-specialist coordination internal unless Antoine needs to see it
- Manager is responsible for visible orchestration summaries in the originating channel/thread
```bash
# Report to manager
curl -s -X POST http://127.0.0.1:18800/hooks/agent \
-H "Content-Type: application/json" \
-H "Authorization: Bearer 31422bb39bc9e7a4d34f789d8a7cbc582dece8dd170dadd1" \
-d '{"message": "Status update: FEA analysis complete", "agentId": "manager"}'
## Channel Ownership
# Delegate to tech-lead
curl -s -X POST http://127.0.0.1:18804/hooks/agent \
-H "Content-Type: application/json" \
-H "Authorization: Bearer 31422bb39bc9e7a4d34f789d8a7cbc582dece8dd170dadd1" \
-d '{"message": "Please review the beam optimization study", "agentId": "technical-lead"}'
# Ask webster for research
curl -s -X POST http://127.0.0.1:18828/hooks/agent \
-H "Content-Type: application/json" \
-H "Authorization: Bearer 31422bb39bc9e7a4d34f789d8a7cbc582dece8dd170dadd1" \
-d '{"message": "Find papers on topology optimization", "agentId": "webster"}'
```
## Discord Channel Ownership
- **Manager**: #ceo-office, #announcements, #daily-standup, #active-projects, #agent-logs, #inter-agent, #general, #hydrotech-beam
- **Tech Lead**: #technical, #code-review, #fea-analysis
- **Secretary**: #task-board, #meeting-notes, #reports, #knowledge-base, #lessons-learned, #it-ops
- **NX Expert**: #nx-cad
- **Webster**: #literature, #materials-data
- **Auditor, Optimizer, Study Builder**: DM + hooks (no dedicated channels)
## Slack (Manager only)
Manager also handles Slack channels: #all-atomizer-hq, #secretary, etc.
Current operational home channels:
- **Manager**: `#hq`, `#all-atomizer-hq`, `#agent-ops`, `#social`
- **Secretary**: `#secretary`, `#reports`
- **Technical Lead**: `#technical-lead`
- **Shared specialist summon channel**: `#all-atomizer-hq` via @mentions / routing rules
## Rules
1. Always respond to Discord messages — NEVER reply NO_REPLY
2. When delegating, be specific about what you need
3. Post results back in the originating Discord channel
4. Use hooks API for inter-agent communication
1. Use native OpenClaw tools for inter-agent communication
2. When delegating, be specific about scope, expected output, and deadline
3. Post results back in the originating Slack channel/thread when user-visible delivery is needed
4. Do not rely on legacy Discord bridge assumptions unless a task explicitly targets a Discord environment
## Response Arbitration (Anti-Collision)

4
hq/workspaces/shared/skills/taskboard/SKILL.md
View File

@@ -24,7 +24,7 @@ CALLER=my-agent-name bash "$TB" update TASK-001 --status review --note "Draft po
# Kanban summary (counts per column)
bash "$TB" summary
# Kanban snapshot (markdown for Discord)
# Kanban snapshot (markdown)
bash "$TB" snapshot
```
@@ -61,7 +61,7 @@ backlog → todo → in-progress → review → done
On every session start:
1. Check your tasks: `CALLER=<you> bash "$TB" list --agent <you>`
2. If you have `todo` tasks: update to `in-progress` and start working
3. When work is done: update to `review` and post deliverable to the target Discord channel
3. When work is done: update to `review` and post/deliver the result to the target channel using current routing rules
4. Append progress to `shared/project_log.md`
## Important