From 8f7c23da7d7a340b80a29e764467c46f833ca847 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 23 Oct 2026 16:10:44 +0200 Subject: [PATCH] Make a timer that writes state, or a rule in code that overrides a person, a change the review asks (issue 1903) --- 00-META/process/07-feature-branches.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/00-META/process/07-feature-branches.md b/00-META/process/07-feature-branches.md index 0a43b589..8c027a15 100644 --- a/00-META/process/07-feature-branches.md +++ b/00-META/process/07-feature-branches.md @@ -230,6 +230,14 @@ issue whether it is being fixed in between, after the delivery, or waits, and on further case, a nicer form: the reviewer opens it with `issue-tracker.open` and names the number in its report, and the round does not wait for it. What a round asks is only what makes the change wrong against its issues, their acceptance criteria and its decisions. +8. **A timer that writes state, or a rule fixed in code that overrides what a person sets, makes the change + wrong.** The mesh is NATS-native: a part says what happened as an event and acts on events; nothing polls + and rewrites state on an interval, and a policy the operator can change is a setting the module declares, + never a constant. The reviewer reads every new or changed interval, ticker, sleep loop and periodic + run-once in the change and asks of each: what event should drive it instead, and what setting turns it off. + One with no answer is a change asked. On 2026-10-23 the forge module's loop rewrote every repository's + branch protection every ten minutes from rules in its code and undid the operator's changes at the forge + (issue 1903). ## Step 3 — Check (no review)