Answer A-214 and A-215: fill through state.info; what widens

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 5f761c16cd
commit fffad9f578
1 changed files with 7 additions and 0 deletions
@@ -140,3 +140,10 @@ the principle that settles it, cited as "design 47 G A-n".
  revision before its take-in, as §16 says; A-86 holds only for `KeepInput`, which the indexer's `input` verb calls
  for a run on request's asker. The run's input and job, what holds the pending revision meanwhile, and how a non-trunk
  branch's pending revision and groups are made go to design lines.
+- **A-214** (§366, §623; principle 7) `show` and `kept` read each store's fill through the bundle's state call
+  `mesh/state.info` (§623), as the forge module's read tool does; the runner's process writes nothing for it.
+  `pipeline-failed` takes scope `merge`, id the commit.
+- **A-215** (§71, §275, §335, A-207; principles 3 and 7) For `widens`, the pipeline's own revision (the candidate) is
+  compared with the branch's newest revision: an acting rule widens when an entry's `Acts` gains a rule, or a rule's
+  `on` now names more, or its `bound` is longer; a credential widens when an entry's manifest names an own secret or
+  provision of a credential it did not name before; permissions come from `grants-for`.