Issue 313: history adopted at the switch was held for a person; ADR 0250 retires it and ends owed work the forge cannot do

03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md

@@ -4,6 +4,7 @@ status: designed
 code: []
 updated: 2026-10-08
 decisions:
+  - 02-DECISIONS/0250-a-merge-heard-only-from-the-buss-history-is-retired-and-owed-work-the-forge-cannot-do-ends.md
   - 02-DECISIONS/0249-a-delivery-groups-order-rules-have-a-precedence-and-a-declared-order-outranks-them-all.md
   - 02-DECISIONS/0239-a-delivery-is-owned-by-the-mesh-delivery-module-and-runs-from-commit-to-delivered.md
   - 02-DECISIONS/0238-a-commit-is-the-build-at-hand-one-commit-one-change-plan-checked-off-the-trunk-and-published-only-on-it.md
@@ -73,12 +74,18 @@ allows.
 | published | merged on the trunk its modules follow, its walk opened and asking nothing; it waits for its turn or its word | 30 minutes | `superseded` when a newer delivery took over its walk; `go` when its walk started |
 | held | it waits for a person | 1 day | nothing: it is the operator's |
 | delivering | its walk runs; its builds are asked and registered tier by tier | 2 hours | `delivered`, `failed` or `superseded`, as the walk's record says |
-| delivered, failed, superseded, stopped | final | — | — |
+| delivered, failed, superseded, stopped, retired | final | — | — |
 
 The transitions are those of ADR 0239 decision 2. A delivery that is merged while not `ready` goes to
 `held`. Its check did not pass, and only a person decides that it goes on. A delivery merged with no walk
 opened for it within ten minutes is held too, saying so: nothing it moves follows that branch, or the merge
-was not heard. Nothing waits silently. **Nothing of a published delivery is registered before its walk
+was not heard. Nothing waits silently.
+
+**History is retired, not held** ([ADR 0250](../../02-DECISIONS/0250-a-merge-heard-only-from-the-buss-history-is-retired-and-owed-work-the-forge-cannot-do-ends.md)).
+A delivery made from the forge's word at its merge, heard fifteen minutes or more after that merge, with no walk
+of it open, was replayed from the bus's history: it reached the machines before this owner was there. It goes
+to `retired` at adoption, before any check, hold or walk, and its pull request is not told. A held delivery that
+fits the same rule is retired by a person's `retire-history`, never released. **Nothing of a published delivery is registered before its walk
 starts**, because a send carries every registered build that waits on its machine (ADR 0236 §4a), and a
 build registered before its turn would be carried by somebody else's send.
 
@@ -113,15 +120,16 @@ them.
 In this order, each by its owner:
 
 1. **kept**: mesh-delivery puts the delivery in its state (`deliveries`, one key per delivery; `groups`, one
-   key per group). Nothing is said before it is kept. What it owes outside is kept with it and retried until
-   done;
+   key per group). Nothing is said before it is kept. What it owes outside is kept with it and retried, later
+   each time, from ten seconds doubling to an hour. The forge's answer that what it is for does not exist ends
+   it at once, and sixty failed tries end it too, each said among the owner's refusals (ADR 0250);
 2. **said**: the event `mesh-delivery.transition` (and `mesh-delivery.group` when a group's derived state
    changes), with the delivery's id, from, to, event, why and plan summary, and no secret or address;
 3. **noted**: mesh-delivery asks the forge's holder (`gitea_note_append`) to append a line to the commit's
    note: the head while the delivery is off the trunk, the commit it landed as once it is on it, and at its
    end a line of what was executed there. The forge's holder writes it in its own repository as the forge's
    own account, and a line already there is not appended again;
-4. **reflected**: the delivery's view, one comment on the pull request with the state, the plan, the machine
+4. **reflected** (not for history, whose pull request the forge may no longer hold): the delivery's view, one comment on the pull request with the state, the plan, the machine
    steps and the group, kept current (`gitea_delivery_view`); the status `mesh/delivery` on the head, and
    `mesh/delivery-group` on every member's head (`gitea_commit_status`). Every status links to the pull
    request, `mesh/merge-gate` among them.
@@ -142,6 +150,7 @@ In this order, each by its owner:
 | `release` | a held delivery to delivering, with why: a person's word |
 | `stop` | any delivery not final to stopped, with why; its walk is ended through the controller |
 | `close` | H2's only verb: the transition the table names for a stalled delivery, refused otherwise |
+| `retire-history` | held history to retired, with why: one by id, refused when the rule does not take it, or every held one, answering how many and naming those it left; `dry` changes nothing |
 
 **The controller's verbs for it** (on the mesh-controller seat): `delivery-plan`, `delivery-order`,
 `delivery-check` (a group's heads composed, or one head checked again), `deliver`, `delivery-stop`,