mesh-build-go runs a checking program over a change's heads (issue 1921, B0) #622

2026-11-06T22:58:56Z

mesh-tools commented

2026-11-06 22:58:56 +00:00

This member. mesh-build-go: a run ask builds a checking program once per key, lays every head read-only (bound after the workspace), asks its input of the checker seat's verb input (manifest invokes), runs it shut off, and answers its last line, bounded at 256 KiB. An ask it cannot read is answered on its step key as refused, never only logged. Kept programs and composers: build_go_kept, build_go_kept_drop, and a sweep of those unused for 30 days. compose keeps seats. 287 test functions (49 integration). The manifest validator accepts the changed manifest in both cases; all 29 checks/* pass.

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 c8bcb2cdf5

https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

**This member.** mesh-build-go: a `run` ask builds a checking program once per key, lays every head read-only (bound after the workspace), asks its input of the checker seat's verb `input` (manifest `invokes`), runs it shut off, and answers its last line, bounded at 256 KiB. An ask it cannot read is answered on its step key as refused, never only logged. Kept programs and composers: `build_go_kept`, `build_go_kept_drop`, and a sweep of those unused for 30 days. compose keeps `seats`. 287 test functions (49 integration). The manifest validator accepts the changed manifest in both cases; all 29 `checks/*` pass. 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 c8bcb2cdf5672239ab37e3b0cce1619403b83c04 https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

mesh-tools added 6 commits 2026-11-06 22:58:57 +00:00

Answer an ask the build module cannot read on its step key as refused (issue 1921, seams must 1) 0220dfa92b

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

Kept composers and programs get a list tool, a drop tool and a sweep (issue 1921, seams must 2) 428ef8bbe5

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

A run ask builds a checking program once and runs it over its heads and input; compose keeps seats (issue 1921, C1-C3) fa73674e22

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

Bind a run's heads read-only over its workspace, read its input from the state the ask names, and prove the kept programs' sweep (issue 1921, review round 1) da1356cd7c

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

Fail a run step whose answer is over the bus's value limit, naming its size (issue 1921, review round 1) 608c4d4be6

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

mesh-build-go asks a run's input of the seat verb the ask names, and reads no checker state (issue 1921, B0 review round 1)

mesh/delivery merged: source.main moved to novox/mesh-catalog@f2b332de73d6

Details

mesh/delivery-group group feat/b0-checking-program merged: every member is merged

Details

mesh/check being carried to c8bcb2cdf567 on f2b332de73d6 | from 980ade933853, hq 885099eebbbd, mesh-delivery 2d201f781ced, mesh-sdk c1b50e99a639

c8bcb2cdf5

The operator's answer: reading mesh-delivery-checker.inputs broke ADR 0596 §2. The manifest drops that read and invokes
seat:mesh-delivery-checker.input; the run step asks the verb through the runtime (stdio.Ask) and takes only the bytes
the ask names (delivery.RunInput.Read).

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

mesh-tools commented

2026-11-06 22:59:03 +00:00

Delivery novox/mesh-catalog@c8bcb2cdf567 — merged since 2026-11-07T00:32:48Z

Source — source.main moved to novox/mesh-catalog@f2b332de73. 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@ec71485755, novox/mesh-catalog@c8bcb2cdf5, novox/mesh-delivery@35b800aaef, novox/mesh-sdk@1b073c23c2

composed together: pass — the checker's verdict at the members' heads (ee1c71a7e59b)

Transitions

2026-11-06 22:58 (new) → proposed (announced): novox/mesh-catalog#622's head announced
2026-11-06 22:59 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.

**Delivery** `novox/mesh-catalog@c8bcb2cdf567` — **merged** since 2026-11-07T00:32:48Z **Source** — source.main moved to novox/mesh-catalog@f2b332de73d6. 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-catalog#622's head announced - 2026-11-06 22:59 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-tools commented

2026-11-06 23:41:04 +00:00

mesh-delivery: not merged. The merge of this pull request into main at c8bcb2cdf5 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 c8bcb2cdf5672239ab37e3b0cce1619403b83c04 was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.

mesh-tools merged commit f2b332de73 into main

2026-11-07 00:32:47 +00:00

mesh-tools deleted branch feat/b0-checking-program

2026-11-07 00:32:47 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#622