What starts the re-reads
Re-reads start when a change reaches the world:- a pull request Attensira opened is merged;
- a rewrite, an article or a copy item is marked shipped with its live URL;
- an article is published through a connector such as Notion;
- an off-site placement is verified.
prompt_ids given to propose_fix). A shipped change with no tracked prompts attached is not re-read.
Three re-reads: +7, +14 and +30 days
Each change is re-read three times, at +7, +14 and +30 days after it shipped. Each re-read compares two windows of the prompt’s daily reading slots:- Before: the 7 slot days before the change.
- After: 7 slot days centred on the +N date.
n), and none is a day-over-day comparison.
Is the change live?
Before measuring, the re-read checks that the change is on the live page:- For a rewrite or copy, the exact new text must appear on the page.
- For a new article, the page must load with content.
The verdicts
Every result is a single dated reading. A Moved verdict is what lets the morning brief, the receipt and the win plan use movement wording at all.
How a verdict reads
Each verdict, in its email and in the action log, opens with the windows it compared:Re-read at +14 days, read on 2026-10-06: 2026-09-15 to 2026-09-21 before the change, against 2026-09-26 to 2026-10-02 after it.
Where you see them
- Work → Shipped: each shipped item shows its latest re-read result, or Re-read booked with its date. See Work.
- The prompt page: Before and after lists this prompt’s re-reads with their samples, windows and outcome. See Prompts.
- The morning brief: What we read again, and when, at most five prompts, soonest first.
- The win plan:
rereads_atis the day the next booked re-read for that prompt is actually read. - Client reports: the re-read verdicts are the only place a client report uses movement language.