diff --git a/00-META/process/07-feature-branches.md b/00-META/process/07-feature-branches.md
index cfcfb9b4..65210632 100644
--- a/00-META/process/07-feature-branches.md
+++ b/00-META/process/07-feature-branches.md
@@ -246,7 +246,7 @@ a minute. After every answer or timeout it reads the state from the verb that ow
 `mesh-controller.plans`, `knowledge-base.get`), because an event only wakes it (ADR 0367). It finishes, and so wakes
 the lead, when the state changes or the wait passes its bound. The lead never sleeps or polls by hand to wait.
 
-**Every five minutes, every two minutes while a delivery plan runs, and at once when something lands, stops or
+**Every ten minutes (the operator, 2026-10-17), every two minutes while a delivery plan runs, and at once when something lands, stops or
 needs the operator,** the lead reports, in one of the two layouts below (the operator, 2026-10-16: an overview
 of the issues, often). Times are local and absolute, from the clock (`date`), never guessed; every number has its
 unit and its bound or baseline; an issue is named by its number and a few words, never by its number alone.