feat: working orhcestration engine
This commit is contained in:
36
docs/adr/0001-the-execution-engine-takes-a-workflow.md
Normal file
36
docs/adr/0001-the-execution-engine-takes-a-workflow.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
status: accepted
|
||||
---
|
||||
|
||||
# The Execution engine takes a Workflow
|
||||
|
||||
The reference is one agent: its engine and its subject, cloud solution architecture, are the same code. About ten of its modules name its Deliverables directly, some forty-five times: the router knows that a failed validation reopens the infrastructure code, the submission tool knows which Deliverable gets a diagram. A second agent on a different subject cannot use it as it stands.
|
||||
|
||||
We decide that the Execution engine names no Deliverable, no Phase, no Cloud provider and no subject. Everything about a subject is one value, a **Workflow**, given to the engine when an agent is assembled. An agent is the Execution engine and one Workflow.
|
||||
|
||||
A Workflow supplies:
|
||||
|
||||
- its Phases, its Deliverables and their Dependencies, and the checks each submission must pass;
|
||||
- what code adds to a Deliverable when it is submitted;
|
||||
- which Deliverable is validation, how its result is read, and what a failure reopens;
|
||||
- the facts a user approves a Phase from;
|
||||
- any fan-out of one Deliverable's work to further agents;
|
||||
- its final Deliverable, and what it adds to an Execution's record and to a reply;
|
||||
- the roles it requires, its local tools and its reviews;
|
||||
- the catalogue its spec is read against, and the adapters that digest sources into one;
|
||||
- its own settings.
|
||||
|
||||
Accepted by the owner on 2026-10-13.
|
||||
|
||||
## Considered Options
|
||||
|
||||
- **Copy the reference and edit it for each new subject:** rejected. Every engine fix would be ported by hand to every copy.
|
||||
- **A plug-in registry the engine discovers Workflows from:** rejected. One agent has one Workflow; passing a value is enough, and it can be read.
|
||||
- **Subclassing the engine per subject:** rejected. The points that differ are data and a few functions, and inheritance would let a subject override what the Ledger guarantees.
|
||||
|
||||
## Consequences
|
||||
|
||||
- The engine's tests need a subject. A toy Workflow of three Deliverables drives them.
|
||||
- The reference's own workflow is written as a Workflow in the engine's tests, to show the seam is wide enough for the case it came from. This shows nothing about results with real models.
|
||||
- A Workflow can run its own code at the points listed and nowhere else. A need that fits none of them is a change to this ADR.
|
||||
- Settings and paths that the reference resolves from its own repository are given by the agent.
|
||||
Reference in New Issue
Block a user