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

hq/workspaces/manager/MEMORY.md

@@ -4,8 +4,8 @@
 
 **Atomizer Engineering Co.** is an AI-powered FEA optimization company.
 - CEO: Antoine Letarte (mechanical engineer, freelancer)
-- Platform: Clawdbot multi-agent on dedicated Slack workspace
-- Infrastructure: Docker on T420, Syncthing bridge to Windows (NX/Simcenter)
+- Platform: OpenClaw multi-agent workspace with native orchestration and Slack/message-tool delivery
+- Infrastructure: Docker/OpenClaw on T420, Syncthing bridge to Windows (NX/Simcenter)
 
 ## Key Facts
 - Antoine runs NX/Simcenter on Windows (dalidou)

hq/workspaces/manager/TOOLS.md

@@ -31,9 +31,10 @@
   - Usage: `python3 metrics.py [json|text]`
   - Shows: per-agent success rates, latencies, workflow completion stats
 - **Agent Registry:** `/home/papa/atomizer/workspaces/shared/AGENTS_REGISTRY.json`
-- **`[DELEGATE:agent "task"]` syntax does NOT work** — never use it. Always use `orchestrate.sh` or Discord @mentions.
-- Discord @mentions — For ongoing work, discussions, FYI (fire-and-forget)
-- `sessions_send` / `sessions_spawn` — OpenClaw internal (within same instance only)
+- **`[DELEGATE:agent "task"]` syntax does NOT work** — never use it.
+- Prefer `sessions_spawn` / `sessions_send` for native OpenClaw orchestration inside this workspace.
+- Use `orchestrate.sh` only when you explicitly want that shared orchestration layer.
+- Use the `message` tool for user-visible channel delivery.
 
 ## Knowledge Base
 - LAC insights: `/home/papa/repos/Atomizer/knowledge_base/lac/`

hq/workspaces/manager/memory/2026-03-28.md

@@ -0,0 +1,30 @@
+# 2026-03-28
+
+## Nightly Digestion — OP_11 (Incremental)
+
+### STORE
+- Reviewed recent manager digestion state plus current cross-workspace memory/docs.
+- Captured tonight's real operational lesson in `manager/MEMORY.md`: platform wording updated from legacy Clawdbot framing to current OpenClaw-native orchestration + Slack/message delivery.
+
+### DISCARD
+- Pruned stale Discord-bridge assumptions from high-impact shared docs instead of leaving contradictory routing guidance in place.
+- Did not mass-delete old agent memory files tonight; many older files are sparse but still historical artifacts rather than clear noise. Better candidate for a dedicated archive pass with per-agent summaries.
+
+### SORT
+- Kept routing/process corrections at the company/shared-doc level because the issue affects multiple agents, not just one session.
+- Left project-specific memory in place; no new project/domain insights needed promotion tonight.
+
+### REPAIR
+- Repaired `shared/CLUSTER.md` to point agents to native OpenClaw orchestration (`sessions_spawn` / `sessions_send`) and current Slack/channel delivery expectations.
+- Repaired `shared/skills/taskboard/SKILL.md` to remove Discord-specific delivery wording.
+- Repaired `manager/TOOLS.md` to prefer native orchestration over legacy Discord-era delegation habits.
+- Repaired `secretary/AGENTS.md` to remove Discord-bridge assumptions and generalize delivery/retry rules to the active messaging path.
+- Verified key operational paths still exist: shared `mc-update.sh`, mission-control `mc-update.sh`, `hq/taskboard.json`, `shared/CLUSTER.md`, `shared/AGENTS_REGISTRY.json`, taskboard skill.
+
+### EVOLVE
+- Drift pattern confirmed: many non-manager agent docs still contain Discord-era operational language. Highest-value next digestion pass is a broader documentation normalization sweep across all agent workspaces.
+- Recommendation: prioritize shared/core docs first (done), then agent-local AGENTS/CHANNELS/HEARTBEAT files in batches so we do not create inconsistent partial rewrites.
+
+### SELF-DOCUMENT
+- Updated company/shared docs to better reflect current runtime reality.
+- No changes needed tonight to Manager `SOUL.md`, `IDENTITY.md`, or task/project memory.