Files
solution_architecture_agent/.agents/plans/iter-01-on-the-engine/MAP.md
Jonathan Boniface c84dbdea20 feat: the solution architecture agent on the shared Execution engine
The reference agent's subject, cloud solution architecture, as an agent in
the operating model agent's pattern: the Execution engine (from
orchestration_engine) and one Workflow in app/solution_architecture,
built for the settings and provider bundle by assembly.workflow_for.

Copied from gcp_solution_architecture_agent at 8b397cd without its own
engine: its role files, Skills, provider bundle, ADRs, vocabulary, scripts
and evaluation datasets. The image takes the engine from a named build
context and installs Terraform. It is called through the Orchestration
engine, and its files are what the operating model agent digests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 19:49:28 +01:00

1.8 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

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 planned
3 The evaluation harness on the engine, from the reference's eval/ The reference's cases run against this agent planned