🏗️ MSV Router Architecture

MeuSecretárioVirtual — Container Provisioning Flow

ENTRY POINTS

message-handler.js

Text messages
[FIRST_INTERACTION] prefix

bot.js

Voice, photos, documents
Inline callbacks

↓ Both call containerManager.*

▼

container-manager.js (896 lines)

✅ PRODUCTION

getValidatedContainerPort()
provisionAgentAsync() →
resetValidationCache()
allocatePort()
storeContainerPort()

🧪 TESTS ONLY

provisionAgent()
provisionAgentWithRetry()
spawnContainer() (sync)

⚠️ Same templates via ./templates

▼

container-pool.js → container-worker.js

🚀 ACTUAL PRODUCTION CODE

Runs in Worker thread (non-blocking)
spawnContainer() ← production version
waitForHealthy(), installProactiveAmcp()
Imports from ./templates

▼

templates/ — 🎯 SINGLE SOURCE OF TRUTH

index.js Re-exports all
agents-template.js → AGENTS.md (first interaction!)
bootstrap-template.js → BOOTSTRAP.md
soul-template.js → SOUL.md
memory-template.js → MEMORY.md

✨ Edit here → changes apply to tests AND production

📁 DETERMINISTIC VOLUME NAMING

Container: msv-agent-{telegramId}

Data dir: /opt/msv/data/{telegramId}/

/opt/msv/data/{telegramId}/
├── config/openclaw.json  → container config
├── workspace/            → AGENTS.md, MEMORY.md, etc
├── sessions/             → conversation history
├── media/                → images, voice, files
└── amcp/                 → agent identity

🔍 Find user: ls /opt/msv/data/{TELEGRAM_ID}/

Entry Points

Production Path

Tests Only

Single Source of Truth