1.7 KiB
1.7 KiB
DAGI / microdao Architecture Inventory — Executive Summary
Generated: 2026-02-16
Scope basis: docs/SESSION_STARTER.md + repository scan + operator clarifications (current thread decisions).
Executive Findings (Updated)
- Canonical deployment authority is per-node compose manifests, not a single universal file.
- NODE1:
docker-compose.node1.yml - NODE3:
docker-compose.node3.yml - Staging:
docker-compose.staging.yml(+ overrides)
- NODE1:
- Drift-check policy should run per node against its local compose stack (services/images/ports/volumes/networks/env-nonsecret/healthcheck).
ingest-service,parser-pipeline,control-planeare currently treated as not active on NODE1; catalog now uses lifecycle statuses (DEPLOYED,DEFINED,PLANNED/EXTERNAL).- NATS canonical run subject policy is set to:
- publish:
agent.run.requested.{agent_id} - subscribe:
agent.run.requested.*with dual-subscribe/publish migration window.
- publish:
- Proxy policy is fixed at architectural level: single owner for 80/443 in production (nginx or Caddy), second proxy internal-only or disabled.
Priority Contradictions To Resolve
- Memory API contract mismatch (
/storein docs vs/memories//events//retrievein code). - NATS run subject shape mismatch (legacy flat subject still in worker/producer paths).
- Proxy ownership conflict (nginx vs Caddy) in runtime runbooks.
- Architecture diagrams include services not currently deployed on NODE1.
Source pointers
docs/SESSION_STARTER.mddocker-compose.node1.ymldocker-compose.node3.ymldocker-compose.staging.ymlservices/crewai-worker/main.pyservices/router/main.pyops/nginx/node1-api.confdocs/OPENAPI_CONTRACTS.mddocs/ARCHITECTURE_DIAGRAM.md