Skip to content

Finance Google Slides Deck, 2026-06-12

URL: https://mkdocs.justinsforge.com/memory/handoffs/finance-slide-deck-2026-06-12/

You are a Fable 5 worker. Justin wants a new Google Slides deck built, pulling a few real figures from his finances. This is a presentation he is showing to someone (likely family), so it should look clean and celebratory, not a spreadsheet dump. Build the actual deck in his Google Drive and hand back the link.

The slides Justin asked for (in order)

  1. "We have paid off all credit cards!" — the headline win. Caveat: except Sip 'n' Serve (that one card/brand is not paid off). So the slide reads the celebratory line with a small honest footnote that Sip 'n' Serve is the lone exception.
  2. "I built a finance website to track everything." — he created a finance tracking website/dashboard. One clean slide announcing it. (It is the Forge finances surface; reference it by what it does, not internal jargon. If there is a real URL for it, you may show it.)
  3. Taxes — good news: getting ~$11-12k back on taxes this year, plus a note on how ERPNext is now set up as the books/accounting system (replaced QuickBooks, 5 companies seeded). Frame ERPNext as "our new accounting system is live and organized."
  4. "There's a secret in the living room." — a teaser/reveal slide. Keep it literal and intriguing as Justin wrote it; do NOT spell out what it is. Just the line, styled as a fun cliffhanger. (Context for you only, do not put on the slide unless Justin says so: Michael moved in 2026-06-10 with aquariums + fish.)

A title slide before slide 1 and a closing slide are fine if they help; keep the deck tight (aim ~5-6 slides total).

Verify the numbers before you put them on a slide

Robust over quick (feedback_robust_over_quick.md): do not invent figures. - Credit cards paid off: confirm against the real data. Finance data lives in forge/data/finance/finance.db (check forge/data/finance/COORDINATION.md FIRST before any read; it is a shared board with the ERPNext-migration + finances sessions). Also see ERPNext (CT 104, reference_forge_biz_apps) and reference_erpnext_daily_post. Verify that card balances are at/near zero (except Sip 'n' Serve). If a card still has a balance, tell Justin rather than overstating "all paid off." - Tax refund ~$11-12k: this is Justin's figure. Show it as the range he gave ("$11-12k"). If finance.db / ERPNext has a more exact number, you may use it; otherwise use his range. - If anything contradicts the headline, surface it to Justin in your findings; the slide claims must be true.

How to build the deck

  • Use Justin's Google account via the canonical helper: forge_google_user.py (multi-account user OAuth; see reference_google_access and reference_agent_integrations). Use the account that makes sense (personal [email protected] for a family-facing deck). Reuse the helper; never hand-roll OAuth.
  • Google Slides API: check whether the Slides scope is already authorized for the chosen account (forge_google_user.user_token(...) scope list, reference_google_oauth_per_account_scopes.md). If Slides is NOT in the granted scopes, do NOT block: fall back gracefully. Options in order: (a) if Slides scope is available, create the deck via the Slides API and share the link; (b) if not, build a clean Markdown/HTML deck and convert, or generate the deck content + a ready-to-paste outline and tell Justin the one step to grant the Slides scope. Pick the path that gets him a real, viewable deck fastest. State clearly which path you used.
  • Style: clean, modern, celebratory. Big headline per slide, minimal text, one number/idea each. No em dashes anywhere. Forge/Justin voice.
  • When the deck exists, always send the shareable link (feedback_drive_docs_send_link.md): print the webViewLink in your findings and notify.

Deliverable

Write forge/memory/handoffs/finance-slide-deck-findings-2026-06-12.md (mkdocs URL line at top): the verified numbers (with source), which build path you used (Slides API vs fallback), the deck link, and any figure that did NOT check out. Notify with the link.

Start

Read COORDINATION.md, verify the payoff + refund numbers, confirm the Slides scope, build the deck, share the link, notify. If a number is wrong, flag it; never put an unverified claim on a slide.