chore(hq): daily sync 2026-04-06
This commit is contained in:
@@ -2,8 +2,8 @@
|
||||
"tasks": [
|
||||
{
|
||||
"id": "guide_onboarding",
|
||||
"title": "🏭 Atomizer HQ — Mission Control",
|
||||
"description": "Self-hosted dashboard at http://100.68.144.33:8091\n\nAgents update tasks by writing to ~/atomizer/mission-control/data/tasks.json.\nNo GitHub tokens needed — everything is local.\n\nManaged by: Manager agent\nBacked up to: Gitea (Atomizer-HQ repo)",
|
||||
"title": "\ud83c\udfed Atomizer HQ \u2014 Mission Control",
|
||||
"description": "Self-hosted dashboard at http://100.68.144.33:8091\n\nAgents update tasks by writing to ~/atomizer/mission-control/data/tasks.json.\nNo GitHub tokens needed \u2014 everything is local.\n\nManaged by: Manager agent\nBacked up to: Gitea (Atomizer-HQ repo)",
|
||||
"status": "permanent",
|
||||
"project": "meta",
|
||||
"tags": [
|
||||
@@ -13,7 +13,7 @@
|
||||
"subtasks": [
|
||||
{
|
||||
"id": "sub_001",
|
||||
"title": "Dashboard is live and accessible ✅",
|
||||
"title": "Dashboard is live and accessible \u2705",
|
||||
"done": true
|
||||
},
|
||||
{
|
||||
@@ -32,8 +32,8 @@
|
||||
},
|
||||
{
|
||||
"id": "ATZ-001",
|
||||
"title": "🧪 Test Orchestration: Material Trade Study Mini-Project",
|
||||
"description": "End-to-end test of the Atomizer HQ orchestration pipeline.\n\n**Objective:** Compare two candidate materials for a hypothetical lightweight bracket:\n- 7075-T6 Aluminum\n- Ti-6Al-4V Titanium\n\n**Criteria:** Strength-to-weight, cost, machinability, fatigue life\n\n**Expected workflow:**\n1. Manager receives this task\n2. Manager spawns Webster → research material properties\n3. Manager spawns Tech Lead → evaluate trade-offs\n4. Manager spawns Auditor → review the evaluation\n5. Manager spawns Secretary → write summary to #reports\n\nThis is a TEST to validate the orchestration pipeline works end-to-end.",
|
||||
"title": "\ud83e\uddea Test Orchestration: Material Trade Study Mini-Project",
|
||||
"description": "End-to-end test of the Atomizer HQ orchestration pipeline.\n\n**Objective:** Compare two candidate materials for a hypothetical lightweight bracket:\n- 7075-T6 Aluminum\n- Ti-6Al-4V Titanium\n\n**Criteria:** Strength-to-weight, cost, machinability, fatigue life\n\n**Expected workflow:**\n1. Manager receives this task\n2. Manager spawns Webster \u2192 research material properties\n3. Manager spawns Tech Lead \u2192 evaluate trade-offs\n4. Manager spawns Auditor \u2192 review the evaluation\n5. Manager spawns Secretary \u2192 write summary to #reports\n\nThis is a TEST to validate the orchestration pipeline works end-to-end.",
|
||||
"status": "backlog",
|
||||
"project": "test",
|
||||
"tags": [
|
||||
@@ -75,7 +75,7 @@
|
||||
},
|
||||
{
|
||||
"id": "ATZ-749aac",
|
||||
"title": "📋 Standardization Review — Project Structure & Protocols",
|
||||
"title": "\ud83d\udccb Standardization Review \u2014 Project Structure & Protocols",
|
||||
"description": "Review and standardize all agent project structures, communication protocols, and deliverable formats.\\n\\nThis was discussed and reviewed but never tracked on the dashboard.\\n\\nScope:\\n- Agent workspace structure standards\\n- Task lifecycle protocol\\n- Deliverable schema enforcement\\n- Communication routing rules",
|
||||
"status": "review",
|
||||
"project": "standards",
|
||||
@@ -87,8 +87,8 @@
|
||||
},
|
||||
{
|
||||
"id": "ATZ-2f1634",
|
||||
"title": "🔧 P-Adaptive-Isogrid — Plate Lightweighting Tool",
|
||||
"description": "Automated plate lightweighting via isogrid pattern optimization.\\n\\nArchitecture: Python Brain + NX Hands + Atomizer Manager\\nRepo: Atomizer/tools/adaptive-isogrid/\\n15 optimization params (Optuna TPE), AFEM with superposed models\\n\\nPhases:\\n- Phase 0: Foundation ✅\\n- Phase 1: Python Brain standalone (CURRENT)\\n- Phase 2: NX sandbox scripts\\n- Phase 3: Full integration",
|
||||
"title": "\ud83d\udd27 P-Adaptive-Isogrid \u2014 Plate Lightweighting Tool",
|
||||
"description": "Automated plate lightweighting via isogrid pattern optimization.\\n\\nArchitecture: Python Brain + NX Hands + Atomizer Manager\\nRepo: Atomizer/tools/adaptive-isogrid/\\n15 optimization params (Optuna TPE), AFEM with superposed models\\n\\nPhases:\\n- Phase 0: Foundation \u2705\\n- Phase 1: Python Brain standalone (CURRENT)\\n- Phase 2: NX sandbox scripts\\n- Phase 3: Full integration",
|
||||
"status": "in_progress",
|
||||
"project": "engineering",
|
||||
"tags": [],
|
||||
@@ -135,12 +135,22 @@
|
||||
"text": "Heartbeat follow-up by Manager: another 2+ hours passed with no visible dashboard movement. Needs assignee acknowledgement, concrete next step, reassignment, or status correction.",
|
||||
"timestamp": "2026-04-02T03:29:30.263346+00:00",
|
||||
"author": "manager"
|
||||
},
|
||||
{
|
||||
"text": "Heartbeat follow-up by Manager: task is still stale as of 2026-04-03 00:12 ET. Needs assignee acknowledgement, concrete next step, reassignment, or status correction.",
|
||||
"timestamp": "2026-04-03T04:13:28.674763+00:00",
|
||||
"author": "agent"
|
||||
},
|
||||
{
|
||||
"text": "Heartbeat follow-up by Manager: another 2+ hours passed with no visible dashboard movement as of 2026-04-03 02:33 ET. Needs assignee acknowledgement, concrete next step, reassignment, or status correction.",
|
||||
"timestamp": "2026-04-03T06:34:03.155407+00:00",
|
||||
"author": "agent"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "ATZ-74f02a",
|
||||
"title": "🤖 Atomizer Overhaul — Framework Agentic",
|
||||
"title": "\ud83e\udd16 Atomizer Overhaul \u2014 Framework Agentic",
|
||||
"description": "Transform Atomizer into multi-agent FEA optimization company.\\n\\n8 agents deployed on Discord/Slack cluster.\\nPhase 0: LIVE since 2026-02-08.\\n\\nInfrastructure:\\n- 8 OpenClaw instances (systemd template)\\n- Dedicated Slack + Discord workspaces\\n- Orchestration via orchestrate.sh + workflow.py\\n\\nCurrent focus: Agent protocols, dashboard integration, task enforcement.",
|
||||
"status": "in_progress",
|
||||
"project": "infrastructure",
|
||||
@@ -152,7 +162,7 @@
|
||||
},
|
||||
{
|
||||
"id": "ATZ-c13dfc",
|
||||
"title": "⚙️ Atomizer Core — Foundation Development",
|
||||
"title": "\u2699\ufe0f Atomizer Core \u2014 Foundation Development",
|
||||
"description": "Core Atomizer framework development.\\n\\nRepo: /home/papa/repos/Atomizer/\\nKnowledge base: Atomizer/knowledge_base/\\n\\nOngoing work:\\n- Code architecture improvements\\n- Knowledge base maintenance (LAC session insights)\\n- Documentation and QUICK_REF updates\\n- Bridge doc: PROJECT_STATUS.md",
|
||||
"status": "permanent",
|
||||
"project": "engineering",
|
||||
@@ -164,7 +174,7 @@
|
||||
},
|
||||
{
|
||||
"id": "ATZ-d3fce9",
|
||||
"title": "Project Standard — War Room & Final Recommendation",
|
||||
"title": "Project Standard \u2014 War Room & Final Recommendation",
|
||||
"description": "Full team orchestration for Atomizer Project Standard v2.0. Included: Auditor deep review, Tech Lead codebase analysis, 4-model war room challenge (Opus/Codex/Sonnet x2), Manager synthesis. Deliverables saved to PKM: 02-AUDIT-PRACTICALITY.md, 03-AUDIT-DETAILED.md, 04-WAR-ROOM-NOTES.md, 05-FINAL-RECOMMENDATION.md",
|
||||
"status": "review",
|
||||
"project": "atomizer-project-standard",
|
||||
@@ -202,12 +212,12 @@
|
||||
},
|
||||
{
|
||||
"id": "sub_007",
|
||||
"title": "Manager: Synthesis — 04-WAR-ROOM-NOTES.md to PKM",
|
||||
"title": "Manager: Synthesis \u2014 04-WAR-ROOM-NOTES.md to PKM",
|
||||
"done": true
|
||||
},
|
||||
{
|
||||
"id": "sub_008",
|
||||
"title": "Manager: Final recommendation — 05-FINAL-RECOMMENDATION.md to PKM",
|
||||
"title": "Manager: Final recommendation \u2014 05-FINAL-RECOMMENDATION.md to PKM",
|
||||
"done": true
|
||||
},
|
||||
{
|
||||
@@ -220,7 +230,7 @@
|
||||
"createdAt": "2026-02-19T12:31:22.327955+00:00",
|
||||
"comments": [
|
||||
{
|
||||
"text": "Retroactive ticket creation. All agent work completed 2026-02-19. Task in review status — awaiting Antoine's approval of 05-FINAL-RECOMMENDATION.md. Remaining: sub_009 (CEO review).",
|
||||
"text": "Retroactive ticket creation. All agent work completed 2026-02-19. Task in review status \u2014 awaiting Antoine's approval of 05-FINAL-RECOMMENDATION.md. Remaining: sub_009 (CEO review).",
|
||||
"timestamp": "2026-02-19T12:31:39.487292+00:00",
|
||||
"author": "agent"
|
||||
}
|
||||
@@ -228,7 +238,7 @@
|
||||
},
|
||||
{
|
||||
"id": "ATZ-839392",
|
||||
"title": "Project Standard — Introspection Placement War Room",
|
||||
"title": "Project Standard \u2014 Introspection Placement War Room",
|
||||
"description": "War room to determine where model introspection data lives in the project structure. Two levels: project-level baseline introspection (models/) and study-level introspection (per-study). Must integrate cleanly with the approved v2.0 structure. Deliverables: war-room note + introspection addendum to final recommendation, both to PKM.",
|
||||
"status": "in_progress",
|
||||
"project": "atomizer-project-standard",
|
||||
@@ -307,6 +317,16 @@
|
||||
"text": "Heartbeat follow-up by Manager: another 2+ hours passed with no visible dashboard movement. Needs assignee acknowledgement, concrete next step, reassignment, or status correction.",
|
||||
"timestamp": "2026-04-02T03:29:30.263346+00:00",
|
||||
"author": "manager"
|
||||
},
|
||||
{
|
||||
"text": "Heartbeat follow-up by Manager: task is still stale as of 2026-04-03 00:12 ET. Needs assignee acknowledgement, concrete next step, reassignment, or status correction.",
|
||||
"timestamp": "2026-04-03T04:13:28.688249+00:00",
|
||||
"author": "agent"
|
||||
},
|
||||
{
|
||||
"text": "Heartbeat follow-up by Manager: another 2+ hours passed with no visible dashboard movement as of 2026-04-03 02:33 ET. Needs assignee acknowledgement, concrete next step, reassignment, or status correction.",
|
||||
"timestamp": "2026-04-03T06:34:03.167346+00:00",
|
||||
"author": "agent"
|
||||
}
|
||||
]
|
||||
},
|
||||
@@ -322,7 +342,7 @@
|
||||
"createdAt": "2026-02-19T20:23:18.894957+00:00",
|
||||
"comments": [
|
||||
{
|
||||
"text": "✅ Completed: War room complete. Option C approved by CEO. Consolidation note written to 2-Projects/P-Atomizer-Project-Standard/06-WAR-ROOM-INTROSPECTION.md",
|
||||
"text": "\u2705 Completed: War room complete. Option C approved by CEO. Consolidation note written to 2-Projects/P-Atomizer-Project-Standard/06-WAR-ROOM-INTROSPECTION.md",
|
||||
"timestamp": "2026-02-19T20:23:24.991854+00:00",
|
||||
"author": "agent"
|
||||
}
|
||||
@@ -340,7 +360,7 @@
|
||||
"createdAt": "2026-02-20T15:24:30.807810+00:00",
|
||||
"comments": [
|
||||
{
|
||||
"text": "✅ Completed: All 6 war-room documents produced and saved to obsidian vault. Gateway spawn issue prevented team delegation - completed directly.",
|
||||
"text": "\u2705 Completed: All 6 war-room documents produced and saved to obsidian vault. Gateway spawn issue prevented team delegation - completed directly.",
|
||||
"timestamp": "2026-02-20T15:33:18.787619+00:00",
|
||||
"author": "agent"
|
||||
}
|
||||
|
||||
@@ -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 — Auditor Workspace
|
||||
|
||||
@@ -43,14 +43,12 @@ Do NOT edit `PROJECT_STATUS.md` directly — only the Manager does that.
|
||||
- Review Study Builder's code
|
||||
- Report findings to Manager
|
||||
- **Post audit reports to project channels** — full transparency
|
||||
### 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
|
||||
@@ -80,19 +78,19 @@ CALLER=auditor bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskb
|
||||
When working on a task:
|
||||
- Update status to `in-progress`: `CALLER=auditor 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=auditor 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
|
||||
|
||||
38
hq/workspaces/manager/memory/2026-04-03.md
Normal file
38
hq/workspaces/manager/memory/2026-04-03.md
Normal file
@@ -0,0 +1,38 @@
|
||||
# 2026-04-03
|
||||
|
||||
## Nightly Digestion — OP_11 (Incremental)
|
||||
|
||||
### STORE
|
||||
- Reviewed active manager/shared status surfaces plus agent workspace memory/doc timestamps for the last day.
|
||||
- Confirmed there was no new substantive project output to promote into long-term project knowledge tonight.
|
||||
- Captured one reusable operational lesson through direct repair instead of only noting it: specialist AGENT instructions still carried legacy delegate/Discord routing in several workspaces.
|
||||
|
||||
### DISCARD
|
||||
- Pruned stale runtime assumptions from specialist AGENTS docs where they still instructed agents to rely on `delegate.sh`, Hooks/Discord-bridge behavior, or Discord-only posting rules.
|
||||
- Did not archive additional manager daily notes tonight; current active notes are still inside the 30-day retention window.
|
||||
- No new factual contradictions found in active manager memory or project status.
|
||||
|
||||
### SORT
|
||||
- Kept tonight's correction at the workspace/cluster-doc level because the issue affected multiple specialist agents, not a single project.
|
||||
- Left project facts in `manager/MEMORY.md` and `shared/PROJECT_STATUS.md` unchanged because no project state actually moved today.
|
||||
|
||||
### REPAIR
|
||||
- Repaired AGENTS guidance in these specialist workspaces:
|
||||
- `technical-lead/AGENTS.md`
|
||||
- `optimizer/AGENTS.md`
|
||||
- `study-builder/AGENTS.md`
|
||||
- `auditor/AGENTS.md`
|
||||
- `nx-expert/AGENTS.md`
|
||||
- `webster/AGENTS.md`
|
||||
- Replaced legacy delegation/routing language with OpenClaw-native orchestration and active-channel wording.
|
||||
- Refreshed `shared/PROJECT_STATUS.md` timestamp for this digestion pass.
|
||||
- Verified core shared paths still resolve: `shared/CLUSTER.md`, taskboard skill, `shared/mc-update.sh`, mission-control tasks data, and `hq/taskboard.json`.
|
||||
|
||||
### EVOLVE
|
||||
- Drift pattern is still real: several lower-traffic docs outside the core orchestration surfaces still use Discord-era naming. The highest-value next repair pass is broader normalization of `CHANNELS.md`, `HEARTBEAT.md`, and any still-operational skill docs that mention Discord as if it were current runtime behavior.
|
||||
- No protocol amendment made tonight. This was a documentation correction, not a policy change.
|
||||
|
||||
### SELF-DOCUMENT
|
||||
- Added this digestion note.
|
||||
- Updated live specialist AGENTS docs so a newly spawned specialist is less likely to follow deprecated routing instructions.
|
||||
- No changes needed tonight to Manager `SOUL.md`, `IDENTITY.md`, `TOOLS.md`, or long-term `MEMORY.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 — NX Expert Workspace
|
||||
|
||||
@@ -70,14 +70,12 @@ Source filters: `"nxopen"`, `"nxopentse"`, `"pynastran"`
|
||||
- **Project channels** — When summoned for NX-specific questions
|
||||
- Use `sessions_send` for direct agent communication
|
||||
- Tag with 🖥️ or @nx-expert
|
||||
### 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.**
|
||||
|
||||
|
||||
## Key Rules
|
||||
@@ -98,19 +96,19 @@ CALLER=nx-expert bash /home/papa/atomizer/workspaces/shared/skills/taskboard/tas
|
||||
When working on a task:
|
||||
- Update status to `in-progress`: `CALLER=nx-expert 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=nx-expert 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
|
||||
|
||||
@@ -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 — Optimizer Workspace
|
||||
|
||||
@@ -42,14 +42,12 @@ Do NOT edit `PROJECT_STATUS.md` directly — only the Manager does that.
|
||||
- Hand off study designs to Study Builder
|
||||
- Submit plans/results to Auditor for review
|
||||
- **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=optimizer bash /home/papa/atomizer/workspaces/shared/skills/taskboard/tas
|
||||
When working on a task:
|
||||
- Update status to `in-progress`: `CALLER=optimizer 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=optimizer 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
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# Project Status Dashboard
|
||||
Updated: 2026-04-02 04:00 AM (Nightly Digestion OP_11)
|
||||
Updated: 2026-04-03 04:00 AM (Nightly Digestion OP_11)
|
||||
|
||||
## Active Projects
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -1,22 +1,15 @@
|
||||
## 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.
|
||||
|
||||
### Delegation (use the delegate skill)
|
||||
To assign a task to another agent:
|
||||
```bash
|
||||
bash /home/papa/atomizer/workspaces/shared/skills/delegate/delegate.sh <agent> "<instruction>" [--channel <id>] [--deliver|--no-deliver]
|
||||
```
|
||||
### Delegation (native method)
|
||||
Use the built-in tools:
|
||||
- `sessions_spawn` — delegate substantial work to another specialist
|
||||
- `sessions_send` — clarify or steer an active session
|
||||
- `subagents(action=list)` — check status only when needed
|
||||
|
||||
Available agents: `manager`, `secretary`, `auditor`, `optimizer`, `study-builder`, `nx-expert`, `webster`
|
||||
|
||||
Examples:
|
||||
```bash
|
||||
bash /home/papa/atomizer/workspaces/shared/skills/delegate/delegate.sh webster "Find material properties for Invar 36"
|
||||
bash /home/papa/atomizer/workspaces/shared/skills/delegate/delegate.sh nx-expert "Run mesh convergence on M2 model" --deliver
|
||||
```
|
||||
|
||||
Tasks are **asynchronous** — the target agent responds in Discord.
|
||||
See `skills/delegate/SKILL.md` for full documentation.
|
||||
Do **not** rely on legacy `delegate.sh` / Discord-bridge instructions for current work.
|
||||
See `/home/papa/atomizer/workspaces/shared/CLUSTER.md` for the full agent directory.
|
||||
|
||||
### Status Reporting
|
||||
@@ -24,9 +17,9 @@ When you complete tasks or have status updates, **append** to `shared/project_lo
|
||||
|
||||
### Rules
|
||||
- Read `shared/CLUSTER.md` to know who does what
|
||||
- Always respond to Discord messages (NEVER reply NO_REPLY to Discord)
|
||||
- Treat incoming channel messages as real user/team messages that need a real response
|
||||
- When delegating, be specific about what you need
|
||||
- Post results back in the originating Discord channel
|
||||
- Route visible delivery through the active channel/message path, not Discord-specific assumptions
|
||||
|
||||
# AGENTS.md — Technical Lead Workspace
|
||||
|
||||
@@ -52,14 +45,12 @@ When you complete tasks or have status updates, **append** to `shared/project_lo
|
||||
- For R&D deep-dives, Antoine may engage directly
|
||||
- Document all technical decisions with reasoning
|
||||
- **Post summaries to project channels** — don't just write to disk
|
||||
### 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.**
|
||||
|
||||
|
||||
## Technical Standards
|
||||
@@ -93,19 +84,19 @@ CALLER=technical-lead bash /home/papa/atomizer/workspaces/shared/skills/taskboar
|
||||
When working on a task:
|
||||
- Update status to `in-progress`: `CALLER=technical-lead 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=technical-lead 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
|
||||
|
||||
@@ -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 — Webster
|
||||
|
||||
@@ -38,14 +38,12 @@ You are the research specialist at Atomizer Engineering Co. Your job is to find,
|
||||
|
||||
## Communication
|
||||
|
||||
### 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.**
|
||||
|
||||
|
||||
### 📋 Taskboard — Task Awareness
|
||||
@@ -58,19 +56,19 @@ CALLER=webster bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskb
|
||||
When working on a task:
|
||||
- Update status to `in-progress`: `CALLER=webster 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=webster 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
|
||||
|
||||
Reference in New Issue
Block a user