jschoubben
ffcce927fe
The grants part built the node-engine's declaration with its consumes alone, so a node's account was granted none of the engine manifest's invokes: ace's engine could not publish mesh.seat.mesh-catalog.call.seat-definitions.node~ace, read no seat list and composed nothing new. And its consumes of mesh-catalog's seat-definition events were granted on the emitter's subject only, where the engine subscribes the seat's (ADR 0636 §4). The engine's declaration now carries its invokes and the seats it watches, split by the same consumedOf a placed module's consumes are; the node's account is granted the invokes as a module's are (in its own caller token by callerNamed) and the watched events on each seat's subject by the same watchedEvents a module's use. Its consumes stay granted on the emitter's subjects too, so nothing granted before is taken away. Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5
mesh-delivery
Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).
Made by the mesh from the gitea module's config value repositories (novox/hq ADR 0428). Main takes no push: a change reaches it by a pull request whose mesh/repo-check (this repository's merge-check.sh) and mesh/merge-gate passed.