📅 Week 10 · 2026-03-06 ⚡ Generated by m2 (orchestrator) 🔒 Internal

Video Calls, Onboarding Engine & Fleet Expansion

68%
Overall production readiness
9 agents healthy 2 degraded 4 blocked 12 shipped

Subsystem Scores

Fleet Management 72%
Memory System 65%
Autonomous Org Builder 52%
Communication Protocols 70%
Playbook Adoption 60%
Resource Provisioning 62%
Role / Org Science 48%
Dark Factory Engine 50%

Fleet Numbers

9
Healthy Agents
2
Degraded
51
Containers
4,100+
Memory Vectors

Shipped This Week

Joinly video call engine — screen share, viz presentations, auto-rejoin, mic management (20+ commits)
Fleet Playbook §14 Production Build Harness + §15 Model Selection Policy + §16 Video Calls
Full onboarding engine in m2-config — spawn machine, admin approval, contacts, templates, Superhero Capital group wiring
Agent-org-simulator benchmark run #8 complete
machinemachine.ai: Dries Cleaning landing page (PL/DE/EN) + market analysis + 5-year business plan
machinemachine.ai: pitch deck navigation overhaul — slide nav, scroll-snap, CRM note integration
5 auto-generated AI research blog posts (Safe-SAGE, Jacobian Regularization, Consensus, Multi-Attribution, DARE-bench)
Host monitor with peak alert tracking deployed
Fleet governance retro run_008 semantic priority check
OpenClaw upstream merge — cron stabilization, security fixes, Spanish locale, compaction safeguards
Forgejo→Coolify auto-deploy webhook instructions added to playbook §13
Daily backups running reliably (7/7 days)

Gaps & Blockers

Critical Gaps

Container sprawl — 8 unhealthy services

8 containers in exited:unhealthy state. Need cleanup or restart: Claude proxy, Home Assistant, Pinokio, aicd-kokoro-tts, claude-worker, joinly, vllm-docker, muninndb-pilot.

No org-level memory

Agents still siloed. Shared knowledge graph across fleet not yet deployed.

Warnings & Blocked

Fleet dashboard CPU spike

fleet-dashboard container at 80% CPU — likely a runaway process or infinite loop.

m2-desktop high resource usage

m2-desktop-worker using 5.9 GiB RAM (4.7% of host) and 66% CPU — heaviest single container.

Dark Factory loop not closed

Compiler + deploy exist but meta-agent gap detection still missing.

🔴 Home Assistant still exited/unhealthy — redirect loop unresolved
🔴 Several services exited/unhealthy: Claude proxy, Pinokio, aicd-kokoro-tts, chatterbox-tts, claude-worker, joinly (original), vllm-docker, muninndb-pilot
🔴 LinkedIn auto-post still blocked (no persistent browser session)
🔴 SpacetimeDB running but unhealthy

Priority Actions

1. Triage 8 unhealthy containers — restart or decommission unused services
2. Investigate fleet-dashboard 80% CPU spike
3. Deploy org_memory shared Qdrant namespace for cross-agent knowledge
4. Close Dark Factory meta-agent gap detection loop
5. Fix Home Assistant redirect loop
6. Ship capability registry so orchestration isn't hardcoded