8 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	3b49d7044f	A state entry may say key-ttl and its bucket allows a time to live per key (issue 1154)	2026-10-18 20:53:42 +02:00
jschoubben	661e8eff2f	The broker asserts the have bucket and grants each node its own keys of it, the controller none (issue 1136)	2026-10-18 19:04:55 +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	e74c32ed50	Keep calls and hand acts on the bus, answer status at once, record durations (hq to-be 45 Phase 0) ... A controller restart lost every call's outcome, `status` composed the mesh while its caller waited (18.6s live on 2026-10-06, past the 10s window), a repair by hand left no trace, and the core's bounds had nothing measured to be set from. - calls: kept in the controller's bucket mesh-controller_calls (last 1000 or 14 days, answers bounded to 64 KiB), read by id across a restart; a controller starting marks a stopped one's running calls abandoned; each call names its caller from the inbox its answer goes to. - status: the serving controller composes it at start, after news from a machine, a build or an acting verb, and every minute; the verb answers the last composition at once with when and how long it took. Composing resolves each machine once instead of twice. - hand-act log in mesh-controller_hand-acts: push (required through the seat), plans stop/close, broker consumer-reset and the new hand-act record take --why/--cause/--condition; `hand-acts` lists them and repeated causes; status counts the week's. - durations (migration 0066): apply (send to first report), heartbeat gap, plan tier and build, recorded as heard; `durations` summarises them. - the controller's seat row takes this binary's definition of its own verbs, so the console no longer judges calls against an older build's schema. - the controller is granted its two buckets' subjects.	2026-10-06 02:59:36 +02:00
jochen	e610f2d92c	Let a build agent be paused, have a build killed, and end an ask cancelled as it took it (hq ADR 0219) ... A queued ask could only be waited out and a running build only ended by stopping the machine, which redelivered it elsewhere. The holder now serves current, kill, pause and resume on its own machine's subjects; a kill ends the build's process group and labelled containers and settles the ask as failed, killed by hand; pause is kept in the workspace across a restart and said on the bus. The controller writes cancelled ids to a cancelled set the holder reads on taking an ask, closing the race a delete alone leaves.	2026-10-05 19:17:42 +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