Design 47 H: H-A-127, nats_consumer_remove refuses by durable name; why is the warrant

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
2026-11-20 06:15:13 +01:00
parent f1164f49ff
commit f3d57662c6
@@ -557,3 +557,9 @@ Where two preparers disagreed, the chosen one is named.
kept-data stream: one no manifest names is an orphan on that stream, removed by warrant (`why` required) and
written in the hand-act log as the keeper's requests are. The clean state's step 5.8 names these three. P4, P7 (no
second tool for one act).
- **H-A-127 (`nats_consumer_remove`: what it refuses and what warrants it, 06:16)** (1) No manifest field names a
durable; the mesh names a module's durable `<node>_<module>`. The tool refuses a durable whose name is that form for
a module of an accepted manifest on that node (the keeper's accepted set), on any stream; every other durable is an
orphan and goes. The judgement is by name, not by stream (H-A-126). (2) `why` is the warrant: the tool acts at once
and writes the hand act through mesh-hand-acts as `nats_bucket_expiry` does. The clean state runs at the operator's
terminal, so an ask of the operator would answer the operator's own call (P7). P4, P7.