novox/hq
7
0
Fork 0
Code Issues Pull Requests 3 Releases Wiki Activity

to-be 17: genesis assigns the builder before the package registry exists and hands it the forge it raised (issue 121, ADR 0336) #337

Merged
mesh-admin merged 1 commits from fix/121-genesis-package-registry into main 2026-10-13 03:37:19 +00:00
Conversation 1 Commits 1 Files Changed 1
+31 -1
mesh-admin commented 2026-10-13 00:56:40 +00:00
Contributor
Copy Link
Copy Source

To-be 17 (raising a mesh) cites ADR 0336 in decisions and describes it: the builder's package registry is an optional requirement that binds once the gitea module is assigned; the packages step seals the genesis document; a real binding wins and the build's log says which; a build needing the registry with neither fails before building, naming the machine; the genesis credential outliving the binding is issue 602. A row in the checks table names the tests, and says the live proof (a genesis bed passing steps 13 to 16) is not yet done.

Checked: records.py, index.py, cycle.py, words.py (with MESH_CATALOG_DIR) and merge-check.sh pass.

Code: mesh-catalog #263, plus the mesh-controller and mesh-host pull requests for issue 121.

To-be 17 (raising a mesh) cites ADR 0336 in `decisions` and describes it: the builder's package registry is an optional requirement that binds once the gitea module is assigned; the packages step seals the genesis document; a real binding wins and the build's log says which; a build needing the registry with neither fails before building, naming the machine; the genesis credential outliving the binding is issue 602. A row in the checks table names the tests, and says the live proof (a genesis bed passing steps 13 to 16) is not yet done. Checked: records.py, index.py, cycle.py, words.py (with MESH_CATALOG_DIR) and merge-check.sh pass. Code: mesh-catalog #263, plus the mesh-controller and mesh-host pull requests for issue 121.
mesh-admin added 1 commit 2026-10-13 00:56:40 +00:00
to-be 17: genesis assigns the builder before the package registry exists and hands it the forge it raised (issue 121, ADR 0336)
mesh/merge-gate head 39830983ccf1 merged into trunk 5a6200ec866c — pass: the change touches no module of the mesh's graph
Details
mesh/repo-check head 39830983ccf1 merged into trunk 5a6200ec866c — pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details
mesh/delivery-group group fix/121-genesis-package-registry delivered: every member is delivered
Details
39830983cc
mesh-admin commented 2026-10-13 00:56:58 +00:00
Author
Contributor
Copy Link
Copy Source

Delivery novox/hq@39830983ccf1 — delivered since 2026-10-13T03:37:33Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Group fix/121-genesis-package-registry, in order: novox/hq@39830983cc → novox/mesh-host@5f147fe6b9

Transitions

  • 2026-10-13 00:56 (new) → proposed (announced): novox/hq#337's head announced
  • 2026-10-13 00:58 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-13 00:58 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-13 03:37 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-13 03:37 published → delivered (done): nothing for a walk to move

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

<!-- mesh-delivery:view --> **Delivery** `novox/hq@39830983ccf1` — **delivered** since 2026-10-13T03:37:33Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Group** `fix/121-genesis-package-registry`, in order: novox/hq@39830983ccf1 → novox/mesh-host@5f147fe6b9c7 - novox/mesh-catalog@e0bc919d4945 before novox/mesh-controller@a641ed7d15c7: built by - novox/mesh-controller@a641ed7d15c7 before novox/mesh-catalog@e0bc919d4945: built by - **refused**: novox/mesh-catalog@e0bc919d4945 and novox/mesh-controller@a641ed7d15c7: built by puts novox/mesh-catalog@e0bc919d4945 first, built by puts novox/mesh-controller@a641ed7d15c7 first, version skew puts novox/mesh-controller@a641ed7d15c7 first; neither outranks the other: declare the order with a line `after: novox/mesh-catalog` in novox/mesh-controller#289's description, or `after: novox/mesh-controller` in novox/mesh-catalog#263's **Transitions** - 2026-10-13 00:56 (new) → proposed (announced): novox/hq#337's head announced - 2026-10-13 00:58 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-13 00:58 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-13 03:37 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-13 03:37 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-admin left a comment
Author
Contributor
Copy Link
Copy Source

Verdict: approve at 39830983cc

Independent review against ADR 0336 and ADR 0330.

No blocking finding. Merge it in the group fix/121-genesis-package-registry once mesh/delivery-group reads green.

