Seams review asks which processes of a module read each event, queue and state #610

Open
mesh-tools wants to merge 1 commits from agents/seams-reads-per-process into main
Member

The seams reviewer (hq .claude/agents/review-seams-and-tools.md) and playbook 01's seams domain gain one question: for every event, queue and piece of state a subject adds or changes, which processes of which modules read it at run time (program, tool runner, other process, same module on several nodes), and whether each gets every item it needs. A durable consumer or a queue group hands each message to one reader only, so two processes reading under one name split the messages silently.

Why: 2026-11-14 on ace the assigner's program and its tool runner read one durable consumer; the runner took all 178 first registrations the program acts on, silently (lead answer A-397, design/47-G-lead-answers-31). Design 19 says one durable consumer per module, written when a module was one process; neither the design review nor the code review asked about processes inside a module. The operator, 2026-11-14: "go ahead, change the seams reviewer now".

Checks: go test ./... at the root passes (words, records, index, cycle). playbooks.html does not repeat the seams wording, so it is unchanged.

Review: pushed before an independent review, on the operator's word to change it now; a two-file wording change. Rule bent: how-work-is-done's push after the review approves; covered by the pull request's check and the operator's read.

Pushed-by: lead-47@shanks at a83f04be

The seams reviewer (hq `.claude/agents/review-seams-and-tools.md`) and playbook 01's *seams* domain gain one question: for every event, queue and piece of state a subject adds or changes, which processes of which modules read it at run time (program, tool runner, other process, same module on several nodes), and whether each gets every item it needs. A durable consumer or a queue group hands each message to one reader only, so two processes reading under one name split the messages silently. Why: 2026-11-14 on ace the assigner's program and its tool runner read one durable consumer; the runner took all 178 first registrations the program acts on, silently (lead answer A-397, design/47-G-lead-answers-31). Design 19 says one durable consumer per module, written when a module was one process; neither the design review nor the code review asked about processes inside a module. The operator, 2026-11-14: "go ahead, change the seams reviewer now". Checks: `go test ./...` at the root passes (words, records, index, cycle). playbooks.html does not repeat the seams wording, so it is unchanged. Review: pushed before an independent review, on the operator's word to change it now; a two-file wording change. Rule bent: how-work-is-done's push after the review approves; covered by the pull request's check and the operator's read. Pushed-by: lead-47@shanks at a83f04be
mesh-tools added 1 commit 2026-11-14 17:05:40 +00:00
This pull request has changes conflicting with the target branch.
  • .claude/agents/review-seams-and-tools.md
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin agents/seams-reads-per-process:agents/seams-reads-per-process
git checkout agents/seams-reads-per-process
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#610