Answer A-412: the builder takes the entry's manifest digest bare, and a look that writes nothing says why

This commit is contained in:
2026-11-14 23:44:11 +01:00
parent 7981d72d9b
commit ee543b8601
@@ -993,3 +993,10 @@ the principle that settles it, cited as "design 47 G A-n".
builder consumes and is granted; principles 1 and 7) The builder reads the last `versions-filled` at its start from the
seat event's own kept stream, through the SDK's hearing of a kept event read from its first message, as any kept event
is heard; it reads nothing of `EVENTS` and needs no new grant.
- **A-412** (live, the build node 2026-11-14 23:40-23:41: the builder's claim of every build is refused, "is not a manifest
digest, 64 lowercase hex digits", since the indexer's catalog entry now says its manifest digest as `sha256:` and hex,
and the builder passes it on as it reads it, while its builds and its manifests are keyed by bare hex; a build asked
again then answers "wrote nothing … its log says why" with no why; principles 3, 7 and 8) The builder takes a catalog
entry's manifest digest in its bare form, through the contract's own reading of it, wherever it plans, claims or keys
a build; the form the entry says is the entry's. A look that writes nothing says why in the builder's log, for each
of its ends, and the answer to a build asked again carries that why.