The lead's answer to a design question from G's join 11 (implement-the-design):
A-293 (§421, §628, ADR 0593 §6, issue 1966 U1/U8; principles 1, 3, 7): in by-entries mode the node-engine says a placed module's newest build that ended failed as a refused key with the build's words, hearing the builder's build-ended event (not reading its builds); the newest build is the last trunk build-ended event heard for the module; a later done end deletes the refused key; an end naming a branch moves nothing.
The lead's answer to a design question from G's join 11 (implement-the-design):
- A-293 (§421, §628, ADR 0593 §6, issue 1966 U1/U8; principles 1, 3, 7): in by-entries mode the node-engine says a placed module's newest build that ended failed as a refused key with the build's words, hearing the builder's build-ended event (not reading its builds); the newest build is the last trunk build-ended event heard for the module; a later done end deletes the refused key; an end naming a branch moves nothing.
hq checks (`go test ./...`) pass on this head.
https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Deliverynovox/hq@7c533965bfa6 — merged since 2026-11-12T16:24:59Z
Source — source.main moved to novox/hq@0d04a16560. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.
Transitions
2026-11-12 16:23 (new) → proposed (announced): novox/hq#586's head announced
2026-11-12 16:23 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-12 16:24 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@7c533965bfa6` — **merged** since 2026-11-12T16:24:59Z
**Source** — source.main moved to novox/hq@0d04a16560e4. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Transitions**
- 2026-11-12 16:23 (new) → proposed (announced): novox/hq#586's head announced
- 2026-11-12 16:23 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
- 2026-11-12 16:24 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The lead's answer to a design question from G's join 11 (implement-the-design):
hq checks (
go test ./...) pass on this head.https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Delivery
novox/hq@7c533965bfa6— merged since 2026-11-12T16:24:59ZSource — source.main moved to novox/hq@0d04a16560. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.