Shadow answers show both bodies of each difference (secrets masked); a folded module is judged inside; the bus membership is carried (issue 1126, group fix/1126-shadow-shows) #112

2026-10-28T00:16:07Z

mesh-tools commented

2026-10-28 00:16:07 +00:00

Delivery group fix/1126-shadow-shows with mesh-host. Issue 1126 (L2 of design 47), notes 45-47.

Seed #531 was answered 'differs' by novox with 20 items no one could read further (the answer named resources, not contents), and ace, g14, shanks answered nothing.

delivery: ModuleDiffers.Bodies carries both bodies of every differing resource (20/module, 8 KiB/side, 256 KiB/answer, the rest named, CandidateAnswer.Note says so); every value under a secret-like key is masked at any depth; a mask says same / another seal of the same value / another value / differs.
frombus (A): a module the composition folds inside the node's own is judged there, never as removed (the 5 'removed' on #531 were this).
frombus (B): the node's own composition carries the bus membership it runs (as its sealed box), so an applied composition never drops novox's bus credential.

Security: secrets travel only in sealed, vault-sealed and secrets fields (the declaration contract forbids them in env), all masked; bus users are stripped before the comparison; plain content already travels in the clear by design.

Quick or thorough: thorough (show every difference, not the first; fix the kinds (A) and (B), not the instances).

Tests: rows in TestPlacement and TestInput, each failing without its fix. Review notes kept on 1126: no row for the 256 KiB cap and 8 KiB cut.

Reviewed-by: review-shows@shanks at 4e0c57771e

Delivery group fix/1126-shadow-shows with mesh-host. Issue 1126 (L2 of design 47), notes 45-47. Seed #531 was answered 'differs' by novox with 20 items no one could read further (the answer named resources, not contents), and ace, g14, shanks answered nothing. - delivery: ModuleDiffers.Bodies carries both bodies of every differing resource (20/module, 8 KiB/side, 256 KiB/answer, the rest named, CandidateAnswer.Note says so); every value under a secret-like key is masked at any depth; a mask says same / another seal of the same value / another value / differs. - frombus (A): a module the composition folds inside the node's own is judged there, never as removed (the 5 'removed' on #531 were this). - frombus (B): the node's own composition carries the bus membership it runs (as its sealed box), so an applied composition never drops novox's bus credential. Security: secrets travel only in sealed, vault-sealed and secrets fields (the declaration contract forbids them in env), all masked; bus users are stripped before the comparison; plain content already travels in the clear by design. Quick or thorough: thorough (show every difference, not the first; fix the kinds (A) and (B), not the instances). Tests: rows in TestPlacement and TestInput, each failing without its fix. Review notes kept on 1126: no row for the 256 KiB cap and 8 KiB cut. Reviewed-by: review-shows@shanks at 4e0c57771e8ce8b89987b0eaebdb8fc9e268c157

mesh-tools added 2 commits 2026-10-28 00:16:08 +00:00

A candidate answer shows every differing resource, masked; a module folded in the node's own is judged there; the node's own carries its bus membership as it runs it (issue 1126, seed #531 ) b31c4580aa

novox's answer to seed #531 named 15 resources by id alone, so why each differed
was guessed. ModuleDiffers.Bodies keeps every differing resource with both
bodies, each value under a key a secret could be in masked (the same, another
seal of the same value, another value). The five old-form modules read
'removed' because the agent also lists them by module from the declaration kept
before the switch; they are judged inside the node's own. And the node's own
lacked bus-membership, which only the controller composes from its store: the
membership the node runs is carried, until the grants part hands it sealed.

Bound the bodies an answer shows, naming the rest (issue 1126)

mesh/delivery merged: source.main moved to novox/mesh-sdk@03da552cb331

Details

mesh/delivery-group group fix/1126-shadow-shows merged: every member is merged

Details

mesh/check pass 4e0c57771e8c on 47eb1009921d | unit 2980 run, 270 kept, 36 skipped | integration 2999 run, 302 kept, 29 skipped | over bound: unit (sl…

4e0c57771e

mesh-tools commented

2026-10-28 00:16:11 +00:00

Delivery novox/mesh-sdk@4e0c57771e8c — merged since 2026-10-28T00:21:50Z

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

Group fix/1126-shadow-shows: novox/mesh-host@047237c911, novox/mesh-sdk@4e0c57771e

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

Transitions

2026-10-28 00:16 (new) → proposed (announced): novox/mesh-sdk#112's head announced
2026-10-28 00:16 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-10-28 00:21 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-sdk@4e0c57771e8c` — **merged** since 2026-10-28T00:21:50Z **Source** — source.main moved to novox/mesh-sdk@03da552cb331. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `fix/1126-shadow-shows`: novox/mesh-host@047237c911a4, novox/mesh-sdk@4e0c57771e8c - composed together: pass — the checker's verdict at the members' heads (c3a8fe6b4bd5) **Transitions** - 2026-10-28 00:16 (new) → proposed (announced): novox/mesh-sdk#112's head announced - 2026-10-28 00:16 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-10-28 00:21 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 03da552cb3 into main

2026-10-28 00:21:48 +00:00

mesh-tools deleted branch fix/1126-shadow-shows

2026-10-28 00:21:48 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-sdk#112