A morning report that knows what to ask
Before I can decide what matters today, I have to find it.
My work lives across notes, messages, tickets, documents and a calendar. I built a morning-report workflow to bring that context together, check whether tasks are still open, and show me what an agent can prepare before I start opening tabs.
- GatherNotes, messages, calendar and linked work
- ReconcileCheck sources, remove duplicates, find completed work
- ProposeAgent can prepare · needs approval · needs me
- ReviewI choose what happens next
Walk through a morning
Fictional data, preset decisions. This demo does not read accounts, call a model, or perform tasks.
1. Gather the evidence
- Note: Summarize the workshop proposal.
- Message: Can you summarize that same workshop proposal?
- Note: Follow up about Thursday’s tour.
- Calendar: Thursday tour accepted by both people.
- Message: Send the workshop announcement.
- Calendar: 10:00 conversation with a collaborator.
- Note: Handle the equipment question.
Documents are unavailable in this fictional run. That gap needs attention.
2. Reconcile before making a list
- Combine the two requests for the same summary. Keep both source references.
- Drop the tour follow-up because the calendar shows it is already arranged.
- “Handle the equipment question” is ambiguous. Ask what outcome is wanted.
- Record the unavailable documents. A partial view must not look complete.
3. Propose work with boundaries
- Agent can prepare: Draft the proposal summary from available evidence.
- Needs approval: Send the announcement. Drafting can happen first.
- Needs me: Have the 10:00 conversation. The agent can help with prep.
- Needs clarification: What does “handle” mean for the equipment question?
These are proposals. Categorizing a task does not authorize executing it.
4. Review the work and the gaps
I can ask for the summary draft, review the announcement, and clarify the equipment question. The report itself sends nothing.
Real workflow difference: required integrations must pass a preflight before a report is generated. A missing required connection stops the run. Other empty or failed reads must remain visible in source accounting.
All four steps are shown below when JavaScript is unavailable.
The decision that mattered
I don’t want the agent to quietly decide that an ambiguous task is my problem, or claim something is finished because it sounds finished. The workflow asks when the evidence is unclear. In an unattended run, it leaves those questions in the report for me.
What the real workflow reads
Recent weekly notes, watched tickets, pull requests linked in my notes, calendar events, messages, and relevant documents. It checks the underlying evidence rather than treating an old todo as proof that work is still open. The report records sources and gaps, and I choose which follow-on work to authorize.