The reason people check work on holiday is not that they expect something. It is that they cannot rule it out. So they look every evening, find nothing five times, and still look on the sixth — and the week off costs most of a week of attention anyway.
A daily digest does not fix that. It replaces the checking with reading, and by the third evening it has taught you that opening it was a waste of time. Then the one evening it matters, you archive it with the others. Anything that arrives every day is something you learn to ignore, which means the only useful version of this is one that almost never arrives.
So the whole design is about the evening where nothing is sent. Three things can interrupt somebody's time off, and each of them is about a cost landing on someone else or on work that has already stopped: another person is blocked by one of your tickets and cannot continue, a run on your work failed and nobody picked it up, or somebody put a ticket on you and it has sat there since. Your own ticket ageing on your own board is deliberately not on that list. Nobody else is stopped by it, it will still be ageing on Monday, and it is the one thing you would have found yourself.
Being one of those three is necessary and not enough. Each has to have gone untouched long enough for the same staleness rule the rest of Aestus grades a waiting ticket by — not a number chosen for this feature, so something cannot be urgent here and fine in tomorrow's standup. That rule reads whether anybody has touched the work at all, which is what keeps a colleague's afternoon of work from becoming your evening's interruption: if somebody is on it, you are not needed. A ticket with no recorded activity is never treated as an alarm either, because a missing timestamp is the cheapest possible way to manufacture a false one.
When nothing clears that, no run is created. Not a run that finds nothing — no run at all. The evening is recorded as a deliberate skip with its reason and it costs nothing, which is what makes it honest to leave the watch on for a fortnight.
The second half of staying quiet is not repeating yourself. Every item carries the ticket and the reason it reached you, and something already reported stays silent unless the shared rule says it has moved up a rung. Same thing, same state, nothing. Same thing, now worse, one more message. The record of what was already said is the tickets the watch filed for you, so it survives in the product rather than in a model's memory.
What does arrive is short, and every line says why it is in front of you. The counts are computed from records before anything is written, the headline is composed in code and copied across unchanged, and a rundown that rephrased it is rejected rather than sent. A line that cites no source fails the review even when it looks right, and a rundown that adds back something the bar deliberately held out is refused outright — that last check is what stops the message quietly widening into the digest it was built not to be. Twice rejected and nothing is sent at all, because a wrong message to somebody who cannot check it is worse than no message.
Some of those asks will not be answered, because you are not there. That is what naming a cover is for. You say who covers and how many hours a thing may wait, and anything that waits longer becomes that colleague's own ticket, assigned to them and due the day you are back. Both halves are needed: name nobody, or set no hours, and nothing is ever handed to anybody. It happens once per thing, not once a night, so a week away does not put the same ask in front of your colleague seven times. They have to be a member of your organization — a user id from anywhere else is refused and counted, never told anything. And work on a team they are not a member of is never put on their board: it is dropped, counted, and reported back to you, so you learn your cover has a blind spot rather than assuming it does not.
It sends, and only sends, where an admin said it may. That permission is granted in advance, bound to one destination and one automation, dated, and revocable — which is what lets an evening run post with nobody watching without inventing a second way to send. It has no permission to reply, to post in a thread, to email or to touch a calendar.
Then it ends in work rather than prose. Each item is filed as your own ticket, assigned to you and due the day you are back, so there is nothing to act on from a phone. And every rundown states what it left out: the rows on teams you are not a member of, the things it judged could wait, and the fact that nobody detected you were away — you said so.