Following the operator's direction on 2026-10-11: the mesh proves which machine called a module (issue 365), not which agent on it, and the operator puts any design for agents after a vendor-neutral inference layer. So a proposal is reviewed by the knowledge base itself, through a fresh judgement with no tools that sees only the record, its links and the rules (as the issue tracker's triage), via claude_code_judge today and the inference layer once it exists. ADR 0290 updated in place with a dated note (option 3 added, option 2 rejected, rule 4, rule 6, consequences); to-be 55 §1, §5, §9, §10 and the design index match. The code change follows under issue 425.
Checks: merge-check.sh passes locally.
Following the operator's direction on 2026-10-11: the mesh proves which machine called a module (issue 365), not which agent on it, and the operator puts any design for agents after a vendor-neutral inference layer. So a proposal is reviewed by the knowledge base itself, through a fresh judgement with no tools that sees only the record, its links and the rules (as the issue tracker's triage), via claude_code_judge today and the inference layer once it exists. ADR 0290 updated in place with a dated note (option 3 added, option 2 rejected, rule 4, rule 6, consequences); to-be 55 §1, §5, §9, §10 and the design index match. The code change follows under issue 425.
Checks: merge-check.sh passes locally.
Deliverynovox/hq@d5eaba135988 — delivered since 2026-10-11T09:27:23Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-11 09:21 (new) → proposed (announced): novox/hq#311's head announced
2026-10-11 09:22 proposed → checked (checked): the verdict names this commit
2026-10-11 09:22 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 09:27 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-11 09:27 published → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@d5eaba135988` — **delivered** since 2026-10-11T09:27:23Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-11 09:21 (new) → proposed (announced): novox/hq#311's head announced
- 2026-10-11 09:22 proposed → checked (checked): the verdict names this commit
- 2026-10-11 09:22 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 09:27 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-11 09:27 published → delivered (done): nothing for a walk to move
The commit's note under `refs/notes/mesh-plan` keeps every transition: `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.
Following the operator's direction on 2026-10-11: the mesh proves which machine called a module (issue 365), not which agent on it, and the operator puts any design for agents after a vendor-neutral inference layer. So a proposal is reviewed by the knowledge base itself, through a fresh judgement with no tools that sees only the record, its links and the rules (as the issue tracker's triage), via claude_code_judge today and the inference layer once it exists. ADR 0290 updated in place with a dated note (option 3 added, option 2 rejected, rule 4, rule 6, consequences); to-be 55 §1, §5, §9, §10 and the design index match. The code change follows under issue 425.
Checks: merge-check.sh passes locally.
Delivery
novox/hq@d5eaba135988— delivered since 2026-10-11T09:27:23ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.