Design 47: the gate reads mesh/check, the forge requires no status (ADR 0534 §1 changes ADR 0447 §5)

2026-10-23 16:31:15 +02:00
parent 8f7c23da7d
commit e8bd9171cd
1 changed files with 2 additions and 2 deletions
@@ -382,8 +382,8 @@ From its delivery, a check is this:
  on its head; it passes only when the head merged onto its trunk's head passed its tests and the composition
  check. For a member of a delivery group it is the group's one verdict, the same on every member's head: every
  member's tests, read beside the others' heads, and one composition of all members' changes. It replaces
-  `mesh/merge-gate` and `mesh/repo-check`; the forge requires it and the gate reads it from R4f, the delivery in which
-  the checker's line is the only one (ADR 0447 §5); the checker writes it unrequired from R4c (ADR 0453 clause 4). ADR 0484 builds the dark half, the verdict, its line and its status, in R4c-5, as one delivery group of four repositories with the shared library a member, one composed check, one Approve and one delivery plan; for this milestone only, before R4e, a group may hold a mesh-sdk member (ADR 0494 §1, §2, which replace ADR 0484 §1 and change ADR 0482 §7): the checker records the status as an act it owes in its own bucket and the forge bridge, the only part that calls the forge, performs it; the checker judges the head merged onto the trunk, for pull requests into the trunk named main only and for hq none, and until the isolated run step exists (issue 1309) it runs a change's code without the sandbox, as today's checks do (ADR 0484 §2, §3, §5, §8, §11). `mesh/delivery-group` stays the delivery's view, not a required check. Wherever
+  `mesh/merge-gate` and `mesh/repo-check`; the gate and the merge tool read it from R4f, the delivery in which
+  the checker's line is the only one, and the forge requires no status on any repository (ADR 0447 §5 as ADR 0534 §1 changes it); the checker writes it from R4c (ADR 0453 clause 4). ADR 0484 builds the dark half, the verdict, its line and its status, in R4c-5, as one delivery group of four repositories with the shared library a member, one composed check, one Approve and one delivery plan; for this milestone only, before R4e, a group may hold a mesh-sdk member (ADR 0494 §1, §2, which replace ADR 0484 §1 and change ADR 0482 §7): the checker records the status as an act it owes in its own bucket and the forge bridge, the only part that calls the forge, performs it; the checker judges the head merged onto the trunk, for pull requests into the trunk named main only and for hq none, and until the isolated run step exists (issue 1309) it runs a change's code without the sandbox, as today's checks do (ADR 0484 §2, §3, §5, §8, §11). `mesh/delivery-group` stays the delivery's view, not a required check. Wherever
  this design says both checks passed, they read this one status.
 - **hq is checked like any repository, by Go tests.** hq's four checks (records, the reading order's index, the development cycle and
  the words) are Go tests in one package at hq's root module, which holds no other Go code; the checker runs them through the Go build