The Orchestration engine keeps every completed agent Execution it relays, by tenant, Customer case and Execution, and serves its record and files at signed, expiring links. A KAB workflow step, which takes one output per step, is given one JSON document of links (`deliver: links`); other callers still get each file, and what they are given is kept either way. - store.py, links.py, delivery.py, serving.py; the relay keeps and links - the card declares `deliver`, `sources` and an output schema - image: STORE_DIR on a /data volume; PUBLIC_URL and LINK_SECRET settings - option 1's tests replaced by tests of the links document Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.9 KiB
2.9 KiB
Plan Map
Iteration: 2, the Orchestration engine
Intent: The service every request comes through. It decides which agent the work belongs to, dispatches it, and relays every question and Approval. First behind it: the operating model agent (../tom_analysis).
Status: F1 proposed; F2 and F4 built 2026-10-20; K1 built 2026-10-21
Decided by the owner, 2026-10-20
- Two agents on the platform: the Orchestration engine, which routes each request to an agent, and the operating model agent behind it. The Orchestration engine is what callers use.
- The solution architecture agent (
../solution_architecture_agent) behind it too, its output passed to the operating model agent through the Orchestration engine (F4).
Sources of truth
../tom_analysis/IMPLEMENTATION_PLAN.md, sections 2 and 4, and steps F1 to F5 in section 10.docs/adr/0003-one-orchestration-engine-above-the-agents.md.docs/adr/0004-the-orchestration-engine-keeps-what-agents-deliver.md.../tom_analysis/.agents/plans/iter-02-platform-deployment/: how an agent runs on the local KAB platform.
Status
| Step | What | Done when | Status |
|---|---|---|---|
| F1 | ADR-0003: one Orchestration engine above the agents | Accepted by the owner | proposed |
| F2 | The service: an A2A server, a configured list of agents, a request passed through to one agent with every prompt relayed; its image; on the local platform | An Execution of the operating model agent runs through it, Approvals included, with the agent untouched | built (steps/step-2.md); the platform workflow through it is step 4 of ../tom_analysis iteration 2 |
| F3 | The decision: readings in code, the Jev question, thresholds, the fallbacks, the record | A labelled set of messages is routed correctly; low confidence asks; no Jev key still routes what is named | planned |
| F4 | "Both": architecture, then its files as sources to the operating model agent |
One request yields both sets of Deliverables under one Customer case | built against scripted agents (steps/step-4.md), ahead of F3 at the owner's request; not yet run with real models |
| F5 | Later messages to the agent that owns the work | A change to the architecture is followed by a change to the operating model | planned |
| K1 | What agents deliver, kept and served at signed links; a platform step given one document of links (ADR-0004, phase 1) | A platform step's output links to each delivered file, and each link serves it | built (steps/step-K1.md); the owner's run through the platform to follow |
| K2 | sources_from: a request names kept work instead of carrying its files; the sequence moved onto it |
An operating model started from the latest architecture of a Customer case | planned |
| K3 | Object storage shared with the platform, the platform's sign-in, retention, each file as a platform artifact | A kept guide is listed among the project's artifacts | planned |