From 3868280be2aa8885c852a424e4fa4036798611e7 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 18 Nov 2026 02:21:59 +0100 Subject: [PATCH] Answer A-486: a tool for every pipeline-runner verb no tool reaches --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) 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 2471003f..23fa70c1 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 @@ -1971,3 +1971,9 @@ the principle that settles it, cited as "design 47 G A-n". it names: (a) "a container module" is any module with a `container` resource, since a container reads its secrets as its own account; (b) a process resource that names no `user` runs as root, as the service manager runs it, so it may read every own secret. (From the develop of ADR 0680 in the manifest validator.) +- **A-486** (G §83, §84; principle 4, a module's tools are its command line) Every seat verb of the pipeline runner + that no tool reaches gets one tool, named for its verb: `runner_start`, `runner_run`, `runner_accept` and + `runner_ask_again`, each asking `seat:mesh-pipeline-runner.` with the verb's own input and answering its + answer, refusing before it asks only what the verb itself refuses, as `runner_rerun` does; the hand act is recorded + by the verb. The seat has no verb `release`, so no tool is made for it. (From the prepare of the take-in of the + modules each node runs at builds placed by hand before G: a cancelled pipeline could not be started again.) -- 2.54.0