Skip to content

Append-only capture. One idea per bullet. Promote to Tasks/ when ready to work.


  • MBR MVP: spec well with Gemini + others, then submit to Cursor (Composer 2) / CC / Stitch (stitch.withgoogle.com); savings first (categorize cashable vs non, chequing; quantify year-1 + 10-yr benefit); build savings functionality now — fastest-current rate data is itself a feature (“first to know”); quantify Talbot’s own situation as test case.
  • F.A.S.T. UI/UX standard: consistent progressive interface for every education/analysis experience (title → adaptive sidebar → next steps/related links), mobile-first → tablet → desktop, AI voice-bot help button; micro-website format as the model (c:\tmp\ScreenShots\keep\comet_JcK17CcoYY.png).
  • MBR logo/component animation: transition to $ like SDC’s; MUST use the SDC entity-component approach that works on iPad/iOS (current approach fails there).
  • gstack (Garry Tan / Y-C): plan-design-review workflow for a solo fintech founder — https://alirezarezvani.medium.com/7-gears-one-founder-what-garry-tans-gstack-reveals-about-building-solo-with-claude-code-in-2026-193a69e31ab1
  • Backrest architecture to model: https://medium.com/codex/i-used-to-be-a-better-software-engineer-than-ai-claude-opus-4-7-changed-that-68991ac6b5b3
  • Content pipeline: extract AI Studio session notes to markdown (esp. viral referral-engine ideas); convert Globe clippings to .md + AI-extract all strategies benefiting MBR/SDC.
  • Extra backup habit noted in export: c:\tmp\bak\MBR\.
  • Client-data infrastructure (OPEN — Talbot’s unanswered question from archived myMBR-OS task, 2026-04-08): accounting/billing is a core infrastructure domain alongside CRM — plan is QuickBooks 2017 desktop → QuickBooks Online (enables integrated automations); must define what data lives where; client data is a special subset requiring absolute privacy separation and the highest backup tier. Needs an architecture decision when users arrive (pairs with Projects/CRM/SPEC.md).