Files
tom_analysis_agent/.agents/plans/iter-02-platform-deployment/steps/step-3.md

2.0 KiB

Step 3: on the platform's network

Built 2026-10-20.

What was built

In the dev kit (../modernization-platform/packages/agent-builder-local-dev-kit), two personal files, excluded from git in that clone's .git/info/exclude:

  • agents-compose.build.personal.yml: tom-analysis built from ../../../tom_analysis with additional_contexts: {engine: ../../../orchestration_engine}.
  • agents-compose.personal.yml: the container tom-analysis on agent-builder-network, port ${TOM_ANALYSIS_PORT:-10020}:8080, A2A_PUBLIC_URL=http://tom-analysis:8080, the credentials mounted read-only, named volumes for /data and /app/deliverables, and its own healthcheck.
./scripts/compose.sh agents build tom-analysis
./scripts/compose.sh agents up tom-analysis

The owner registered it in the catalogue from the admin page (Agents, Discover agent, http://tom-analysis:8080). It is listed as target_operating_model_agent.

What differed from the plan

  • No pod. podman-compose puts every container in one pod, and podman refuses a per-container user namespace (keep-id, step 1) inside a pod. The personal file sets x-podman: in_pod: false. Agents reach each other by name on the network, not through the pod.
  • The platform calls the address an agent was registered with, not the A2A interface its card names (agent_catalog_service.py sets endpoint.url to the discovery URL). The engine served JSON-RPC only at /a2a, so every platform call would have been a 404. Chosen by the owner: the engine serves the same handler at / as well (execution_engine/main.py, with a test in tests/toy/test_server.py). The card still names /a2a. The platform's choice is worth raising with its team.

Verified

  • From the API and workers containers: /health, both card paths, and JSON-RPC at / and at /a2a.
  • The catalogue record names the agent, its skill and its examples.
  • The engine: 532 tests pass; ruff and mypy clean. This agent: 177 tests pass.