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>
24 lines
1.2 KiB
Markdown
24 lines
1.2 KiB
Markdown
# Plans
|
|
|
|
One directory per iteration. Each holds the plan for that iteration and, for finished steps, the record of what was built.
|
|
|
|
## Iterations
|
|
|
|
| # | Directory | Status | What it is |
|
|
| --- | --- | --- | --- |
|
|
| 1 | `iter-01-execution-engine/` | steps 1 to 6 built on 2026-10-13; 7 planned | The Execution engine: brought from the Reference, given a Workflow, and proved on a toy Workflow and on the Reference's own. |
|
|
| 2 | `iter-02-orchestration-engine/` | F1 proposed; F2 and F4 built on 2026-10-20; K1 (ADR-0004) built on 2026-10-21 | The Orchestration engine: routes each request to the agent for its work and relays everything back. |
|
|
|
|
The plan across both repositories is `../tom_analysis/IMPLEMENTATION_PLAN.md`.
|
|
|
|
## Files in an iteration
|
|
|
|
- `MAP.md`: the intent, each step's status, and the sources of truth to read.
|
|
- `steps/step-N.md`: written when step N is finished. What was built, what differed from the plan, and how it was verified. A step with no file is not done.
|
|
|
|
## Working in an iteration
|
|
|
|
1. Read `MAP.md` and the sources of truth it names.
|
|
2. Build the step until its "done when" holds and `pytest`, `ruff check`, `ruff format --check` and `mypy` all pass.
|
|
3. Write `steps/step-N.md` and set the step's status in `MAP.md`.
|