Weekly summaries
Draft, review, finalise — and the action items that land on the board.
Three states
A draft is generated
From what actually happened in that week's feed. An empty week gets no summary — a summary of nothing only fills the space with prose.
You correct it
A draft is a proposal, not a report. Action items can be added, removed or rewritten.
You finalise it
On finalising, the action items become tasks, and their initial owner is whoever finalised. Ownership is reassignable, and unassigned is a real, visible state.
Where a week starts and ends
Weeks are precise, non-overlapping ranges and every moment belongs to exactly one of them. The first day of the week is configurable.
Indicators use the same definition, so a weekly summary and a weekly indicator always mean the same week.
If no language model is configured
Generating a draft needs a model. Without one, the request fails cleanly and nothing half-built is left behind.
The rest of the cycle — action items, ownership, ticking — works with no model at all.
Read this next
- Work, tasks & PulseWhere tasks come fromFour sources, and one rule that keeps the board from filling with noise.
- Work, tasks & PulsePulseEngagement cards, ordered by which one needs attention now.
- Assistant & searchWhen the assistant cannot answerFour different states, and why none of them invents an answer.
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.