1.5 KiB
1.5 KiB
Open Questions and Assumptions
Decisions Confirmed in This Session
- Production authority is per-node compose manifests (NODE1/NODE3/Staging), not merged universal compose.
ingest-service,parser-pipeline,control-planeare currently not active on NODE1 runtime.- Canonical run subject policy is namespaced:
agent.run.requested.{agent_id}with wildcard subscriber strategy. - Production must have single edge proxy owner for 80/443.
Remaining Open Items
- Exact deployment location (host/node/manifest) for
ingest-service,parser-pipeline,control-planewhen they become DEPLOYED. - Final production proxy owner choice (nginx or Caddy) for canonical runtime profile.
- Timeline/PR sequence for NATS subject migration completion and legacy deprecation cutoff.
- Missing referenced services in default compose (
node-registry,city-service,agent-cabinet-service,devtools-backend,orchestrator,microdao): same repo future work vs external repo ownership.
Verification Artifacts Required to Close Items
- Node-specific compose/service unit link proving deployment location.
- Runtime
docker ps+ health snapshot for each node. - NATS stream/consumer metrics showing legacy subject traffic = 0 before deprecation.
- Proxy port ownership verification (
80/443) on runtime host.
Source pointers
docs/SESSION_STARTER.mddocker-compose.node1.ymldocker-compose.node3.ymldocker-compose.staging.ymlservices/crewai-worker/main.pyops/nginx/node1-api.confinfra/compose/Caddyfile