Answer A-293: in by-entries mode a failed newest build is said as a refused key on the builder's build-ended event

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 17:05:37 +01:00
parent 852a0d1163
commit 66d37b8f30
1 changed files with 4 additions and 0 deletions
@@ -434,3 +434,7 @@ the principle that settles it, cited as "design 47 G A-n".
  'not yet'); every later change is said as `manifest-reads-changed` at once. A say the bus does not take is said
  again within the same link through the SDK's bus retry until the bus takes it, and each failed attempt is written
  to the engine's journal with the event's name; the held-for-the-next-link form stays only for a link that is lost.
+- **A-293** (§421, §628, ADR 0593 §6, issue 1966 U1/U8; principles 1 and 3) In by-entries mode the node-engine still
+  says a placed module's newest build that ended failed as a refused key with the build's words: it hears the
+  builder's build-ended event for that fingerprint (an event, not a read of the builder's builds), so no reader waits
+  on a build that will never be done; a queued or running build stays unpublished.