Answer A-43: plain views families are followed, the runner's writer uses its JetStream
mesh/check checking d9a0e19b204e on e1819e0a0d08
mesh/delivery merged: source.main moved to novox/hq@e1819e0a0d08

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
This commit is contained in:
2026-11-11 22:25:39 +01:00
parent 2d5f6ac949
commit d9a0e19b20
@@ -161,3 +161,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
has it, and the lead notes it for the next milestone; no new verb is added in G for it.
- **A-42** (§592; principle 8) The gate's `approval-carried-open` has scope `delivery`, a scope the mesh already uses
for the delivery's findings, and id `<repository>.<pull>`.
- **A-43** (A-26, A-28, A-16; principle 7) As built in mesh-catalog d03ffa80 and mesh-tools 4bfae38a: an owner's plain
`<owner>.views.<state>` family is followed by `Reader.Follow`, the follower's `Ask` set after (`Adopt` is for a seat's
events); and the tool runner's held writer is given its JetStream, the writer's own defaults publishing and
listening, so `bus.Conn` gains no publish method.