Synthesis Meeting Transcripts

A protocol for fetching AI-generated meeting transcripts from the user's Gmail and Google Drive into a local markdown archive. Designed for teams where Google Meet + Gemini (or equivalents) produce meeting notes + word-for-word transcripts that live in Google Docs, and the user wants them mirrored locally alongside their project context.

The earlier release notes and rationale are retained in references/earlier-version-history.md. Unknown authentication, tab enumeration, or archive coverage is a visible gap, never a no-source attestation.

Binding rules

1. Declared means fetched. A ritual sync runs Step 0 below: enumerate the declared set, fetch every member, and account for each as fetched or as an unclosed gap. Relevance is judged after fetching, never before.
2. Unknown coverage is a visible gap. Unknown authentication, tab enumeration or archive coverage never becomes a no-source attestation, and the meetings watermark never moves past an unsaved doc or a meeting that may still be under way.
3. A Drive search listing cannot prove a window complete, because it omits the provider completeness flag. A full page, a next-page token, an incompleteSearch warning or a failed search leaves the window open; say so in the report.
4. The verbatim transcript is the only primary source. Fetch it in full whenever the source has one. The Gemini email is for discovery only, never for content.
5. Select the transcript by the document's stable tab ID, never by order or a regular expression; a title only when exactly one tab in a complete tab list carries it. Only a complete tab list establishes transcript-tab-absent.
6. Verify both halves landed with verify_transcripts.py --file <exact saved file> --json before calling a meeting fetched. A directory scan does not substitute.
7. Use the <!-- VERIFIER: no-source-transcript --> marker only when the source truly has no transcript, with a one-line reason beside it.
8. Never derive attribution from a tool summary. Who warned, decided, approved or owns comes from the verbatim transcript; if it does not say, keep the passive form.
9. A scanned commitment is a candidate until the principal confirms it in the same turn. Stamp each confirmed one with exactly one owner; nothing is created from scanner output alone.
10. Cross-check every date against at least two independent signals before writing a dated file.
11. Never leave transcripts in ~/Downloads/. Commit them to transcripts_repo, whose pre-commit gate refuses a summary saved as a transcript.