The approval mark and every-event: the prepare's answers, so both parts are complete for develop with milestone G #542

2026-11-11T02:27:00Z

mesh-tools commented

2026-11-11 02:27:00 +00:00

Step 0b of playbook 07 for the two parts delivered with design 47's milestone G (design 46 milestone 7, the approval mark; design 34 every-event): the 25 design questions their prepare found, each answered as a design line citing its id, and the one review round of step 0b (four reviewers by architectural domain) answered whole.

The approval gate follows the build a bundle actually runs (its fingerprint, the catalog entry by fingerprint), never the version placed, so a delivery that drops a mark cannot let an old bundle run unasked.
The approvals state is in the tool runner's old state section (a foundation part), fixed 64 MiB; recording a warrant is a kept call (ADR 0668 §7), with a record action by hand.
Readings are judged older by the runner's fingerprint; an added subscribe deny passes as a narrowing; the node-engine reads withheld subjects through the seat mesh-grants' new read withheld.
A read of a file's mode where the reading account cannot enter is built on the seat node-files (ADR 0394 §9 retired node-reads).
Only the indexer reads manifests (the operator, 2026-11-11); no new decision records.

Reviewed-by: review-security-and-upgrade, review-seams-and-tools, review-running-and-testing, review-health-and-events (step 0b round) for lead-47@shanks at 8e9116469a

https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

Step 0b of playbook 07 for the two parts delivered with design 47's milestone G (design 46 milestone 7, the approval mark; design 34 every-event): the 25 design questions their prepare found, each answered as a design line citing its id, and the one review round of step 0b (four reviewers by architectural domain) answered whole. - The approval gate follows the build a bundle actually runs (its fingerprint, the catalog entry by fingerprint), never the version placed, so a delivery that drops a mark cannot let an old bundle run unasked. - The `approvals` state is in the tool runner's old `state` section (a foundation part), fixed 64 MiB; recording a warrant is a kept call (ADR 0668 §7), with a `record` action by hand. - Readings are judged older by the runner's fingerprint; an added subscribe deny passes as a narrowing; the node-engine reads withheld subjects through the seat mesh-grants' new read `withheld`. - A read of a file's mode where the reading account cannot enter is built on the seat node-files (ADR 0394 §9 retired node-reads). - Only the indexer reads manifests (the operator, 2026-11-11); no new decision records. Reviewed-by: review-security-and-upgrade, review-seams-and-tools, review-running-and-testing, review-health-and-events (step 0b round) for lead-47@shanks at 8e9116469a0aab2fb70b8a076a004c924257e82b https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

mesh-tools added 2 commits 2026-11-11 02:27:00 +00:00

Answer the prepare's questions on the approval mark and marked waits 28c22c65cb

Each of the 25 recommendations becomes a design line with its question id,
so the builders find every field, test and source named; the live readings
of the credentials go into the gate's stated bound.

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

Answer step 0b's review of the approval mark and marked waits

mesh/delivery merged: source.main moved to novox/hq@f1fe609b3e85

Details

mesh/check being carried to 8e9116469a0a on f1fe609b3e85 | from fbd7981b7be2

8e9116469a

The served version comes from what the bundle runs and a reading from the
runner that made it, so no placement or clock lifts a deny; the runner's
state takes the old form the bus module can create; kept calls stay open on
their key; and the closed directory's mode is read by node-files.

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

mesh-tools commented

2026-11-11 02:27:04 +00:00

Delivery novox/hq@8e9116469a0a — merged since 2026-11-11T08:56:24Z

Source — source.main moved to novox/hq@f1fe609b3e. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-11-11 02:27 (new) → proposed (announced): novox/hq#542's head announced
2026-11-11 02:27 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-11 08:56 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/hq@8e9116469a0a` — **merged** since 2026-11-11T08:56:24Z **Source** — source.main moved to novox/hq@f1fe609b3e85. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-11 02:27 (new) → proposed (announced): novox/hq#542's head announced - 2026-11-11 02:27 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-11 08:56 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 merged commit f1fe609b3e into main

2026-11-11 08:56:23 +00:00

mesh-tools deleted branch design/34-wait-on-any-event

2026-11-11 08:56:23 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#542