What I checked:

  1. hq's four checks pass at the head: records.py ("all checks passed"), index.py, cycle.py ("436 documents checked, the chain holds") and words.py ("28 retired words and 2 identifiers, none in running prose"). sh merge-check.sh also passes.
  2. The public-repository rule holds. The added lines name no node, host, domain, address, absolute path or username. They name role-free things only: the account mesh-builder, the own-secret genesis-package-registry, the requirement npm-package-registry, and the @novox/ package scope, which to-be 20 already names.
  3. The text agrees with the ADR. To-be 17 cites ADR 0336 in its frontmatter, updated is moved to 2026-10-13, and the new section states §1 to §7: the requirement is optional, genesis is not reordered, the genesis document is issued outside the mesh, the binding wins, what needs the registry, the loud refusal, and the sdk and base steps. It names issue 602 for §8 rather than deciding it, and the rules table says honestly that the genesis bed from bare is not yet proved. "builder" is the glossary's word for the build seat's holder, so its use beside build-agent is correct.

Non-blocking:

  • The design does not mention the builder's choice (a) above: binds and secrets are not marked only-when-bound, because no such form exists, and are left out by ADR 0330 §6. ADR 0336 §1 itself still says they are marked. The record needs a progressive insight through knowledge-base.propose; the design needs no change.
  • The section's lead says the builder "is handed the forge genesis raised" and the same paragraph explains the document. Calling it the genesis document from the first sentence would match the glossary-style "one name per thing" better, but the term is defined in bold where it first matters.

Statuses at this head:

  • mesh/merge-gate: success, "head 39830983cc merged into trunk 5a6200ec86 — pass: the change touches no module of the mesh's graph"
  • mesh/repo-check: success, "head 39830983cc merged into trunk 5a6200ec86 — pass: its merge-check.sh passed"
  • mesh/delivery: success, "ready: it delivers once merged"
  • mesh/delivery-group: failure, "group fix/121-genesis-package-registry rejected: its order contradicts itself: novox/mesh-catalog@e0bc919d49 and novox/mesh-controller@a6…"
Verdict: approve at 39830983ccf186229d42dc87879faf17afbfe206 Independent review against ADR 0336 and ADR 0330. No blocking finding. Merge it in the group fix/121-genesis-package-registry once mesh/delivery-group reads green. What I checked: 1. hq's four checks pass at the head: records.py ("all checks passed"), index.py, cycle.py ("436 documents checked, the chain holds") and words.py ("28 retired words and 2 identifiers, none in running prose"). `sh merge-check.sh` also passes. 2. The public-repository rule holds. The added lines name no node, host, domain, address, absolute path or username. They name role-free things only: the account `mesh-builder`, the own-secret `genesis-package-registry`, the requirement `npm-package-registry`, and the `@novox/` package scope, which to-be 20 already names. 3. The text agrees with the ADR. To-be 17 cites ADR 0336 in its frontmatter, `updated` is moved to 2026-10-13, and the new section states §1 to §7: the requirement is optional, genesis is not reordered, the genesis document is issued outside the mesh, the binding wins, what needs the registry, the loud refusal, and the sdk and base steps. It names issue 602 for §8 rather than deciding it, and the rules table says honestly that the genesis bed from bare is not yet proved. "builder" is the glossary's word for the build seat's holder, so its use beside `build-agent` is correct. Non-blocking: - The design does not mention the builder's choice (a) above: binds and secrets are not marked only-when-bound, because no such form exists, and are left out by ADR 0330 §6. ADR 0336 §1 itself still says they are marked. The record needs a progressive insight through knowledge-base.propose; the design needs no change. - The section's lead says the builder "is handed the forge genesis raised" and the same paragraph explains the document. Calling it the genesis document from the first sentence would match the glossary-style "one name per thing" better, but the term is defined in bold where it first matters. Statuses at this head: - mesh/merge-gate: success, "head 39830983ccf1 merged into trunk 5a6200ec866c — pass: the change touches no module of the mesh's graph" - mesh/repo-check: success, "head 39830983ccf1 merged into trunk 5a6200ec866c — pass: its merge-check.sh passed" - mesh/delivery: success, "ready: it delivers once merged" - mesh/delivery-group: failure, "group fix/121-genesis-package-registry rejected: its order contradicts itself: novox/mesh-catalog@e0bc919d4945 and novox/mesh-controller@a6…"
mesh-admin merged commit 963f0d0ecd into main 2026-10-13 03:37:19 +00:00
mesh-admin deleted branch fix/121-genesis-package-registry 2026-10-13 03:37:20 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
mesh-admin
Labels
No items
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
jschoubben miel.truyen
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#337