feat: add Atomizer HQ multi-agent cluster infrastructure

- 8-agent OpenClaw cluster (Manager, Tech-Lead, Secretary, Auditor,
  Optimizer, Study-Builder, NX-Expert, Webster)
- Orchestration engine: orchestrate.py (sync delegation + handoffs)
- Workflow engine: YAML-defined multi-step pipelines
- Agent workspaces: SOUL.md, AGENTS.md, MEMORY.md per agent
- Shared skills: delegate, orchestrate, atomizer-protocols
- Capability registry (AGENTS_REGISTRY.json)
- Cluster management: cluster.sh, systemd template
- All secrets replaced with env var references

hq/workspaces/manager/memory/2026-02-08.md

@@ -0,0 +1,51 @@
+# 2026-02-08
+
+## New Project: Hydrotech Beam Structural Optimization
+- **Channel:** #project-hydrotech-beam
+- **Request:** Optimize I-beam with sandwich cross-section — reduce mass, reduce tip displacement, keep stress safe
+- **Status:** Intake received, project folder created at `/home/papa/atomizer/projects/hydrotech-beam/`
+- **Next:** Delegate technical breakdown to Technical Lead (OP_09 → OP_10 Step 2)
+- 4 design variables, NX Nastran static analysis, steel beam with lightening holes
+- Current baseline: ~974 kg, ~22 mm displacement
+- Targets: minimize mass, displacement < 10 mm, stress < 130 MPa
+
+## Issues Raised by Antoine
+- No Notion project page yet (Phase 2 feature — not available)
+- Secretary had no project context — briefed her via sessions_send, she's now tracking it
+- Slowness noted — all agents on Opus, expected for now
+- Project folder confirmed at `/home/papa/atomizer/projects/hydrotech-beam/`
+- Antoine wants cross-agent context sharing to work better — need to think about how Secretary gets project updates automatically
+
+## Config Changes
+- Added `#project-hydrotech-beam` (C0AE4CESCC9) to channel config with `requireMention: false`
+- Antoine no longer needs to tag to get a response in project channels
+
+## Antoine Request: Project Dashboard & File Access
+- Manager now owns ALL admin responsibility — Mario only for infrastructure bridges
+- NO Notion — Antoine doesn't use it
+- Project data should live in Atomizer repo (Gitea: http://100.80.199.40:3000/Antoine/Atomizer.git)
+- Documentation = efficient .md files in the repo
+- Current project files at `/home/papa/atomizer/projects/hydrotech-beam/` need to move into `/home/papa/repos/Atomizer/projects/hydrotech-beam/`
+- Syncthing syncs: ATODrive, Atomaste, obsidian-vault, Sync — NOT the atomizer workspace
+- Atomizer repo is git-managed (correct approach for project data)
+
+## Project Structure Overhaul — COMPLETED
+- Designed and implemented KB-integrated project structure for Atomizer
+- Hydrotech Beam restructured: README, CONTEXT, BREAKDOWN, DECISIONS, models/, kb/, studies/, deliverables/
+- KB initialized: components/sandwich-beam.md, materials/steel-aisi.md, fea/models/sol101-static.md
+- Gen 001 created from intake + technical breakdown
+- 6 decisions logged in DECISIONS.md (DEC-HB-001 through DEC-HB-006)
+- Created `knowledge-base-atomizer-ext.md` — Atomizer extension of Mario's shared KB skill
+- Extension pattern: use base skill as-is, extend with Atomizer-specific agent workflows
+- All committed to Gitea: commit 9541958
+- Channel config fixed: #project-hydrotech-beam no longer requires mention
+
+## Repo Cleanup — IN PROGRESS
+- CEO approved major docs cleanup of Atomizer repo
+- Spawned sub-agent (label: repo-cleanup) to handle:
+  - Archive stale docs (RALPH_LOOP, old CANVAS plans, dashboard iterations) to docs/archive/review/
+  - Create docs/hq/ with agent-facing documentation (PROJECT_STRUCTURE, KB_CONVENTIONS, AGENT_WORKFLOWS, STUDY_CONVENTIONS)
+  - Update docs/00_INDEX.md
+- KB skill discussion resolved: Mario's pipeline = tool, Atomizer owns project KB, no duplication
+- Mario's KB output can bootstrap Atomizer project KB if available
+- CAD-Documenter tool being renamed (to KBS or similar) — update references when it lands