Bus state by template: the judge's rules, manifest-accepted, the old-section count and the ledger account (issue 1966, B1) #146

2026-11-03T14:36:00Z

mesh-tools commented

2026-11-03 14:36:00 +00:00

Milestone B1 of issue 1966 (ADR 0595 §10 steps 2 and 4; design 25 § 12). One delivery group with mesh-sdk, mesh-tools and mesh-catalog on branch feat/bus-state.

The indexer's judge refuses bus state in requires that breaks a template's bounds, naming the module, the entry and the field; one local name is one form; the old state's message says what it accepts (0 is taken as 1), its behaviour unchanged (ADR 0579 §1).
The indexer says manifest-accepted with the bus-state entries whole for a newly accepted verdict (nothing consumes it before B2).
The indexer counts the modules on each old section (state oldsections, tool indexer_old_sections); the zero rule takes the count of the accepted set the last pass held, and is skipped, logged, when it cannot be read; the checker's judge counts from the trunk case, so the merge check refuses what take-in refuses.
The grants part composes one ledger account per module assignment asking for a ledger, publishing only on its ledger history and snapshot subjects (mesh-sdk's names); no membership binding is written in B1 (design 25 § 12.2: after created, B2).

Acceptance: issue 1966 notes 8 and 10 (AC7-AC11, AC20, AC21, AC27).
Test budget: the repository is over (805 unit, 71 integration before); not raised (804 unit), table cases only.
The last commit only pins the group's mesh-sdk head (f8bd12e) in place of the local replace; unit suites and vet re-run after it, and it was reviewed on its own.

Reviewed-by: reviewer-bus@shanks at 4bb790bedf

Milestone B1 of issue 1966 (ADR 0595 §10 steps 2 and 4; design 25 § 12). One delivery group with mesh-sdk, mesh-tools and mesh-catalog on branch feat/bus-state. - The indexer's judge refuses bus state in `requires` that breaks a template's bounds, naming the module, the entry and the field; one local name is one form; the old state's message says what it accepts (0 is taken as 1), its behaviour unchanged (ADR 0579 §1). - The indexer says `manifest-accepted` with the bus-state entries whole for a newly accepted verdict (nothing consumes it before B2). - The indexer counts the modules on each old section (state `oldsections`, tool `indexer_old_sections`); the zero rule takes the count of the accepted set the last pass held, and is skipped, logged, when it cannot be read; the checker's judge counts from the trunk case, so the merge check refuses what take-in refuses. - The grants part composes one ledger account per module assignment asking for a ledger, publishing only on its ledger history and snapshot subjects (mesh-sdk's names); no membership binding is written in B1 (design 25 § 12.2: after `created`, B2). Acceptance: issue 1966 notes 8 and 10 (AC7-AC11, AC20, AC21, AC27). Test budget: the repository is over (805 unit, 71 integration before); not raised (804 unit), table cases only. The last commit only pins the group's mesh-sdk head (f8bd12e) in place of the local replace; unit suites and vet re-run after it, and it was reviewed on its own. Reviewed-by: reviewer-bus@shanks at 4bb790bedffeeb4e94c0e95f0a89aa31527b8f33

mesh-tools added 10 commits 2026-11-03 14:36:00 +00:00

The judge refuses bus state in requires that breaks a template's bounds, naming the entry and the field (issue 1966 D1) 7ee7248fad

One local name is one form, and the old state says what it accepts: 0 is taken as 1 (issue 1966 D2) 9a508701ff

The indexer says manifest-accepted, with the bus-state entries whole, for a newly accepted verdict (issue 1966 D3) 756a3813e2

The indexer counts the modules on each old section, a tool reads it, and the judge refuses a section at 0 outside the foundation (issue 1966 D4) dd2e7c8e64

The grants part composes a ledger account per assignment of a module asking for a ledger, publishing only on its ledger histories and snapshots (issue 1966 D5) 07af86b153

The wanted accounts include the ledger kind, held in the tool runner's ledgers, in step with mesh-sdk's buscompose (issue 1966 D5b) 1ab0274547

The ledger account's subjects come from mesh-sdk's one naming of them (issue 1966 D5) 28a6858863

The checker's judge counts the old sections from the trunk case as the indexer does, so a change adding a section at 0 is refused at the merge check (issue 1966 D4) 2fdb0516cd

The zero rule takes the count of the accepted set the last pass held, and is not applied when it cannot be read (issue 1966 D4) aa98729457

Pin the group's mesh-sdk head f8bd12e in place of the local replace (issue 1966)

mesh/check pass 4bb790bedffe on 8f83608503da | unit 6460 run, 262 kept, 27 skipped | integration 6639 run, 264 kept, 35 skipped | over bound: unit, in…

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

Details

mesh/delivery-group group feat/bus-state merged: every member is merged

Details

4bb790bedf

mesh-tools commented

2026-11-03 14:36:04 +00:00

Delivery novox/mesh-delivery@4bb790bedffe — merged since 2026-11-03T15:24:38Z

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

Group feat/bus-state: novox/mesh-catalog@34ce2895dd, novox/mesh-delivery@4bb790bedf, novox/mesh-sdk@f8bd12e4b7, novox/mesh-tools@43d3fba501

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

Transitions

2026-11-03 14:36 (new) → proposed (announced): novox/mesh-delivery#146's head announced
2026-11-03 14:36 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-03 15:24 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-delivery@4bb790bedffe` — **merged** since 2026-11-03T15:24:38Z **Source** — source.main moved to novox/mesh-delivery@c4470f42dba9. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `feat/bus-state`: novox/mesh-catalog@34ce2895dd33, novox/mesh-delivery@4bb790bedffe, novox/mesh-sdk@f8bd12e4b7b1, novox/mesh-tools@43d3fba501d3 - composed together: pass — the checker's verdict at the members' heads (7bbdc38f1f86) **Transitions** - 2026-11-03 14:36 (new) → proposed (announced): novox/mesh-delivery#146's head announced - 2026-11-03 14:36 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-03 15:24 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 c4470f42db into main

2026-11-03 15:24:36 +00:00

mesh-tools deleted branch feat/bus-state

2026-11-03 15:24:37 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-delivery#146