3.0 KiB
Plan Map
Iteration: 2, on the platform
Intent: The operating model agent runs as a container beside the local KAB platform, is registered in its catalogue, and completes an Execution started by a platform workflow. The Orchestration engine (F1, F2, in ../orchestration_engine) is then put in front of it.
Status: steps 1 to 3 built 2026-10-20; step 4 in progress
Decided by the owner, 2026-10-20
- E7, locally: the image is built with a named build context,
--build-context engine=../orchestration_engine, and installs the Execution engine from it. No file is copied by hand. CI will use a dependency on the engine's repository at a pinned commit. - Order: this agent first (steps 1 to 4), then the Orchestration engine (step 5).
- Models: Gemini on Vertex AI, as in the evaluation, with the developer's application default credentials mounted read-only. The platform's LiteLLM is not used.
Sources of truth
IMPLEMENTATION_PLAN.md, sections 2 and 10 (E7, F1, F2).../modernization-platform/packages/agent-builder-local-dev-kit/README.md: the local platform,agents-compose.ymlandscripts/compose.sh agents.../modernization-platform/packages/agent-builder-temporal-workers/src/temporal/a2a_client.py: how a platform workflow calls an agent.
Known mismatch
A platform workflow step treats an A2A input_required as the agent runtime's action review (a list of tool calls to approve, at most MAX_ACTION_REVIEWS rounds). The engine's questions and Approvals are not that, so a platform workflow calls this agent pre-approved. Interactive Executions go through the Orchestration engine, which relays every prompt (F2). Step 4 confirms this rather than assuming it.
Status
| Step | What | Done when | Status |
|---|---|---|---|
| 1 | The image (E7): Dockerfile, .dockerignore, the engine from the named build context |
The image builds from a clean checkout of both repositories; /health and the agent card answer |
built (steps/step-1.md) |
| 2 | A real-model run through the container | One pre-approved Execution of case 01 completes through the container's A2A endpoint | built (steps/step-2.md) |
| 3 | On the platform's network: an entry in the dev kit's agents-compose.personal.yml, registered in the catalogue |
It is listed in the catalogue; the API container reaches http://tom-analysis:8080/health |
built (steps/step-3.md) |
| 4 | A platform workflow with one step calling this agent | The workflow completes in Temporal with the Deliverables in its output | in progress: the engine's card declares KAB's input contract (request, customer_case, scope, pre_approved), chosen by the owner; waiting on the catalogue refresh and the workflow |
| 5 | The Orchestration engine in front (F1, F2 in ../orchestration_engine) |
An Execution of either agent runs through it, Approvals relayed | F2 built (../../../orchestration_engine/.agents/plans/iter-02-orchestration-engine/steps/step-2.md): this agent's questions relayed through it on the platform; F1 awaits the owner |