Design 47 H2: H-A-398, an unfinished mover is placed by the seat verb place-unfinished
This commit is contained in:
@@ -229,3 +229,11 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
|
||||
steps with no taken-at: a taken ask's put surely landed and its holder takes an id once (ADR 0668 §2), so putting it
|
||||
again under a new id would ask the work twice; an untaken one may never have been put, and its bound key, armed at
|
||||
the put, carries it from there (H-A-395). P3, ADR 0668 §2.
|
||||
- **H-A-398 (an unfinished mover is placed by a seat verb, 00:40)** §786, R5. The tools bundle reaches the runner's
|
||||
process by a seat verb, as every acting runner tool does: the seat mesh-pipeline-runner gains `place-unfinished`
|
||||
(input: the unfinished entry's key and why; answer: the pipeline's key), which puts the mover in a pipeline of its own
|
||||
at once; its key is `<branch>.<revision>.unfinished.<module>`, after the run and publish key forms. No mark in a
|
||||
state watched by the process (a call that needs an answer is a verb, P-NATS-native;
|
||||
tools-are-how-a-module-is-spoken-to). The contract row is the mesh-delivery developer's (mesh-delivery-contracts,
|
||||
regenerated). §786's "could-not-run" end is read as the pipeline outcome failed (a could-not-run step ends it so);
|
||||
the outcomes stay passed, failed, refused, superseded, cancelled. P3.
|
||||
|
||||
Reference in New Issue
Block a user