Feature 57 (config and provisioning): release mesh-host #115

Closed

mesh-tools wants to merge 15 commits from feat/57-config-and-provisioning into main

pull from: feat/57-config-and-provisioning

merge into: :main

:main

:replay/r92-before

:fix/567-an-access-is-judged-by-who-writes-it

:fix/inspect-by-kind-not-the-ambiguous-bare-form

Conversation 3 Commits 15 Files Changed 43

+4112 -77

mesh-tools commented 2026-10-16 08:16:57 +00:00

Member

Copy Link

Copy Source

Feature 57's release of mesh-host (the node-engine): the release branch feat/57-config-and-provisioning (reviewed and merged there: #114) into main. Delivery group 57 bundle A with mesh-sdk, mesh-controller and hq.

Feature 57's release of mesh-host (the node-engine): the release branch feat/57-config-and-provisioning (reviewed and merged there: #114) into main. Delivery group 57 bundle A with mesh-sdk, mesh-controller and hq.

mesh-tools added 15 commits 2026-10-16 08:16:57 +00:00

Open the integration branch of release 57 (config and provisioning) ... 1203f96a24

So the packages of hq design 57 meet here, reviewed one by one, and reach main as one delivery group.

Say who owns a placed file at runtime, and which files the provisioner fills ... 1cc588ebc0

