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
2026-10-21 19:50:24 +01:00
2026-10-21 19:50:24 +01:00
2026-10-21 19:50:24 +01:00
2026-10-21 19:50:24 +01:00
2026-10-21 19:50:24 +01:00

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
No description provided
Readme 467 KiB
Languages
Python 100%