Answer A-490l: mesh-config wakes on its inputs alone; one timer for its real deadlines; a proposal naming a pull request is refused

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
2026-11-19 23:04:25 +01:00
parent bbeb890399
commit a09270d6b8
@@ -2111,3 +2111,10 @@ the principle that settles it, cited as "design 47 G A-n".
view again on its next event and runs the starts it held once the view reaches that revision, with no timer. (Live
2026-11-19 22:40: the catch-up took mesh-delivery 0ea4b60d in, writing six modules, and said nothing, so no
pipeline started for them.)
- **A-490l** (issue 1982, ADR 0681, ADR 0426 §3, ADR 0580 §1; principles 1, 3 and 11) mesh-config wakes only on an
input that changed and reads its own states from their watched copies; it keeps no tick. Its pull sweep and its
read of the router's record run once at start and then only on their events. One one-shot timer stands, set for the
earliest real deadline it holds: a waiting proposal's end, an unanswered retirement's second ask, and a rename
window's held finding (seven days), so each comes in a quiet mesh too. The timer's floor is a setting with a default,
not a constant. A stored proposal that names a pull request is refused on its approval, saying why; such proposals
are listed on the issue with ADR 0681 §7's keys before the removal is delivered.