The provisioner (ADR 0349 §5) needs each file it places to say whether it is
owned, a seed or managed, and the node-engine needs to know which paths it
fills. The words map onto today's forms (drift written back, create-once,
into), so no write changes; the reader accepts the fields and states
OwnershipContract before any controller sends them. Issue 667.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Merge pull request '57/P1: The node-engine knows who owns a placed file at runtime (issue 667)' (#109) from pkg/57-p1-ownership into feat/57-config-and-provisioning 6b54fed706

Let genesis's controller write its record mirrors ... c892062251

The controller now keeps the assignments and each registered module's declared
config on the bus (hq issue 652, design 57 F3), so its composed grant gains the
two buckets and their two events. The installer's first user list must equal
that composition, or the controller is refused at genesis; mesh-controller's
genesis template test holds the two to each other.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Name the provisioner client's account in the declaration, and share the apply's record ... fddcddfaf7

The local write of a filled file (ADR 0349 §4) accepts only the provisioner client's account, which the declaration names; the reader takes provisioner_account before any controller sends it (contract 10). The apply's record and its rule for what moved become helpers the write uses too. Issue 668.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Write a filled file on the provisioner client's request, and nothing else ... eb2ec23679

The provisioner's client (ADR 0349 §4) fills a module's templates and needs the node-engine to write them: it must not hold the right to write the machine's files itself. A second local socket accepts a write only from the account the declaration names as the provisioner client's (SO_PEERCRED, same namespaces), only for a clean path the declaration names as filled, under the apply's own locks, and writes it through the apply as the declared file would be, firing restart-on, reload-on and container reads. Issue 668.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Write a filled file through the apply, and move what reads it ... 1d57bcd6f9

A filled file is the declared file with the client's content: applied through applyFile, applyInto or applyBlock by who owns it at runtime, with the apply's guards, Keep and record, then restart-on, reload-on and container reads applied as an apply does. Issue 668.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Serve the local write of a filled file on its own socket ... 499a687149

A second unix socket beside mesh-cli's: the kernel's word on the asking account (SO_PEERCRED, same namespaces), that account judged against the declaration before its request is read, the path judged clean, absolute and filled, and the write done under the apply's lock. The journal has the path and digest, never the content. Issue 668.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Hold a library's containers through the write verb, as a full apply does ... 76dc93c421

Review 11959 of mesh-host#111: a write through the verb recreated a container that reads the filled file over a library whose disk was missing (ADR 0328 §9). Also refuses a filled path two resources declare, with a test. Issue 668.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Judge a caller before it holds the socket, and keep accepting after a failed accept ... 0c17c76493

Review 11959 of mesh-host#111: any account could hold the four slots for a second each and starve the provisioner's client, and one failed accept ended the socket until the engine restarted. A caller is judged from the kernel's word before it holds a slot and, refused, is answered and closed at once; busy refusals that wait are bounded as mesh-cli's are; a failed accept is said, backed off and retried. The request refuses unknown fields, and the socket's directory is given its mode. Issue 668.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Merge pull request '57/F3: Let genesis's controller write its record mirrors (issue 652)' (#110) from pkg/57-f3-controller-mirror-grants into feat/57-config-and-provisioning c18d5a8ff3

Say every refusal kind at once and never lose a count; bound the waiting and the busy per socket ... 2767278228

Review 12004 of mesh-host#111: refusals counted after a said one reached the journal only if the same account was refused again a minute later, and a refusal of another kind hid behind it. The first of each (account, kind) is said at once, and what is counted is said on a timer and when the socket stops. Connections waiting to be judged are bounded below the open-file limit, the busy refusals belong to one Serve, and the tests' ask has a deadline. Issue 668.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Merge pull request '57/P2: The node-engine writes a filled file on the provisioner client's request, and nothing else (issue 668)' (#111) from pkg/57-p2-local-write-verb into feat/57-config-and-provisioning 53fd326189

Land feature 57's node-engine work on its release branch ... 5a7ec3775b

The node-engine renders the feature's templates, collections and moved
providers' files, on the SDK the feature's modules build on (feature 57,
config and provisioning).

Merge pull request 'Feature 57 (config and provisioning): the node-engine's part, into its release branch' (#114) from 57-config-and-provisioning into feat/57-config-and-provisioning b546d4316c

mesh-tools commented 2026-10-16 08:17:04 +00:00

Author

Member

Copy Link

Copy Source

Merge check at b546d431
Judged: head b546d4316c3b merged into trunk 49c9002c04d3

• mesh/merge-gate: FAIL — head b546d4316c does not merge cleanly into trunk 49c9002c04: in conflict examples/foundation-first-node.lock (modules: mesh-host)
• mesh/repo-check: FAIL — head b546d4316c does not merge cleanly into trunk 49c9002c04: in conflict examples/foundation-first-node.lock

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

• tier 0: mesh-host
• ace: receives mesh-host
• g14: receives mesh-host
• novox: receives mesh-host
• shanks: receives mesh-host
• grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-host is judged on its first machine
• read by no module's build: RELEASE-57.md, cmd/mesh-host/filling_test.go, cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_library_test.go, internal/apply/filled_test.go, internal/apply/ownership_test.go, internal/apply/vault_sealed_test.go, internal/declaration/ownership_test.go, internal/declaration/provisioner_test.go, internal/filling/filling.go, internal/filling/filling_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go, internal/units/units_test.go, validate/validate_test.go

Run by the build seat on novox as build-1792138621792444111 (builds --log build-1792138621792444111).

head b546d4316c3b does not merge cleanly into trunk 49c9002c04d3: in conflict examples/foundation-first-node.lock

**Merge check** at `b546d431` Judged: head `b546d4316c3b` merged into trunk `49c9002c04d3` - `mesh/merge-gate`: **FAIL** — head b546d4316c3b does not merge cleanly into trunk 49c9002c04d3: in conflict examples/foundation-first-node.lock (modules: mesh-host) - `mesh/repo-check`: **FAIL** — head b546d4316c3b does not merge cleanly into trunk 49c9002c04d3: in conflict examples/foundation-first-node.lock **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-host is judged on its first machine - read by no module's build: RELEASE-57.md, cmd/mesh-host/filling_test.go, cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_library_test.go, internal/apply/filled_test.go, internal/apply/ownership_test.go, internal/apply/vault_sealed_test.go, internal/declaration/ownership_test.go, internal/declaration/provisioner_test.go, internal/filling/filling.go, internal/filling/filling_test.go, internal/link/movesecret_test.go, internal/liveness/liveness_test.go, internal/units/units_test.go, validate/validate_test.go Run by the build seat on novox as `build-1792138621792444111` (`builds --log build-1792138621792444111`). ``` head b546d4316c3b does not merge cleanly into trunk 49c9002c04d3: in conflict examples/foundation-first-node.lock ```

mesh-tools commented 2026-10-16 08:17:06 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-host@b546d4316c3b — stopped since 2026-10-16T08:27:26Z

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

• tier 0: mesh-host
• ace: receives mesh-host
• g14: receives mesh-host
• novox: receives mesh-host
• shanks: receives mesh-host
• grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-host is judged on its first machine

Group feat/57-config-and-provisioning, in order: novox/hq@110bb7d1d7 → novox/mesh-controller@6a6628a769 → novox/mesh-host@b546d4316c → novox/mesh-sdk@67ee945af5

• novox/mesh-controller@6a6628a769 before novox/mesh-host@b546d4316c: built by, over engine before controller
• novox/mesh-controller@6a6628a769 before novox/mesh-sdk@67ee945af5: built by

Transitions

• 2026-10-16 08:17 (new) → proposed (announced): novox/mesh-host#115's head announced
• 2026-10-16 08:17 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-16 08:17 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
• 2026-10-16 08:27 rejected → stopped (closed): the pull request closed unmerged

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-host@b546d4316c3b` — **stopped** since 2026-10-16T08:27:26Z **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-host is judged on its first machine **Group** `feat/57-config-and-provisioning`, in order: novox/hq@110bb7d1d7e1 → novox/mesh-controller@6a6628a76961 → novox/mesh-host@b546d4316c3b → novox/mesh-sdk@67ee945af5d1 - novox/mesh-controller@6a6628a76961 before novox/mesh-host@b546d4316c3b: built by, over engine before controller - novox/mesh-controller@6a6628a76961 before novox/mesh-sdk@67ee945af5d1: built by **Transitions** - 2026-10-16 08:17 (new) → proposed (announced): novox/mesh-host#115's head announced - 2026-10-16 08:17 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 08:17 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-16 08:27 rejected → stopped (closed): the pull request closed unmerged The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools referenced this pull request from novox/mesh-sdk 2026-10-16 08:17:16 +00:00

Feature 57 (config and provisioning): release mesh-sdk #29

mesh-tools commented 2026-10-16 08:24:53 +00:00

Author

Member

Copy Link

Copy Source

Closed: it did not merge cleanly into main (examples/foundation-first-node.lock). Feature 57's release goes from branch release/57-config-and-provisioning: the release branch merged with main (tree db310999, the same as the release branch's, whose lock line already held main's one addition), as one commit on top of main.

Closed: it did not merge cleanly into main (examples/foundation-first-node.lock). Feature 57's release goes from branch release/57-config-and-provisioning: the release branch merged with main (tree db310999, the same as the release branch's, whose lock line already held main's one addition), as one commit on top of main.

mesh-tools closed this pull request 2026-10-16 08:24:53 +00:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-host#115