Answer A-489a and A-489b: every end of an ask is written, said and acknowledged; a build module that cannot say a step's end fails its own test

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
2026-11-19 15:36:25 +01:00
parent eb0e67753f
commit 7d2c80b9c0
@@ -2033,3 +2033,14 @@ the principle that settles it, cited as "design 47 G A-n".
module cannot judge or run it now) still leaves it unacknowledged for the bus to give again, and a give-back is no
delivery that counts toward poison. (Live 2026-11-19: 56 messages held on `SEAT_NODE_BUILD_NODE`, ack floor 0, the
sdk's build waiting on three of them since 13:24.)
- **A-489a** (A-489; principle 3) Every way an ask ends goes through A-489: a decline, a refused run, a refused drop and an
ask on its last delivery (`delivered` at the seat's max-deliver, run or not) each write their end, say it as
`step-ended` (could not run, poison when a run of it started, out of its deliveries when none did) and are then
acknowledged; an end that could not be written is given back, never acknowledged. An ask the module cannot read and
that carries no id has no key to write: it is acknowledged with its journal line, which names its stream sequence, as
its only record.
- **A-489b** (principle 3; fix-a-bug-met-twice) A build module whose steps cannot say a step's end fails its own test: the
build modules' conformance kit has a case that refuses `AskSteps` without the end's publish or the node, every build
module's test runs it, and the catalog's failure-kit check refuses a build module whose tests do not. A step ask is never
the first place this is found. `mesh-build-node` has the need `node-build-node` alone, as `mesh-build-go` has
`node-build-go`.