Files
solution_architecture_agent/.agents/plans/iter-01-on-the-engine/MAP.md

1.9 KiB

Plan Map

Iteration: 1, on the engine Intent: The reference agent's subject, cloud solution architecture, as an agent in the operating model agent's pattern: the shared Execution engine and one Workflow, called through the Orchestration engine, its files passed on to the operating model agent. Status: step 1 built 2026-10-20; step 2 run 2026-10-21

Decided by the owner, 2026-10-20

  • A new agent in solution_architecture_agent/, copied from gcp_solution_architecture_agent/ and aligned to tom_analysis/'s pattern. The reference is left as it is.
  • Every request reaches it through the Orchestration engine, and its output is passed to the operating model agent there.

Sources of truth

  • CONTEXT.md and docs/adr/, from the reference.
  • ../orchestration_engine/tests/reference_workflow/: the engine's example of this Workflow, which app/solution_architecture/ was brought from.
  • ../orchestration_engine/docs/adr/0003-one-orchestration-engine-above-the-agents.md.
  • ../tom_analysis/app/operating_model/digest.py: what the operating model agent reads of this agent's files.

Status

Step What Done when Status
1 The agent on the engine: its folder, app/ as the Workflow, the image, on the local platform behind the Orchestration engine A pre-approved Execution on the agent's own roles, Skills and provider bundle delivers every file the operating model agent digests; the container answers on the platform built (steps/step-1.md)
2 A run with real models through the Orchestration engine, then the sequence into the operating model agent One request for architecture_and_operating_model yields both sets of Deliverables under one Customer case built (steps/step-2.md): completed 2026-10-21 in 74.9 minutes
3 The evaluation harness on the engine, from the reference's eval/ The reference's cases run against this agent planned