# MEMORY.md — Manager Long-Term Memory

## Company Context

**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)

## Key Facts
- Antoine runs NX/Simcenter on Windows (dalidou)
- Optimization loop: agents prepare → Syncthing delivers → Antoine runs `run_optimization.py` → results flow back
- All deliverables need Antoine's approval before going external
- Quality over speed, but ship regularly

## Founding Documents
All Atomizer HQ planning docs are in `context-docs/`:
- **00-PROJECT-PLAN.md** — The full project plan (vision, phases, success criteria)
- **01-AGENT-ROSTER.md** — All 13 agents with detailed roles, capabilities, models
- **02-ARCHITECTURE.md** — Technical architecture (Clawdbot multi-agent, Slack, Syncthing bridge)
- **03-ROADMAP.md** — Phased rollout: Phase 0 (Core) → Phase 1 (Optimization) → Phase 2 (Production) → Phase 3 (Advanced)
- **04-DECISION-LOG.md** — Key decisions: Clawdbot over Agent Zero, dedicated Slack workspace, phased rollout, autonomy with approval gates
- **05-FULL-SYSTEM-PLAN.md** — Complete system specification (83KB, comprehensive)
- **README-ANTOINE.md** — CEO's overview, the "why" behind everything
Read these on first session to fully understand the vision and architecture.

## Active Projects
- **Hydrotech Beam** — Channel: `#project-hydrotech-beam` | Phase: DOE Phase 1 complete (39/51 solved, mass NaN fixed via commit 580ed65, displacement constraint relaxed 10→20mm). Next: pull fix on dalidou, rerun DOE. **Blocked on Antoine running updated code on dalidou.**
- **Adaptive Isogrid Plate Lightweighting** — Channel: war-room-isogrid | Phase: Technical spec locked + reviews complete. Full spec (32KB) + optimizer/tech-lead/webster reviews in `shared/war-room-isogrid/`. Architecture: "Python Brain + NX Hands + Atomizer Manager". Next: CEO review → implementation planning.
- **Atomizer Project Standard** — Phase: Full review package delivered (2026-02-18). Spec (~57KB), tech-lead review, auditor audit, secretary synthesis all complete. Files in `shared/standardization/`. **Auditor verdict: spec is over-engineered — recommends Minimum Viable Standard (MVS) based on Hydrotech Beam's existing structure.** Awaiting CEO decision: adopt full spec vs MVS approach. Next: Antoine review → decision → implementation.
- **Atomizer V2 Migration** — Phase: COMPLETE (2026-02-23). 8 commits pushed to Gitea. 218+ Python files, 58 tests passing. All phases done: repo bootstrap, core engine port, integration testing, reference implementation, CLAUDE.md, Data Contracts (5 dataclasses), Pipeline-NX integration tests, roadmap for items 4-9. Dalidou validated: `import atomizer` v2.0.0 + 24/24 tests on Windows. V1 tagged `v1-final` but kept active for Antoine's current optimizations. AOM→Obsidian auto-sync via crontab (15min rsync + wiki-link conversion). Phase 6 (archive V1) deferred until Antoine switches production work.
- **Atomizer/HQ Separation** — CEO decision (2026-02-23): Atomizer = product (V2 repo), HQ = AI operations team (HQ repo). AOM governs the product. 7 AOM docs updated to reflect boundary. DEC-037 logged. HQ repo pushed to Gitea with full operational structure (218 files).

## Core Protocols
- **OP_11 — Digestion Protocol** (CEO-approved 2026-02-11): STORE → DISCARD → SORT → REPAIR → EVOLVE → SELF-DOCUMENT. Runs at phase completion, weekly heartbeat, and project close. Antoine's corrections are ground truth.

## Lessons Learned
- Mass confusion (11.33 vs 1133 kg) — contradictions propagate fast when not caught. Digestion protocol's DISCARD + REPAIR phases exist to prevent this.
- `beam_lenght` typo in NX — must use exact spelling. Domain-level knowledge.
- NX integer expressions need `unit=Constant`, not `MilliMeter`
- Always `.resolve()` paths, never `.absolute()` — NX file references break on copy
- Existing `optimization_engine` should be wrapped, not reinvented
- Sub-agents hit 200K token limits easily — keep prompts lean, scope narrow
- Spawned sub-agents can't post to Slack channels (channel routing issue) — do Slack posting from main agent
- Secretary also hit Slack posting issues (missing bot token in spawned context) — always post final deliverables from main agent
- Auditor produces high-value "reality check" reviews — always include in spec/design work
- Taskboard CLI (`mc-update.sh`) works but only supports basic commands (status/comment/add/complete/start) — no `list` view