Engine v0.2: flow graph, datapoint states, gates, modes, overrides, deviations (RBT-WP-0007)
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: sonnet Assistant-Process: 295952@bnt-lap001 Assistant-Session: e93f64ad-516c-46eb-9666-aad8d300c477
This commit is contained in:
parent
3fc279a6ed
commit
60d983769f
13 changed files with 1017 additions and 22 deletions
|
|
@ -34,6 +34,10 @@ pack
|
|||
| **Step** | `todo`, `running`, `done`, `failed` (`skipped` for read-only) | Has it been applied? |
|
||||
| **Gate** | `open`, `passed`, `failed`, `waived` | Is the quality condition met? |
|
||||
|
||||
A datapoint becomes `ok` when the step or gate named in its `confirmed_by` passes. A gate must not
|
||||
require a datapoint (`datapoints_ok`) that it is itself `confirmed_by`: that is circular and the validator
|
||||
rejects it.
|
||||
|
||||
A v0.1 `parameter` is a datapoint that has a value type and is asked as a
|
||||
question. Steps `uses:` datapoints; steps may `produces:` datapoints
|
||||
(for example an artefact location).
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue