Build a weekly team-meeting deck generator for a sales/BDR team. The goal is to turn a live forecast plus a few manual notes into a warm, discussion-led meeting deck — people first, numbers second — so the team lead never hand-builds slides each week. All routes should be tenant-authenticated. Trigger and entry. Serve a webpage at /meeting that acts as a holding page: a gallery of every past deck as clickable blocks (the team's historical record). A "Create new deck" action reveals a notes form (meeting date, team updates, new starter, security notice, enablement theme, guest speakers) shown alongside a chat panel. Two paths to build, one destination. The lead can either fill the form by hand or chat to an AI "meeting architect" agent that fills the same fields conversationally (keep the form in sync as it talks), builds the deck on request, or edits an existing deck in place. Both paths converge on a single generate endpoint. Generation. On submit or on the agent's request, POST the notes to a generate step that pulls the current week's rows from the team's forecast source — Google Sheets, or whatever spreadsheet/data source your team uses — rolls up the headline numbers in code (team number, goal, attainment, to-go) so they're authoritative and never invented by the model, then calls an LLM (Claude via Anthropic — or your preferred model provider) with a fixed coaching voice and a defined output schema to draft each deck section. Output and history. Save each finished deck as its own file in a persistent volume (one file per deck so concurrent generations don't collide) and render it as a presentation-ready slide deck at a /deck webpage. List past decks back on the form, each reopenable in the agent's edit mode. Keep the whole thing read-only against the forecast source — nothing writes back to the spreadsheet or any external system. Use connectors for all credentials; no secrets in code. Tools used: Google Sheets, Anthropic (Claude), 3B named volumes, 3B workflow connector