A meeting brief is only useful if it is ready before the meeting and short enough to read on the way to it. One that arrives afterwards has failed however correct it is, and so has one that takes five minutes to read, because the five minutes are the ones you no longer have. Everything below follows from those two sentences.
So it runs thirty minutes ahead. Not the night before, when you would read it and forget it, and not five minutes before, when you can no longer do anything about what it says. Thirty to forty-five minutes is late enough that "what changed" is still true when you walk in, and early enough to decide the thing it tells you is blocked on you, or to ask the one person who knows.
And it opens with one sentence. What is open against you, how much of it has stopped moving, and what was not shown. That sentence is composed in code from the rows themselves before any model is asked to write anything, and the model is told to copy it across character for character — a brief whose opening line was rephrased is rejected rather than published. Somebody with twenty seconds reads that line and nothing else and still knows what the meeting is about. Everything under it is there for the person who has three minutes.
What is in the rest is chosen the same way. Who is in the room and when this workspace last heard from each of them. What shipped, slipped or got blocked since the last time you met. What you still owe them, with the column, the age in that column and who holds it — the row no notetaker has, because it is a fact about the work rather than about the conversation. What they will probably raise, and why you expect it. Three to five questions, each naming the ticket it unblocks. Then what to decide before you join.
What is left out is chosen just as deliberately. It does not read your chat. It reads your mail only when you connect Gmail, only threads with the people in the meeting, and only to find what they asked for — the brief is still built on the work, which is the half nobody else holds. It does not read your calendar for anything but the meeting itself, and it cannot write to it — the step that reaches your calendar is handed only the read tools, so moving a meeting is not a thing it declines to do, it is a thing it has no way to do.
It also leaves out anything it would have had to guess. Where there is no record, the brief says "no record in this workspace" rather than offering a plausible answer you would then have to defend out loud. No sentence commits you to a date, a price or a scope that is not already written in a ticket the brief cites, and a review step reads the whole thing before you do and fails it on the first sentence that does — a confidently wrong delivery date is the specific harm here, because you will say it to the person it is wrong to.
It is a personal brief, so it contains only what one reader may see. The board is read as you: a ticket owned by a team you are not on is dropped entirely, never shown with a placeholder, and counted in the number the first line states. Who the brief is for comes from the run itself and cannot be supplied as a setting, so asking for somebody else's meeting to be prepped is refused rather than quietly honoured. That matters more here than almost anywhere else in Aestus, because this document is read aloud in a room with people from another company in it.
An event title, an agenda and an attendee's name are all text somebody outside your organization wrote. The step that reads them holds no access to your workspace at all, and the step that reads your workspace holds no tools. Neither half has both, so an instruction planted in an invite has nothing to act on: the worst it can do is make one brief wrong, which is what the review step is for.
Then it ends in work rather than prose. The brief is saved as a document on the day's prep ticket, the questions are added to that ticket, and every ticket a question unblocks is linked to it. Nothing is created — the ticket already exists before the run starts — so a retry cannot leave a second copy behind, and no ticket other than that one is ever edited.