Design 25 bindings-first-view §9: compose a bucket's binding from the bus module's list answer, breaking the registry circle (issue 1966) #549

2026-11-11T12:49:05Z

mesh-tools commented

2026-11-11 12:49:05 +00:00

Issue 1966 (the registry recovery), notes 203-204. The operator, 2026-11-11 13:30 CET in the terminal: "Shall I break the registry circle by letting the grants part take a bucket's binding from the bus module's existing list answer when the new binding field is missing?" — "Yes, build it".

New §9: when no entry of mesh-broker.list's answer carries binding (a bus module build from before this milestone), the grants part composes the binding of a held key-value or object-store entry from the answer's own fields (local-name, storage-type, template, bus-name); a stream or ledger entry stays unbound, said in the log. The bus module's own word, so ADR 0595 §1/§7 and ADR 0596 §2 hold.
§7: the "needs no edge" sentence is replaced: it missed that the bus module's own image build needs the registry's mirror, which needs the holder's state mirrors (the circle). §4, §6, §8 follow; the main file's acceptance row names §9's checks.

A design edit of a few lines (playbook 08 step 4): the operator's Approve of its merge is its review. go test ./... at the root passes.

Reviewed-by: the operator's Approve of this merge (design edit, playbook 08 step 4) at f65acb98c7

https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

Issue 1966 (the registry recovery), notes 203-204. The operator, 2026-11-11 13:30 CET in the terminal: "Shall I break the registry circle by letting the grants part take a bucket's binding from the bus module's existing list answer when the new binding field is missing?" — "Yes, build it". - New §9: when no entry of `mesh-broker.list`'s answer carries `binding` (a bus module build from before this milestone), the grants part composes the binding of a held key-value or object-store entry from the answer's own fields (local-name, storage-type, template, bus-name); a stream or ledger entry stays unbound, said in the log. The bus module's own word, so ADR 0595 §1/§7 and ADR 0596 §2 hold. - §7: the "needs no edge" sentence is replaced: it missed that the bus module's own image build needs the registry's `mirror`, which needs the holder's state `mirrors` (the circle). §4, §6, §8 follow; the main file's acceptance row names §9's checks. A design edit of a few lines (playbook 08 step 4): the operator's Approve of its merge is its review. `go test ./...` at the root passes. Reviewed-by: the operator's Approve of this merge (design edit, playbook 08 step 4) at f65acb98c7423f3dc414dcc2af6b7d52694c48d9 https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

mesh-tools added 1 commit 2026-11-11 12:49:05 +00:00

Compose a bucket's binding from the bus module's existing list answer, breaking the registry circle

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

Details

mesh/check checking f65acb98c742 on 1c6fe9611ccc

f65acb98c7

The bus module's new build cannot be built: its image needs the registry's
mirror, which the registry holder serves only with a state binding the grants
part never heard and waited for that very build to say. The operator chose
(2026-11-11 13:30 CET) to compose key-value and object-store bindings from the
fields the running bus module already answers, delivered with the grants part
alone. Records that §7's 'needs no edge' missed the bus module's own build
through the registry.

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

mesh-tools commented

2026-11-11 12:49:07 +00:00

Delivery novox/hq@f65acb98c742 — merged since 2026-11-11T12:50:10Z

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

Transitions

2026-11-11 12:49 (new) → proposed (announced): novox/hq#549's head announced
2026-11-11 12:49 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 12:50 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@f65acb98c742` — **merged** since 2026-11-11T12:50:10Z **Source** — source.main moved to novox/hq@1c6fe9611ccc. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-11 12:49 (new) → proposed (announced): novox/hq#549's head announced - 2026-11-11 12:49 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 12:50 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 1c6fe9611c into main

2026-11-11 12:50:08 +00:00

mesh-tools deleted branch design/25-bindings-from-the-list

2026-11-11 12:50:08 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#549