Almanac has synced my calendars for months. Weekly reads that feed and synthesises the week. The result was accurate and useless. Twelve meetings, mostly Tuesday through Thursday is a shape, not work. No amount of prompt engineering extracts an outcome from a title and a guest list.
The Pointer Was Already in the Payload
Then meeting notes started arriving attached to the Calendar events themselves. The interesting part isn't the note quality. It is that the file ID sits inside the same Calendar API payload Almanac already pulls on every sync. No new provider, no scraping, no Drive crawl. Setup cost, zero.
During sync, Almanac exports each attached doc as plain text and keeps three fields: action items, decisions, unresolved questions. Summary prose gets dropped.
Only the Extract Crosses the Boundary
Almanac exposes one endpoint returning those three fields per event, plus title and start time. Raw doc content never leaves Almanac. The endpoint is declared in its capability list, so Gopher discovers it like everything else and proxies it to Weekly. That is the rule the estate keeps converging on: apps hand each other the extract, never the source material.
What Changes in the Synthesis
Weekly inserts notes above last week's event list, so the model reads what was decided before what was scheduled. Instead of saying a design review happened on Tuesday, the synthesis says five action items came out and two are still open. The unresolved-questions field matters most, because it is the only part of a week that reliably disappears.
It compounds. Weekly's outstanding items pick up meeting carry-forwards instead of being email-only. Meeting Prep starts from what the last one concluded. Gopher can answer what did we decide without me remembering which meeting it was. One artifact, produced by someone else's tool, made three apps better at once.
The Estate, End to End
Recorded from the demo build, so the data is synthetic and the flows are real.
Three Things Were Broken
Filming the demo is what made me check whether the feature actually ran. It did not.
The extraction function was declared async but called without await. Python doesn't complain, so a coroutine object went into a JSON conversion, raised outside the surrounding try block, and failed the entire sync for any calendar with a single Doc attachment. The function does no I/O, so the fix was deleting one keyword.
The fetch helper looked up export links on a top-level Drive resource instead of the per-file one, so every doc resolved to nothing. Two calls collapsed into one against the correct file export link.
The third is still open. The scope I asked for covers only files the app created, and a meeting-notes doc belongs to whoever ran the meeting. Reading it needs full read access to my entire Drive, and Google offers nothing in between for files attached to events I am invited to. That is a consent decision, not a bug, so it stays as is.