Answer A-425a: which proposals are asked is the assigner's config key ask-operator-for
This commit is contained in:
@@ -1096,3 +1096,11 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
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.
|
||||
- **A-425a** (A-425; the operator, 2026-11-15 about 16:00 CET: "this is all configuration, a simple, single mesh mcp
|
||||
call"; read live: the assigner declares only `outside-settle-seconds` and `outside-wait-minutes`, and asks every
|
||||
passing proposal in its code; principles 4 and 7) Which proposals the assigner asks of the operator is the assigner's
|
||||
declared config key `ask-operator-for`, a list of change kinds (`place`, `take-off`, `pin`, `unpin`, `hold`,
|
||||
`unhold`, `decide`, `config`, `add-node`, `remove-node`, and `stops` for a verdict that stops or removes a module or
|
||||
its data), set at mesh level with `mesh-config.config`; its default is A-425's: `take-off`, `remove-node`, `stops`.
|
||||
A proposal none of whose changes is listed is applied at once. The asks of a module whose moves a person takes stay
|
||||
as they are. A change of the key is said in the assigner's log at its next pass.
|
||||
|
||||
Reference in New Issue
Block a user