Files
orchestration_engine/.agents/plans/iter-02-orchestration-engine/steps/step-K2.md
Jonathan Boniface 1ec939f4fd feat: build on kept work by reference with sources_from (ADR-0004 phase 2)
A request names work the Orchestration engine kept instead of carrying its
files: a record or latest link from an earlier document of links (checked,
and of the request's tenant and Customer case), latest/<work>, or an
Execution's id. The kept files and the record that the work completed are
the agent's sources. Nothing starts, and the caller is told why, when the
reference does not resolve to completed work it may use.

A sequence's next agent is given what was kept of the one before, the same
way.

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

2.5 KiB

Step K2: building on kept work by reference (ADR-0004, phase 2)

Built 2026-10-21 on feat/sources-from, from feat/delivery-store.

What was built

  • sources_from: a request names work kept earlier instead of carrying its files. It may be:
    • a link from an earlier document of links, its record or its latest: what a platform step maps from an earlier step's output. The signature is checked; the link must be of the request's tenant when the request names one, and of its Customer case when it names one;
    • latest/<work>: the newest completed Execution of that work in the request's Customer case;
    • an Execution's id in the request's Customer case.
  • What the agent is sent: the kept files as sources, with the Orchestration engine's record that the work completed (execution.json: status, Customer case, Execution, the request, the work). A request naming no Customer case takes the kept work's.
  • Nothing starts, and the caller is told why, when the reference resolves to nothing, to work that did not end completed, to another tenant or Customer case, when the link was changed, when nothing is kept here, or when sources is given as well. The reply is a completed task with {"status": "not_started", "reason": ...}.
  • The sequence on the same footing: an agent after another is given what was kept of the one before (Delivery.sources), as a request naming it in sources_from would be. Without a store, it is given the files relayed, as before.
  • Store.files, Delivery.resolve, Delivery.sources; the record execution.json moved to delivery.py.
  • The card offers sources_from.

Verified

  • 12 tests in test_sources_from.py: each of the three forms; a latest link followed to the newest work; a changed link, another tenant, another Customer case, nothing kept, work that ended with warnings, and sources with sources_from each starting nothing; a sequence's next agent given what was kept; the card.
  • 589 tests pass; ruff and mypy clean.
  • Deployed on the local platform; the card offers sources_from. No agent was run: the owner runs it through the platform.

Using it from the platform

A second workflow step on the Orchestration engine with work: operating_model and sources_from mapped from the first step's record; or, in a later workflow, sources_from: latest/solution_architecture with the Customer case. The operating model agent's own fields (who operates it, business outcomes) go in that step's scope.