Say the uplink verbs shipped optional, not staged: a progressive insight in ADR 0241, corrected in to-be 48

The controller that merged (mesh-controller #116) dropped the staged seat and marked both verbs optional, stored in the seat's row and read back optional.
2026-10-07 21:18:11 +02:00
parent e6a17b8bf6
commit 91daabaa97
3 changed files with 21 additions and 3 deletions
@@ -144,6 +144,18 @@ Nobody opens a terminal on the machine. The verbs are *staged*: promised and rou
 of holding the seat, and never stored in the seat's row. A controller older than them reads the row and
 would refuse every holder of its time. A later change requires them once both holders serve them.

+> **Progressive insight — 2026-10-07.** The verbs did not ship *staged*. This rule said they were
+> "promised and routed, but not yet a condition of holding the seat, and never stored in the seat's row",
+> and the check for rule 8 in the table below said "a staged verb is never seeded into the row and comes
+> back from the binary". The controller that merged (mesh-controller #116) has no staged seat. It marks
+> both verbs optional (`Verb.Optional`). An optional verb is promised, so a claim serving it is accepted,
+> but it is not required, so a holder serving neither still holds the seat. It is seeded into the seat's
+> row like any verb, and it stays optional when read back, because the mark is taken from the seat as
+> compiled. Mesh-controller's `TestTheUplinkVerbsReadBackFromTheRowStayOptional` holds that. The
+> decision is unchanged: promised now, required once both holders serve them. The general rule for a verb
+> added to a held seat is [ADR 0246](0246-a-seats-new-verb-is-promised-before-it-is-required.md), from
+> [issue 298](../04-ISSUES/298-a-new-seat-verb-deadlocks-across-two-repositories/00-report.md).
+
 ## Consequences

 - **The VPN rewriting the laptop's file is said within about a minute,** naming FortiClient from its