6d32bc696d0ef9e85e7326b71ca05bc178cfe03e
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>
Orchestration engine
Two things live here.
- Execution engine (
execution_engine/): the package an agent runs on. It holds one Execution of a Workflow: Deliverables, Phases, Approvals, and the agents that produce them. It knows no subject. - Orchestration engine: the service every request comes through, which decides which agent the work belongs to. Not built yet.
Vocabulary is in CONTEXT.md, decisions in docs/adr/, the design in .scratch/engine/spec.md, and what has been built in .agents/plans/.
python3 -m venv .venv
.venv/bin/pip install -e '.[dev]'
.venv/bin/python -m pytest -q
Description
Languages
Python
100%