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)
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user