Answer the what-if as data, let the build seat read the gate's pull keys, and prove the parts' and the gate's grants (design 47 R3d, ADR 0450) #401

Merged

mesh-tools merged 4 commits from feat/r3d-sdk-and-controller into main 2026-10-19 22:33:11 +00:00

Conversation 1 Commits 4 Files Changed 11

+993 -48

4 Commits

Author	SHA1	Message	Date
mesh-tools	0aac89f4e2	Test that the gate's buckets are writable by its machine's tool runner account only (issue 1326) ... ADR 0437 §3's check: the gate, written in the test as the clause declares it, is composed with the parts and the view through Users; its seven buckets are writable by its machine's tool runner and by no other account, and each part reads only the gate buckets its manifest declares.	2026-10-19 21:48:07 +00:00
mesh-tools	d8c13d97ca	Test that the forge bridge's, indexer's and teller's credentials grant exactly their manifests (issue 1243) ... ADR 0437 §4's check: the three manifests, copied from mesh-delivery's main, are composed through Users and PermissionsFor; each may do what it declares and is refused another module's bucket, another module's name and a seat's verb subject.	2026-10-19 21:47:47 +00:00
mesh-tools	4083755ca1	Let the build agent read the gate's pull keys and watch both buckets (issue 1325) ... From R3e the gate writes mesh-delivery-gate_pulls and today's bucket stops (ADR 0450 §1). The build agent's manifest reads both, and a running check's watch listens in every bucket that exists, so a move is heard whichever holds the key.	2026-10-19 21:42:37 +00:00
mesh-tools	23a209f3d0	Answer plans what-if as data, the document delivery-plan answers (issue 1324) ... The gate reads a delivery's plan as data once delivery-plan goes (ADR 0450 §2). The data form is an explicit switch, `data: true`, as plans wait asks for its data: a person still gets the text. Both verbs build their document from one function, deliveryPlanDocument, so they cannot differ; delivery-plan is unchanged (ADR 0450 §8).	2026-10-19 21:40:26 +00:00