novox/hq
8
0
Fork 0
Code Issues Pull Requests 2 Releases Wiki Activity

Say rollout, not walk (issue 646) #365

Merged
mesh-tools merged 2 commits from fix/646-rollout-not-walk into main 2026-10-15 17:59:22 +00:00
Conversation 2 Commits 2 Files Changed 82
+561 -561
mesh-tools commented 2026-10-15 17:58:08 +00:00
Member
Copy Link
Copy Source

Issue 646, part 1. The operator's word, 2026-10-15: "walk is a dirty word; we should never use walk."

  • The glossary entry walk becomes rollout (the controller's sending of one batch's builds across nodes, tier by tier; ADR 0236, ADR 0276), its Not: line strikes walk (hq); the homonym rows follow.
  • Running prose across hq: about 668 uses renamed (walk, walks, walked, walking) in 82 files; where the word meant something else it now says so (traversal, exercised, traversed, going through step by step).
  • Kept, about 44: code spans, identifiers (stalled walks, walkMoved, delivery-walks), controller output quoted, test and file names, link targets. Those name code that still says walk; renaming the controller's and mesh-delivery's output is part 2.
  • The catalogue's copy of the retired words holds only tools-scoped words, so it needs no change; hq's check against it passes.

Playbook 08. sh merge-check.sh passes. Reviewed independently before push: APPROVE at 437523554e (round 2); the head adds only a merge of main (playbooks 07 and 08).

Issue 646, part 1. The operator's word, 2026-10-15: "walk is a dirty word; we should never use walk." - The glossary entry **walk** becomes **rollout** (the controller's sending of one batch's builds across nodes, tier by tier; ADR 0236, ADR 0276), its *Not:* line strikes walk (hq); the homonym rows follow. - Running prose across hq: about 668 uses renamed (walk, walks, walked, walking) in 82 files; where the word meant something else it now says so (traversal, exercised, traversed, going through step by step). - Kept, about 44: code spans, identifiers (`stalled walks`, `walkMoved`, `delivery-walks`), controller output quoted, test and file names, link targets. Those name code that still says walk; renaming the controller's and mesh-delivery's output is part 2. - The catalogue's copy of the retired words holds only tools-scoped words, so it needs no change; hq's check against it passes. Playbook 08. `sh merge-check.sh` passes. Reviewed independently before push: APPROVE at 437523554efb0af27046fde19ee35fdac29f24ea (round 2); the head adds only a merge of main (playbooks 07 and 08).
mesh-tools added 2 commits 2026-10-15 17:58:08 +00:00
Say rollout, not walk, for the sending of a batch across nodes (issue 646) 437523554e
Merge remote-tracking branch 'origin/main' into fix/646-rollout-not-walk
mesh/merge-gate head 75ac87c72b6a merged into trunk 058d76ee8a4e — pass: the change touches no module of the mesh's graph
Details
mesh/repo-check head 75ac87c72b6a merged into trunk 058d76ee8a4e — pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details
75ac87c72b
mesh-tools commented 2026-10-15 17:58:11 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/hq@75ac87c72b6a — delivered since 2026-10-15T17:59:26Z

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

Transitions

  • 2026-10-15 17:58 (new) → proposed (announced): novox/hq#365's head announced
  • 2026-10-15 17:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-15 17:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-15 17:59 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-15 17:59 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@75ac87c72b6a` — **delivered** since 2026-10-15T17:59:26Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-15 17:58 (new) → proposed (announced): novox/hq#365's head announced - 2026-10-15 17:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-15 17:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-15 17:59 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-15 17:59 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-tools added the mesh/ready label 2026-10-15 17:58:30 +00:00
mesh-tools commented 2026-10-15 17:58:31 +00:00
Author
Member
Copy Link
Copy Source

ready at 75ac87c72b (the operator's word, 2026-10-15; independent review APPROVE at 4375235, the head adds only a merge of main).

ready at 75ac87c72b6a50e5142d0e110af6c6ac35334312 (the operator's word, 2026-10-15; independent review APPROVE at 4375235, the head adds only a merge of main).
mesh-tools merged commit 5ff97ec3aa into main 2026-10-15 17:59:22 +00:00
mesh-tools deleted branch fix/646-rollout-not-walk 2026-10-15 17:59:22 +00:00
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 mesh/ready
Milestone
No items
No Milestone
Assignees
Clear assignees
jschoubben mesh-tools miel.truyen
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#365