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	f2d6ab3bf9	The trust bed raises a mesh, and places the bus's users as genesis must ... novox/hq 04-ISSUES/146. The bed now does what raising a first node actually takes: the private network so the authority can certify the address it holds, and the composed user list placed beside the bus at the two moments an account comes into existence — when the token is issued, and when the machine enrols. Neither can arrive in a declaration, because a machine that has not enrolled gets none. MESH_LAB_KEEP leaves the machine standing, which is where every answer in this sequence came from. No 'module issue' for the authority: that delivers a bus account and it declares none. The bed still fails, at the machine being enrolled twice from one attempt.	2026-09-29 17:37:08 +02:00
jschoubben	62a02d7e94	A bed for the trust anchor, and the bundle rewrite its foundation needs ... novox/hq ADR 0147. The bed dials the authority itself — step-ca serves its own API with a leaf it issued — so a plain client verifying that handshake is verifying one thing: the mesh's root is in this machine's trust store. The negative half runs twice, before the module is assigned and after it is unassigned; an anchor bed that only checks the success would pass on a machine that trusted everything. foundationBundle learns the new bundle's bus reference, the way it already knows the store's and the previous broker's. The bed does not run yet: raising a foundation fails before any module is reached (novox/hq issue 146).	2026-09-29 15:26:05 +02:00