4 Commits

Include renames

Author	SHA1	Message	Date
jochen	1af6efb356	Name the one genesis bundle in every bed and the README (hq issue 146, ADR 0331) ... mesh-host now carries one genesis bundle, foundation-first-node.lock, on the bus the mesh runs on; the NATS one it replaces is deleted. Beds that still named it would point at a file that is gone, and the harness's rewrite for the previous broker's image rewrote nothing.	2026-10-12 22:50:50 +02:00
jschoubben	a734d427c0	A bed says what it actually needs to be pointed at ... The instructions in every bed named the bundle that raises the predecessor's broker, so a first attempt ends in a control plane crash-looping on a missing MESH_BUS_NATS — which reads like a broken lab. They name the bundle that works now, and the README says the host binary needs SYSTEM=arch, because one built without it refuses everything with an empty system name. And the three habits that each cost a run before they were adopted: MESH_LAB_KEEP to leave the machine standing, MESH_LAB_WARM while iterating, and rebuilding all three repositories the bed places rather than the one that changed.	2026-09-29 17:45:09 +02:00
jschoubben	514f7a46cd	The store-window bed holds a report through the gap, asserts the enrolment is answered meanwhile, and compares the keys the mesh recorded with the ones the machine generated	2026-09-22 14:24:01 +02:00
jschoubben	c9fd6d7887	A bed that takes the store away while a machine enrols, and holds the enrolment to completing on its own (novox/hq issue 083)	2026-09-22 14:08:45 +02:00