After G: a full delivery cycle by hand, as the operator asked on 2026-11-17

This commit is contained in:
2026-11-17 09:22:37 +01:00
parent 36d5b50d5b
commit d84b7cbb57
@@ -3,7 +3,7 @@ layer: to-be
status: in-progress
design: 47
milestone: G
updated: 2026-11-16
updated: 2026-11-17
decisions:
- "ADR 0667"
---
@@ -60,6 +60,18 @@ deals with it, which is how the list is kept true.
`invokes`, `uses` and the `views` forms stay in a manifest at all is asked with the research on the mesh's
accounts, and "each fact is declared in one place".
13. **A full delivery cycle by hand** (the operator, 2026-11-17 about 09:00: "make sure that every part of the
build-and-delivery system is also doable by hand via mcp tools", "so you can fully take control of a full cycle";
asked when, "after G"; principle 4). A survey of 2026-11-17 found, along the cycle merge, the gate's source,
take-in, entries, pipeline, steps, release, wants, grants, put and running: about 52 acts a module does by itself
with no hand tool, about 110 bus states with no per-key clear and 26 with no read tool, all but one of about 25 capped
states with no fill against their cap, and 14 recoveries with no tool. One milestone: the SDK's state tools for
every declared state (read, fill against cap, clear a key, drop key-gone objects), the missing hand acts per module,
a summary of the pipeline runner's pipelines by outcome, `source-moved` and the runner's `ended` declared so they
can be waited on, and the catalogue check that refuses a module whose state or act has no tool. Also a consumer
composed from the union of the want's and the trunk's manifests, as grants already are (a bundle's new `consumes`
is unbound until a want names its build).
## Met during G's start (2026-11-14)
- **The seed of registrations** left out modules whose manifest lives in the application's own repository on its