When it arrives
The brief sends at 07:00 in your workspace’s own time zone — not ours, and not UTC. A customer in Auckland and a customer in Denver both get a brief that says “this morning” and means it. Six mornings a week it is the short daily edition. On Monday, again in your own time zone, it is the Monday note: the week’s work and what is showing up from it.The daily edition, in order
1
The artifact, first — or not at all
The newest finished piece of work since the last brief: a page rewritten, a pull request opened, an outreach draft filed. If there is nothing to lead with, this section is absent — the brief does not manufacture a highlight.
2
What needs you
Up to three decisions waiting on you: the Inbox’s top three, in the same order. The same problem is never listed twice. This is the same list as Inbox → Waiting on you; the brief is a pointer to it, not a second copy of it.
3
The numbers
Counts, with the sample size behind each one — never a percentage on its own, and never a day-over-day comparison. One day is too small a window to compare honestly; see How we collect data for why.
4
What we read again, and when
Shown when re-reads are scheduled: at most five prompts, soonest first. The date shown is the day the re-read is actually read, a few days after its +7, +14 or +30 day mark, once its window has fully happened.
5
Changes we saw on your pages
Shown when a change on one of your pages was first seen, or had its before-and-after decided, the day before (the week before, on Monday): at most three, moved first. Each is the page change card’s own two sentences, what changed and what was measured, never joined by a “because”. These lines alone never send a brief on an otherwise quiet day.
Quiet days send nothing
If there is no artifact, nothing needs you, and nothing has changed, no daily email goes out. A quiet day is not a failure to report on; it is the absence of anything worth interrupting your morning for.The Monday note
The Monday note answers a different question from the daily brief: what did the agents do for you this week, and is any of it showing up yet? It covers the seven days before Monday in your time zone, and every number in it carries its own dates. The subject line leads with the work: “4 shipped this week · OpenAI’s crawlers fetched /vs/dentrix 41 times”, or “Nothing shipped this week · …” when nothing did.What it says, in order
Shipped work and the early signals come first, because they are what can honestly be shown in a workspace’s first weeks. Citations and goal pace take longer, so they come after.1
Status
One line on your goals: how many are ahead of pace, on pace, behind, or not measured yet. A workspace with no goals reads “No goals are set for this workspace yet.”
2
Shipped
How many pieces of work were delivered this week, by kind (“We shipped 4 pieces of work this week: 2 page changes, 1 pitch and 1 pull request.”), then the newest three, each with its link and, for work that went live on a page, the day it did. Each piece of work is counted once, however many steps it took.A week with nothing delivered says “Nothing shipped this week.” in those words, followed by how many items are waiting on you when any are. If the delivery record could not be read that morning, the section is left out rather than printed as a zero.
3
Early signals on the pages we changed
The pages that delivered work changed and that went live in the last seven days. An open pull request, or a rewrite nobody has published yet, is not a changed page.For up to three of them, most fetched first, how often AI crawlers fetched the page after it went live: “OpenAI’s crawlers fetched /vs/dentrix 41 times between 24 and 28 September. The page went live on 24 September.” Only verified crawlers count; a request that only claims to be one is left out. The two facts sit side by side, and the note never says the change caused the fetches.Then Search Console’s impressions and clicks on up to ten of those pages, with the days they cover and a note that Search Console trails today by two days.When something cannot be counted, the note says why instead of printing a zero: the crawler snippet is not installed, crawler data could not be read that morning, Search Console is not connected, Search Console did not answer that morning or has not been asked about the changed pages yet, or the pages went live inside its two-day lag. A week in which no changed page went live says so, because there is then no page to count anything for. If neither source could be read at all, the section says “Crawler and Search Console data was unavailable this morning.” and the note still sends.
4
Changes we saw on your pages
Up to three changes the crawl saw on your own pages during the week, each with what it matched and what was measured. Shown only when there are any.
5
Citations
How many answers named or linked you for the first time this week, with up to three of them: the engine, the day, and the prompt it was answering. Then the re-reads that came back this week, as counts with their n: in how many prompt and engine pairs the difference cleared the sampling noise.
6
Goals
Each goal’s pace, in the goal’s own words when they pass the same honesty rules as the rest of the note, and in plain words (“on pace”, “behind pace”) when they do not.
7
The first eight weeks
While your workspace is in its first eight weeks, and always in its first Monday note, the note says which week you are in and what to expect. See What to expect, week by week.
8
Next
Up to three pieces of work you approved that the agents have not shipped yet, oldest approval first. “No approved work is waiting to start.” when there is none. Then what we read again, and when.
9
What needs you
Up to three things waiting on you, the same list as the daily edition.
10
One observation, and one quote
One observation, stated as a count with its sample size — never a bare percentage. One verbatim answer quote from a real model response, word for word, never paraphrased.
What to expect, week by week
The note, the app when you sign up, and this page show the same four steps:
The steps describe what we measure and roughly when it can first appear. They are not a promise about what the engines do with the work: we guarantee the work itself.
It always sends
The Monday note sends even on a quiet week. A week we found nothing more than “Nothing shipped this week” is itself worth saying out loud; suppressing it would make Attensira look broken instead of quiet.Getting the Monday note in Slack
The Monday note can go to email, to a Slack channel, or to both. Email is the default.- Connect Slack under Customize → Connectors.
- Open Settings → Notifications and, under Monday note, pick the Slack channel to post in. It is one channel, shared with the win message under Wins.
- Turn on Slack.
The same brief, wherever you read it
The email, the Slack post, the app, and your own tooling all get the same brief, composed from the same data each time rather than separate renderings that can drift apart. Pull it yourself with theget_brief MCP tool, or over REST with GET /v1/brief. Both take an optional date (YYYY-MM-DD) for one of your workspace’s past days.
On a Monday the response also carries order: the note’s section keys in the order it prints them.
A past Monday’s note shows the crawler and Search Console numbers stored when it was sent that morning, not this week’s. If none were stored that morning, the early-signals section is left out rather than filled with this week’s numbers.