Issue 298 and ADR 0246: a seat's new verb is promised before it is required

Design 33 said a seat's verbs change additively, and section 3 made each one a condition of holding, so a verb added in the controller and served from the catalogue could land in neither order. It happened three times on 2026-10-07. Section 7 now says the three steps and how each is checked.
2026-10-07 21:14:20 +02:00
parent 921ff3e6c4
commit e6a17b8bf6
6 changed files with 230 additions and 2 deletions
@@ -208,6 +208,7 @@ python3 00-META/checks/index.py            fail if stale
 - **0237** — [A change is judged against the mesh that runs, before it merges, on the build seat](0237-a-change-is-judged-against-the-mesh-that-runs-before-it-merges-on-the-build-seat.md)
 - **0238** — [A commit is the build at hand: one commit, one change plan, checked off the trunk and published only on it](0238-a-commit-is-the-build-at-hand-one-commit-one-change-plan-checked-off-the-trunk-and-published-only-on-it.md)
 - **0239** — [A delivery is owned by the mesh-delivery module and runs from commit to delivered](0239-a-delivery-is-owned-by-the-mesh-delivery-module-and-runs-from-commit-to-delivered.md)
+- **0246** — [A seat's new verb is promised before it is required](0246-a-seats-new-verb-is-promised-before-it-is-required.md)

 ### Its tiers, from the bottom up