diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 26053882..fb8429a5 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1088,3 +1088,11 @@ the principle that settles it, cited as "design 47 G A-n". an asker may have at most three asks open; principles 3 and 7) The operator channel keeps no count of open asks per asker and holds none back for room: every ask is offered when it is raised. The router's limit, the teller's own and the ask-again for a held-back ask (§394, §450) go; an ask still lapses at its expiry or ends at its answer. +- **A-425** (the operator, 2026-11-15 about 15:57 CET: "yes, remove the per-placement approve", after the lead proposed + it under propose-removing-a-wrong-rule: a person's yes for every placement holds work on a form, against "merges and + deliveries need no approval"; principles 3 and 7) A proposal whose verdict passes is applied by the assigner at once, + with no ask of the operator, when it only places, pins, unpins, holds, unholds, decides or configures. A proposal + that takes a module off a node, removes a node, or whose verdict says a node would stop or remove a module or its data, + is still asked of the operator, as are the asks of a module whose moves a person takes. Each applied proposal is said + as an event and in the assigner's log, naming who proposed it and why. The decision record that made every proposal + wait on the operator's yes gets a new record saying so once the knowledge base admits callers again.