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

1.3 KiB

Step 2: a real-model run through the container

Run 2026-10-20.

What was run

Evaluation case 01's written spec (eval/datasets/specs/landing-zone-shared.yaml), sent to the container from step 1 as one A2A message/send with configuration.blocking: false, then polled with tasks/get. The message metadata carried pre_approved: true, customer_case: bench-landing-zone-shared and the spec as scope. Models were Gemini on Vertex AI with the developer's application default credentials, mounted read-only.

Result

Minutes State Capabilities People Scenarios
31.6 completed 20 5.1 13 of 13 pass

The task's artifacts were all eleven files: the guide, scope.yaml and scope.json, operational requirements, capabilities, the Target operating model and its organisation chart, staffing, findings, verdicts and scenarios.

What differed from the plan

  • The Customer case must be the spec's. The first attempt named another slug and was refused at once: "The scope spec is for bench-landing-zone-shared, and this was started for smoke-01." A caller that sends a spec sends its Customer case with it.
  • Postgres. The engine tries localhost:5432, logs a warning and falls back to SQLite in /data. Harmless here; a shared deployment sets DATABASE_URL.