Seams review asks which processes of a module read each event, queue and state, and whether a shared reading place splits what each needs (A-397)

2026-11-14 18:05:23 +01:00
parent f67c788c82
commit a83f04be5c
2 changed files with 5 additions and 1 deletions
@@ -25,6 +25,7 @@ write.
 What you judge:

 - Seams: where each piece of state lives on the bus (key-value bucket, stream, object store) and which module owns it; which seat, verb or event joins two parts; any link that is not NATS-native (a poll, a timer, HTTP between modules, a shared file, state only in memory); whether a form the manifest lacks is named with its cost (a mesh-sdk change rebuilds every module).
+- Seams inside a module, at run time: for every event, queue and piece of state the subject adds or changes, which processes read it on each node (a module's program, its tool runner, any other process its manifest names, the same module on several nodes), and whether each gets every item it needs. A NATS durable consumer or a queue group hands each message to one reader only: two processes reading under one name split the messages silently, and the bus refuses nothing. A design line that names one reading place per module where more than one process reads is a **must**; only a work queue, where one reader per item is the point, is shared. (The operator, 2026-11-14: on ace the assigner's program and its tool runner read one durable consumer, and the runner took all 178 first registrations the program acts on; lead answer A-397.)
 - Tools: for every new piece of state a tool that reads it, and for every new behaviour a tool that steers it (do by hand, ask again, drop, repair, re-check), as the instruction tools-are-how-a-module-is-spoken-to says.

 Judge only whether the settled direction or design is complete and sound in your two architectural domains,
@@ -112,7 +112,10 @@ the four reviewer agents in `.claude/agents/` (`review-security-and-upgrade`, `r
  link that is not NATS-native. Each piece of state is kept in the bus storage form that fits it (a key-value
  bucket, a stream, an object store); a form the manifest lacks is added to mesh-sdk, and the review names that change
  and its cost (a mesh-sdk change rebuilds every module) to the operator, never folds it in silently (the
-  operator, 2026-11-02);
+  operator, 2026-11-02). Inside a module too: which of its processes (its program, its tool runner, another process
+  its manifest names) read each event, queue and piece of state at run time, and whether each gets every item it
+  needs: a durable consumer or a queue group hands each message to one reader only, so a reading place shared by two
+  processes splits the messages silently (the operator, 2026-11-14; lead answer A-397);
 - **running qualities**: build capacity, speed, storage growth, and what happens while a part, the bus or the
  control-node is down;
 - **health**: what each part's health check says, which conditions are raised and cleared, and whether any