9 Commits

Include renames

Author	SHA1	Message	Date
jochen	9372e80cec	Serve a trusted holder from a runtime of its own account, refuse it in the machine's runtime, and say while an agent can become root where it runs (hq ADR 0259 §8)	2026-10-09 13:48:56 +02:00
jochen	c9be75b13e	Carry a channel's capabilities on its claim and tell the router every kind, so an answer is judged by the controller's record and not the channel's word	2026-10-09 13:48:56 +02:00
jochen	f5f315cc95	Grant a seat's traffic by caller and by kind, so an ask's asker and a channel's kind are facts the bus enforces (hq ADR 0259)	2026-10-09 13:48:56 +02:00
jochen	b74268fb08	Grant a bar one key of the state it shows, and per-machine state its own machine's key (hq ADR 0260) ... A derived read reached the whole bucket, and the power module could write every machine's draw. A read granted for a block now reaches that block's key alone, by the direct get of its subject and a consumer filtered to it, and state declared per-machine is written and read at the machine's own key only.	2026-10-08 15:51:20 +02:00
jochen	cfac579392	Module state is hq ADR 0201 after all: the derived-value record moved to 0202 on hq main	2026-10-04 11:02:42 +02:00
jochen	78915f9f7a	Module state is hq ADR 0202: 0201 landed first for a provider's derivations	2026-10-04 03:44:50 +02:00
jochen	aec55b7072	A module's state on the bus: buckets from the catalogue, grants, membership (novox/hq ADR 0201) ... A manifest names the state it keeps (state) and reads (reads); the controller asserts a key-value bucket per name on every raise, grants owners write and readers read (measured against a running server), issues each assignment its buckets in the membership, and reports buckets nothing declares without removing them.	2026-10-04 02:40:49 +02:00
jschoubben	24f024dd74	The proxy is told its routes and the mesh on the bus, and serves internal names to the mesh only ... The proxy answered every routed name to any request carrying it, so an internal-only route would have been public under its internal name. Each membership now carries what its module receives, from the same composition as its received file, and every machine's private-network address, the list the packet filter's "from the mesh" is. The proxy follows its membership, serves internal names only to those machines and itself, and keeps the file until the bus has spoken (novox/hq ADR 0167, issue 191).	2026-10-02 01:46:30 +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