4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	d01839c29c	Grant the grants part reading every membership; seal the seeded account in the addresses test (ADR 0547 §5, review; issue 1945) ... The grants part reads each module's last membership before it publishes, so it is granted the direct get on every membership subject beside the publish (review of mesh-grants, B1). The test TestTheControlPlaneIsToldWhereTheNodePutTheStoreAndTheBroker failed on main since PR #467: it seeds anchor.mesh-controller with no seal, and an account counts as issued only once sealed (ADR 0543 §2). The rule is right; the fixture is fixed, sealing the seeded credential the controller already uses. Test only.	2026-10-25 22:51:25 +01:00
jschoubben	f67d15536b	Grant the grants part publishing the modules' memberships, and nothing more (ADR 0547 §5, issue 1945) ... No membership is published since release 6 (issue 1945 notes 42, 47), so a seat-holding module placed now cannot serve its seat or pull asks (mesh-build-go on ace, 2026-10-25). The operator decided at 22:31 that the grants part publishes them from the first milestone: its principal, module mesh-grants, may publish mesh.assignment.*.* and no stream definition. The SDK's copy of this composer gets the same line, so the two stay byte-equal. Research 072 (the controller, NATS-native): this moves the memberships of its Bus row to the grants part.	2026-10-25 22:32:35 +01:00
jochen	9d4d847dc4	The machine runs one tool runtime, loading every delivered bundle (hq ADR 0175, to-be 38 WP2.3) ... Where node-tools is in a node's set, the declaration ends with one process: the runtime module's own bundle, run from its one entrypoint by its language's interpreter, told in MESH_TOOL_MODULES every <module>=<file> the machine's bundles load, where its credential is (the module's own broker secret as this node places it), and — on a machine with an operator account — who the operator is, running as that account so a tool that needs root can escalate as the operator would. Restarted when any bundle it loads or the credential changes. A machine with no account runs it as root without the two operator words; a machine without the runtime is sent nothing new. A bundle says which of its entrypoints the runtime LOADS (`loads`), because one bundle may carry a daemon beside its tools and importing the daemon into the runtime would start it there; absent, a module declaring tools has every entrypoint loaded. And the TypeScript toolchain is rooted at the module, so an entrypoint lands at the path it is named by — the runtime loading bundles by their declared paths is what made the compiler's common-directory default visible.	2026-10-02 18:26:54 +02:00
jschoubben	603ad61142	The mesh issues an assignment's subjects: a membership per module on a machine (hq ADR 0160) ... For every module on every machine the controller composes what that instance serves — its machine's address always, the module's plain address in a queue when it is alone or its definition says its instances are interchangeable — the verbs of the seats it holds at the seats' subjects, where its events land, and what it may reach, resolved the same way for the modules it invokes. Published beside the node's declaration on `mesh.assignment.<node>.<module>`, last per subject in a stream that allows direct reads, and the account may read exactly its own. Composed from the same records the bus's accounts are, so what a runtime serves and what its account may are one composition. `instances: interchangeable` is the one fact a definition states for it. The shape issued is the shape the mesh already had, so nothing moves when the membership arrives; the runtime that reads it instead of deriving it is the next piece.	2026-10-01 14:43:26 +02:00