Research 082 graduated into ADR 0595 (a module asks the bus module for its kept data by a template, in requires), ADR 0596 (events subscribed, data asked through tools; no module reads another's bus state) and ADR 0597 (the ledger; the knowledge base is its first), all accepted 2026-11-03. Issue 1966.
One design per thing (playbook 02): the designs that already cover each area are amended, no new design is written.
Design 25 (the bus on NATS), new § 12: bus state as a provision of the bus module; the three layers and six templates with their fixed settings and options; who creates and how the binding reaches a module; the seat mesh-broker's verbs, events, conditions and fill; the ledger and apply in the tool runner; the calls package; the move and the build order; how each rule is checked.
Design 32 (what a module declares), § 4: bus state in requires, one form, no readers; events subscribed, data asked through the owner's tools.
Design 55 (the knowledge base): the records kept as the first ledger; no object bucket of sections, no state names, no stream versions, no commit rule of its own; the move, the rollback and the tests follow.
Glossary: Data domain gains bus state, storage type (Not: data type), configuration, template, option, ledger, operation, ledger effect, snapshot of a ledger's state; Core's bus entry gains bus module; Config gains template file; Homonyms gain configuration, snapshot, template, option, effect.
What the design settles that the records left to it: the bus module's events kept 30 days on its old streams section; only the owning module calls the ledger's apply; the knowledge base's rollback during its move; reviews as a bare stream. Left to the operator, noted on issue 1966: a margin for the condition full, an event of its own for drop and recreate, and a correction of fact for ADR 0595 §4.
go test ./... passes at the root.
Reviewed by architectural domain, three rounds (each design ends with the record):
Reviewed-by: review-security-and-upgrade@shanks at 0cd0cfd (approved round 2)
Reviewed-by: review-seams-and-tools@shanks at 476557deeb
Reviewed-by: review-running-and-testing@shanks at 0cd0cfd (approved round 3)
Reviewed-by: review-health-and-events@shanks at 0cd0cfd (approved round 3)
The commits after 0cd0cfd add only the review record, read and approved by review-seams-and-tools at 3d4e361; its one suggested line is in 476557d.
Research 082 graduated into ADR 0595 (a module asks the bus module for its kept data by a template, in `requires`), ADR 0596 (events subscribed, data asked through tools; no module reads another's bus state) and ADR 0597 (the ledger; the knowledge base is its first), all accepted 2026-11-03. Issue 1966.
One design per thing (playbook 02): the designs that already cover each area are amended, no new design is written.
- **Design 25 (the bus on NATS), new § 12:** bus state as a provision of the bus module; the three layers and six templates with their fixed settings and options; who creates and how the binding reaches a module; the seat `mesh-broker`'s verbs, events, conditions and fill; the ledger and `apply` in the tool runner; the calls package; the move and the build order; how each rule is checked.
- **Design 32 (what a module declares), § 4:** bus state in `requires`, one form, no readers; events subscribed, data asked through the owner's tools.
- **Design 55 (the knowledge base):** the records kept as the first ledger; no object bucket of sections, no state `names`, no stream `versions`, no commit rule of its own; the move, the rollback and the tests follow.
- **Glossary:** Data domain gains bus state, storage type (*Not:* data type), configuration, template, option, ledger, operation, ledger effect, snapshot of a ledger's state; Core's bus entry gains bus module; Config gains template file; Homonyms gain configuration, snapshot, template, option, effect.
What the design settles that the records left to it: the bus module's events kept 30 days on its old `streams` section; only the owning module calls the ledger's `apply`; the knowledge base's rollback during its move; `reviews` as a bare stream. Left to the operator, noted on issue 1966: a margin for the condition `full`, an event of its own for `drop` and `recreate`, and a correction of fact for ADR 0595 §4.
`go test ./...` passes at the root.
Reviewed by architectural domain, three rounds (each design ends with the record):
Reviewed-by: review-security-and-upgrade@shanks at 0cd0cfd (approved round 2)
Reviewed-by: review-seams-and-tools@shanks at 476557deeb4b0b62382d8c1bb9384ec22fa6051e
Reviewed-by: review-running-and-testing@shanks at 0cd0cfd (approved round 3)
Reviewed-by: review-health-and-events@shanks at 0cd0cfd (approved round 3)
The commits after 0cd0cfd add only the review record, read and approved by review-seams-and-tools at 3d4e361; its one suggested line is in 476557d.
Research 082 graduated into three accepted records; the bus module's design (25) and the manifest's (32) are the home of bus state for every module, and the knowledge base (55) becomes its first ledger.
Deliverynovox/hq@476557deeb4b — merged since 2026-11-03T10:21:11Z
Source — source.main moved to novox/hq@9a2d398070. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.
Transitions
2026-11-03 09:51 (new) → proposed (announced): novox/hq#506's head announced
2026-11-03 09:51 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 10: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-delivery:view -->
**Delivery** `novox/hq@476557deeb4b` — **merged** since 2026-11-03T10:21:11Z
**Source** — source.main moved to novox/hq@9a2d398070ed. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Transitions**
- 2026-11-03 09:51 (new) → proposed (announced): novox/hq#506's head announced
- 2026-11-03 09:51 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 10: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`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Research 082 graduated into ADR 0595 (a module asks the bus module for its kept data by a template, in
requires), ADR 0596 (events subscribed, data asked through tools; no module reads another's bus state) and ADR 0597 (the ledger; the knowledge base is its first), all accepted 2026-11-03. Issue 1966.One design per thing (playbook 02): the designs that already cover each area are amended, no new design is written.
mesh-broker's verbs, events, conditions and fill; the ledger andapplyin the tool runner; the calls package; the move and the build order; how each rule is checked.requires, one form, no readers; events subscribed, data asked through the owner's tools.names, no streamversions, no commit rule of its own; the move, the rollback and the tests follow.What the design settles that the records left to it: the bus module's events kept 30 days on its old
streamssection; only the owning module calls the ledger'sapply; the knowledge base's rollback during its move;reviewsas a bare stream. Left to the operator, noted on issue 1966: a margin for the conditionfull, an event of its own fordropandrecreate, and a correction of fact for ADR 0595 §4.go test ./...passes at the root.Reviewed by architectural domain, three rounds (each design ends with the record):
Reviewed-by: review-security-and-upgrade@shanks at
0cd0cfd(approved round 2)Reviewed-by: review-seams-and-tools@shanks at
476557deebReviewed-by: review-running-and-testing@shanks at
0cd0cfd(approved round 3)Reviewed-by: review-health-and-events@shanks at
0cd0cfd(approved round 3)The commits after
0cd0cfdadd only the review record, read and approved by review-seams-and-tools at 3d4e361; its one suggested line is in476557d.Delivery
novox/hq@476557deeb4b— merged since 2026-11-03T10:21:11ZSource — source.main moved to novox/hq@9a2d398070. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.