Weekly report¶
The weekly report is a recap of what actually happened across your missions in the past seven days. It is the one routine that looks backwards.
Why it exists¶
Every other routine is about the next move. That leaves a gap: at the end of the week it is hard to see what the work added up to. The daily notes and cards are scattered across a week, and a week of at-risk verdicts reads differently in one place.
The report puts it together for you, in the past tense, so you can read it once on Monday and know where you stand without opening every mission.
What it does¶
It reads, for each mission, the updates written this week, the insights captured and the tasks closed or materially changed. It then writes a single document:
- a heading per mission that had signal, followed by past-tense bullets covering what closed, the key insights and the verdicts written this week;
- missions with no signal in the week are left out, so there are no empty headers.
It is deliberately limited. Past tense only: what happened, with no next moves and no forecasts. It proposes nothing, so there is nothing to approve.
What you see¶
Two things, both created in one run:
- An output, standalone, which you can read, edit or share like any other output. It is not tied to a task and does not become a publish request.
- A report card in your inbox that points at the output. It is information only: read it and clear it.
The card closes itself after a day, and the output stays. The X on the card discards the card, never the output.
When it runs¶
Weekly, on Sunday, so the recap is waiting at the start of the week.
Tuning it¶
- Turn it off if you do not run missions week to week. The report is noise in that case, and noise in the inbox costs more than the report is worth.
- Its quality tracks your missions. The report is assembled from mission updates, insights and tasks, so a week with few of those produces a short report, which is honest.
- Edit the output if you want to forward it. It is an ordinary document.