jschoubben
dead64ee6e
Issue 1966: the list sealed 2026-11-07 23:09, composed while the seat list was unread (only the bootstrapped seats compose), took the node seats from the tool runners, the vault's reads from the node-engines and the seat queues from the build modules, and left out ledger.novox.mesh-knowledge. - While the seat list is unread (the gate's MayAct with no seat) or a pass is placed by the haves, each user of the loaded list and of the list in force is sealed with the union of what the pass composes and what those lists give it (publish, subscribe, responses; a deny only where every list saying one denies it), kept the way a refused principal is; the users so kept are the pass's kept_loaded. - In such a pass a list that still takes a permission from, or leaves out, a loaded user is held (user-list-held), naming each user and how many permissions it loses. - A held module keeps its ledger account, ledger.<node>.<module>, with its other users: heldModuleUsers matched <node>.<module>[.<process>] only, which dropped the ledger user. 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.