Design 47 H: lead answer H-A-117 (the check and recheck kinds stay in H1; the runs' input is mesh-wants') #785
@@ -500,3 +500,8 @@ Where two preparers disagreed, the chosen one is named.
|
||||
`take-in.taken` (it consumes the indexer's `take-in.taken` in place of the retired `manifest-accepted`, H-A-49) and
|
||||
looks at every module again as it does today; the finer wake on a mover's new entry is H2's with the builder's own
|
||||
lines. The mechanical changes SDK-C forces on the builder's seat-list calls are in scope. P1, P7.
|
||||
- **H-A-117 (build-modules developer, 04:57)** The build seats' step kinds `check` and `recheck` stay in H1: they carry
|
||||
the composer's and the validator's runs (a compose or run ask is kind `check` of the Go seat), and §753's queues are
|
||||
H2's to rename with the builder's lines; H-A-57 is narrowed to the checker's seat, its copies and its own verdict
|
||||
verb. The runs' input moves from the checker's `input` to the seat mesh-wants' `input`, which the assigner serves
|
||||
(H-A-34), not to mesh-catalog. P7; rules-are-weighed, said.
|
||||
|
||||
Reference in New Issue
Block a user