Design 47 G: the lead's answers A-469t, A-469u (one shared form; the four run verbs) #669
@@ -1696,3 +1696,14 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
do not apply.
|
||||
- **A-469s** (G-24 DMC-20; §720; principle 1) The assigner's manifest gains the `invokes` entry `seat:node-build-go.drop`
|
||||
beside §720's `consumes` entries.
|
||||
- **A-469t** (G-24 C1; §729, A-468d, A-468e, A-469q; principles 7 and 8) `shared` is always a list, of one definition
|
||||
`Shared` `{machine, run, ask, asked-by}`, `machine` and `asked-by` optional: a composition step's list holds one entry
|
||||
per machine, a test step's one entry with no machine. `mesh-wants` keeps that definition once, and its `step-ended`
|
||||
and `step-progress` both name it; `mesh-pipeline-runner`'s `StepResult` names the same form.
|
||||
- **A-469u** (G-24 C1; §728, A-469f; principles 4 and 8) The four verbs are `compositions` and `compositions-drop` on
|
||||
`mesh-wants`, `test-runs` and `test-runs-drop` on `mesh-pipeline-runner`, each reached by its tool `assigner_<verb>` or
|
||||
`runner_<verb>`; class `read` and `act`, no callers of their own (§391's default, as `cancel` and `rerun`). A read
|
||||
answers `{runs, fill}`: each run the key's value under §719's or §725's field names plus `key`, the outcome's words in
|
||||
`said`, a composition reader a `StepRun` with its ask `id` (A-468), a test reader `{pipeline, artifact}`, `verdict` a
|
||||
free object, a test run's `packages` `[{package, digest}]` and `gone` with its words when the object is gone. A drop
|
||||
answers the entry it deleted plus `ended`, the readers it ended.
|
||||
|
||||
Reference in New Issue
Block a user