45 lines
4.3 KiB
Markdown
45 lines
4.3 KiB
Markdown
# Steps T1, T2, T5 to T13: the Workflow, from a written operating spec
|
|
|
|
Built 2026-10-13, on the Execution engine as it stood that day (not yet committed there).
|
|
|
|
## What was built
|
|
|
|
- **The Workflow** (`app/operating_model/workflow.py`): five Phases, six Deliverables, each with its Specialist, sections and data file; the validation policy; the views; the account of a Change request; the card.
|
|
- **The operating spec's catalogue** (`skills/operating-scoping/`): 32 fields, read by the engine's spec reader. The provider bundle supplies the Cloud provider and the currencies.
|
|
- **The capability catalogue** (`skills/operating-capabilities/`): 17 entries in five domains, each citing frameworks from a register of nine. `catalogue.py` refuses an entry that cites nothing or cites an unregistered framework, and proposes the entries that apply to a spec.
|
|
- **The chain** (`chain.py`): the checks on operational requirements and on capabilities.
|
|
- **The graph** (`graph.py`): its shape for the engine's graph tools, its refusals, findings, and the rendered responsibility matrix, organisation chart, and staffing and cost.
|
|
- **Staffing and cost** (`staffing.py`): the rate card's loader and checks, and the arithmetic.
|
|
- **Scenarios** (`scenarios.py`): five kinds, generated and traced by code, their verdicts written into `verdicts.json`.
|
|
- **The agent's folder**: eight role files and a shared protocol, `providers/gcp.yaml`, the `operating-chain` Skill, `app/main.py`.
|
|
- **106 tests**, among them seven whole Executions on the scripted runtime.
|
|
|
|
## Differed from the plan and the spec
|
|
|
|
- **The spec's files keep the engine's names,** `scope.yaml` and `scope.json`. The plan said `operating-spec.yaml`. The engine's spec support does not yet let a Workflow name them.
|
|
- **The inventory travels with the rest of the spec** to every Specialist, not as a separate `solution.json`. The engine's digest step (E6) is where that changes.
|
|
- **The graph holds no list of Capabilities.** They are the capability model's, named by id, so a failed Check can reopen who does the work without reopening what the work is.
|
|
- **The currencies a spec may state are listed in the provider bundle,** so the engine refuses another at the start. A test keeps the list the same as the rate card's conversion rates.
|
|
- **A Role on business hours is as small as its work.** The spec's formula applied the minimum roster to every Role; the plan, which the owner approved, applies it only to hours wider than a working day. The plan was followed.
|
|
- **A Check that depends on a finding is recorded as `waits_on_finding`.** The validator gives it `not_verifiable`; code rewrites the verdict when the validation is submitted. Left as `not_verifiable`, the engine's router reopened the capability model for it, again and again: a finding is not a gap in the model.
|
|
- **A scenario's verdicts are written into `verdicts.json` by code,** as Checks whose ids begin `SC-`, and the walk-through as a whole is the file's `dry_run`. A failed scenario is therefore a failed Check to the router, which reopens the graph.
|
|
- **The matrix shows both parts** when one Role is accountable and responsible for a Capability (`A/R`).
|
|
|
|
## Not built
|
|
|
|
- **The digest** (T3, T4). An Execution starts from an operating spec that is already written. Nothing reads the solution architecture agent's files yet.
|
|
- **A guide template** (T11). The packager has its sections and its instructions.
|
|
- **Evaluation** (T14). Nothing has run with a real model: no role file, Skill or catalogue entry has been read by one.
|
|
- An interactive Execution and a Change request are not tested here; the engine's own tests cover both on other Workflows.
|
|
- The capability catalogue's references are drafted from general knowledge and marked `unverified`. Nobody has checked them against the frameworks.
|
|
- The rate card's figures are placeholders.
|
|
|
|
## What it found in the engine
|
|
|
|
- The engine was not typed as a package (`py.typed` added there), so this repository could not be type-checked against it.
|
|
- An editable install of the engine is invisible to the type checker unless made with `editable_mode=compat`.
|
|
|
|
## Verified
|
|
|
|
`pytest -q`: 106 passed. `ruff check .`, `ruff format --check .`, `mypy .` (20 files): clean. The engine's suite still passes (521). `git status` in the solution architecture agent shows the same nine modified files as before any of this work began.
|