This member.go/delivery: StepAsk.Run and RunJob (a program built from a change and run over the heads), RunKey, RunAnswer; the input by reference, bounded at 256 KiB, asked of the checker seat's verb input (RunInputAsk, RunInputAnswer, RunInput.Read checks the digest); Verdict.JudgedBy. composer.Request.Seats kept through decode, fill and marshal. go/buildstepAskWhat names a run ask. go/catalogue checker seat defines input. The types stay in go/delivery for B0 (the operator, 2026-11-06); the registry milestone moves them into mesh-delivery-contracts (ADR 0634 §4). Unit 604, integration 30, unchanged.
Milestone 47/B0 (ADR 0644: the delivery's own parts checked and delivered by their own change, its one delivery first; issue 1921; design 47, row B0). A delivery group of four, pushed together: mesh-sdk, mesh-delivery, mesh-catalog, hq, each on its B0 branch.
The ordering window (said, as ruling Q5 asks). mesh-build-go invokes the checker's new verb input, so the module graph delivers mesh-delivery-checker first. Until the new mesh-build-go reaches a build node, a check's run ask to an old build module is dropped; the checker puts it again after 5 minutes and fails the check after 5 more, naming the missing job run. Loud, never silent; milestone G's acting rule for the build step closes it.
Review. One review of all four members (hq playbook 07, three rounds), by mesh-code-reviewer: round 1 found four faults (heads not read-only, facts too large, the design not as built, the milestone file), round 2 approved the three code members and traced which manifest validator judges the two changed manifests in this check (cmd/mesh-judge built at this group's mesh-delivery head with its mesh-sdk head: accepts) and at the take-in (the indexer built at the merged revision: accepts), round 3 approved hq. The seams-and-tools review's three musts on the prepare are met in the code (read by round 1). The operator chose the checker verb for the input (ADR 0596 §2) on 2026-11-06.
Tests. Every new row fails with its effect taken out. Integration rows were run once locally against an embedded bus, as playbook 07 allows: the checker's 8, mesh-build-go's new bus row under real bubblewrap.
**This member.** `go/delivery`: `StepAsk.Run` and `RunJob` (a program built from a change and run over the heads), `RunKey`, `RunAnswer`; the input by reference, bounded at 256 KiB, asked of the checker seat's verb `input` (`RunInputAsk`, `RunInputAnswer`, `RunInput.Read` checks the digest); `Verdict.JudgedBy`. `composer.Request.Seats` kept through decode, fill and marshal. `go/buildstep` `AskWhat` names a run ask. `go/catalogue` checker seat defines `input`. The types stay in `go/delivery` for B0 (the operator, 2026-11-06); the registry milestone moves them into `mesh-delivery-contracts` (ADR 0634 §4). Unit 604, integration 30, unchanged.
Milestone 47/B0 (ADR 0644: the delivery's own parts checked and delivered by their own change, its one delivery first; issue 1921; design 47, row B0). A delivery group of four, pushed together: mesh-sdk, mesh-delivery, mesh-catalog, hq, each on its B0 branch.
**The ordering window (said, as ruling Q5 asks).** mesh-build-go invokes the checker's new verb `input`, so the module graph delivers mesh-delivery-checker first. Until the new mesh-build-go reaches a build node, a check's `run` ask to an old build module is dropped; the checker puts it again after 5 minutes and fails the check after 5 more, naming the missing job `run`. Loud, never silent; milestone G's acting rule for the build step closes it.
**Review.** One review of all four members (hq playbook 07, three rounds), by mesh-code-reviewer: round 1 found four faults (heads not read-only, facts too large, the design not as built, the milestone file), round 2 approved the three code members and traced which manifest validator judges the two changed manifests in this check (cmd/mesh-judge built at this group's mesh-delivery head with its mesh-sdk head: accepts) and at the take-in (the indexer built at the merged revision: accepts), round 3 approved hq. The seams-and-tools review's three musts on the prepare are met in the code (read by round 1). The operator chose the checker verb for the input (ADR 0596 §2) on 2026-11-06.
**Tests.** Every new row fails with its effect taken out. Integration rows were run once locally against an embedded bus, as playbook 07 allows: the checker's 8, mesh-build-go's new bus row under real bubblewrap.
Reviewed-by: b0-review@shanks at 1b073c23c2a54a4b853de8d8af9165e7afe75e6a
https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
A run ask has a program built at a commit and run in the build seat's
sandbox over named heads, its input kept by the asker by digest and
measured against a bound before asking (ADR 0644, ADR 0656; design 47's
ask run). The checker asks it for the checking program in milestone
47/B0.
Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
A build module that fills a request re-marshals it, and without the
field it dropped the seat list the trunk's manifest validator reads, so
the validator never got one (milestone 47/B0, ADR 0636 §4, ADR 0644).
Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
The verdict gains judged-by: where the checking program was built, the
key its build is kept under and the heads it read, so the checker's
reads say who judged a check (ADR 0644, design 47's bootstrap delivery).
Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
The operator's answer: a build module reading the checker's state broke ADR 0596 §2. RunInput names the seat verb it is
served on (seat:<seat>.<verb>), RunInput.Read asks it and takes only the bytes named, and the seat
mesh-delivery-checker defines the verb input (RunInputAsk, RunInputAnswer).
Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
Deliverynovox/mesh-sdk@1b073c23c2a5 — merged since 2026-11-07T00:32:42Z
Source — source.main moved to novox/mesh-sdk@54aff0a3d9. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.
composed together: pass — the checker's verdict at the members' heads (ee1c71a7e59b)
Transitions
2026-11-06 22:58 (new) → proposed (announced): novox/mesh-sdk#170's head announced
2026-11-06 22:58 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-07 00:32 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/mesh-sdk@1b073c23c2a5` — **merged** since 2026-11-07T00:32:42Z
**Source** — source.main moved to novox/mesh-sdk@54aff0a3d920. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Group** `feat/b0-checking-program`: novox/hq@ec714857556d, novox/mesh-catalog@c8bcb2cdf567, novox/mesh-delivery@35b800aaef68, novox/mesh-sdk@1b073c23c2a5
- composed together: pass — the checker's verdict at the members' heads (ee1c71a7e59b)
**Transitions**
- 2026-11-06 22:58 (new) → proposed (announced): novox/mesh-sdk#170's head announced
- 2026-11-06 22:58 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-07 00:32 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: not merged. The merge of this pull request into main at 1b073c23c2 was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.
mesh-delivery: **not merged.** The merge of this pull request into main at 1b073c23c2a54a4b853de8d8af9165e7afe75e6a was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.
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.
This member.
go/delivery:StepAsk.RunandRunJob(a program built from a change and run over the heads),RunKey,RunAnswer; the input by reference, bounded at 256 KiB, asked of the checker seat's verbinput(RunInputAsk,RunInputAnswer,RunInput.Readchecks the digest);Verdict.JudgedBy.composer.Request.Seatskept through decode, fill and marshal.go/buildstepAskWhatnames a run ask.go/cataloguechecker seat definesinput. The types stay ingo/deliveryfor B0 (the operator, 2026-11-06); the registry milestone moves them intomesh-delivery-contracts(ADR 0634 §4). Unit 604, integration 30, unchanged.Milestone 47/B0 (ADR 0644: the delivery's own parts checked and delivered by their own change, its one delivery first; issue 1921; design 47, row B0). A delivery group of four, pushed together: mesh-sdk, mesh-delivery, mesh-catalog, hq, each on its B0 branch.
The ordering window (said, as ruling Q5 asks). mesh-build-go invokes the checker's new verb
input, so the module graph delivers mesh-delivery-checker first. Until the new mesh-build-go reaches a build node, a check'srunask to an old build module is dropped; the checker puts it again after 5 minutes and fails the check after 5 more, naming the missing jobrun. Loud, never silent; milestone G's acting rule for the build step closes it.Review. One review of all four members (hq playbook 07, three rounds), by mesh-code-reviewer: round 1 found four faults (heads not read-only, facts too large, the design not as built, the milestone file), round 2 approved the three code members and traced which manifest validator judges the two changed manifests in this check (cmd/mesh-judge built at this group's mesh-delivery head with its mesh-sdk head: accepts) and at the take-in (the indexer built at the merged revision: accepts), round 3 approved hq. The seams-and-tools review's three musts on the prepare are met in the code (read by round 1). The operator chose the checker verb for the input (ADR 0596 §2) on 2026-11-06.
Tests. Every new row fails with its effect taken out. Integration rows were run once locally against an embedded bus, as playbook 07 allows: the checker's 8, mesh-build-go's new bus row under real bubblewrap.
Reviewed-by: b0-review@shanks at
1b073c23c2https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
Delivery
novox/mesh-sdk@1b073c23c2a5— merged since 2026-11-07T00:32:42ZSource — source.main moved to novox/mesh-sdk@54aff0a3d9. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Group
feat/b0-checking-program: novox/hq@ec71485755, novox/mesh-catalog@c8bcb2cdf5, novox/mesh-delivery@35b800aaef, novox/mesh-sdk@1b073c23c2Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.mesh-delivery: not merged. The merge of this pull request into main at
1b073c23c2was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.