Space mail reading's batches 160 s apart, as ADR 0459 §15 now says

03-DESIGN/01-to-be/59-the-mail-web-client.md

@@ -156,8 +156,10 @@ mail-store (mesh-mail) ── MAIL: mail.<account>.message.added ──▶ mesh-
   says; then each mail, at most 3.5 KiB (its headers at most 512 bytes, its text cut to its first 3 KiB), a mail in
   a Junk folder said to be so. A batch asks for up to 40 s with `within` and collects with
   `claude_code_judged` (built under issue 508, recorded by ADR 0459 §14). Research 066 measured 1.9 to 3.1 s per
-  mail, so a batch of 10 takes about 19 to 31 s; the bound keeps an issue tracker's check that waits behind a batch
-  on the same machine within its two minutes (ADR 0278 §2), which research 066's 15 mails and 120 s would not.
+  mail, so a batch of 10 takes about 19 to 31 s. A batch starts at least 160 s after the previous one started, so
+  an issue tracker's check that waits behind a batch on the same machine ends within 115 s, inside its two minutes
+  (ADR 0278 §2), which research 066's 15 mails and 120 s back to back would not; mail reading then reads up to 225
+  mails an hour (ADR 0459 §15).
   Batches stay judgements; whether they become threads is issue 1417.
 - **Reading lessons.** When the operator changes a mail's mark or mail group on the page, `mesh-mail-web` calls
   `correct` and the correction is kept at once as a reading lesson (headers, the change, when; never body text),