Answer A-445: the bus keeper's A-376 path and its four manifest lines go

This commit is contained in:
2026-11-16 09:51:57 +01:00
parent 9cf4d63c9c
commit 60872e67e9
@@ -1222,3 +1222,7 @@ the principle that settles it, cited as "design 47 G A-n".
- **A-443a** (A-443; principles 3 and 7) A step given up at its bound is not cancelled through the SDK, whose bus calls
take no context: its call ends at the SDK's own bound of the ask, and distribution logs, by the step's name, that it
gave the step up and, later, when the call behind it ended and how. No context is added to the SDK for it.
- **A-445** (A-379 replaces A-376 and A-378 for the start; principle 7) The bus keeper reads nothing of the seat
`mesh-catalog` before the first views: its A-376 path, and the manifest's consumes of `seat:mesh-catalog.views.modules`
and `.views.manifests` and invokes of `seat:mesh-catalog.modules` and `.manifests`, go, since the seat offers neither
those views nor those verbs and the validator refuses them.