Answer A-19: HearSeatEvents' read at the start

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
2026-11-11 21:54:44 +01:00
parent c58a00b3a7
commit 99d9721ff3
1 changed files with 5 additions and 0 deletions
@@ -71,3 +71,8 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-18** (§587, §305; principle 7) What G retires leaves no trace: the gate's record type drops the `remove` operation
  and `OpRemove` (§587: a removal is no operation), and its `table`, `recheck` and `close` go with their handlers and
  tools (§305). `checks`, which no line retires, stays.
+- **A-19** (§641, §556; principles 1, 7 and 2) `HearSeatEvents` learns that a stream is kept last per subject from the
+  stream's own info on the bus, with no new parameter; its ordered read at the start filters on the same subjects as its
+  durable; the read's messages go to the same handler as the durable's, so one path handles both; it names the read
+  `waiting` and then `read` through one callback option it calls, which the module wires to its first views, so
+  `process` imports nothing of `views`.