Project gus affiliate link in bio program
name: Gus the Bass affiliate/creator stack program approved, Cloudflare-edge architecture description: Master plan for Gus the Bass affiliate/link-in-bio program: CT app 'Link In Bio', Cloudflare edge for public surfaces, brand sites Claude-built and not Michael-accessible type: project
Justin approved a multi-phase program to build out the Gus the Bass creator/affiliate stack, spec'd via /feature-plan and written to memory/plans/affiliate-click-foundation-2026-07-08.md.
Key decisions locked in:
- CreatorTrack app name: "Link In Bio" (route /link-in-bio, DB namespace stays links.* internally). This is the Michael-editable module, Gus-scoped.
- Robustness requirement drove architecture: public money-making surfaces (bio page, click redirects /r/<id>, email capture /c) must survive a home internet outage, since CreatorTrack and gusthebass.com currently live on home infra (Console, media-server). Solution: these move to Cloudflare edge (Pages + Workers + D1 + KV), effectively $0 at Justin's scale (ceiling ~$5/mo only past ~3M clicks/month). Home CT becomes editor+reporting only, syncing to/from D1 with idempotent upserts so an outage never loses data.
- Brand websites (gusthebass.com, justinwieb.com) are Claude+Justin-built, deployed to Cloudflare Pages, and explicitly NOT Michael-accessible — separate from the Link In Bio and Storefront CT modules Michael does touch.
- Control model: Justin owns all backend/infra/API-credential layers; Michael only ever gets CreatorTrack UI scoped to the Gus workspace (per-app permissions already exist).
- Master stack table (11 layers: bio page, link tracking/Dub, affiliate networks, analytics/PostHog+Affilimate, email/Mautic+Resend, CRM, Discord community, Whop course, Stripe payments, brand sites, contacts spine) is now the top-level roadmap in the plan file, phased 1-8.
- CRM direction: don't rebuild HubSpot — CT's existing CRM tables need one canonical contacts table keyed by email, with tags (shopify-customer, course-buyer, pdf-downloaded-X) and synced events from each source (Shopify, email capture, course, downloads). Framed as medium effort, not a big build.
Why: recorded here because it spans multiple future sessions and decides file locations, naming, and access boundaries that would otherwise need re-litigating.
How to apply: when picking up Phase 1+ tasks in affiliate-click-foundation-2026-07-08.md, use the Cloudflare-edge/CT-editor split and the Link In Bio naming as settled, not open questions. Don't route brand-site work through CreatorTrack or give Michael access to gusthebass.com/justinwieb.com build tooling.
[auto-memory session d316bfec-dd4c-4598-92d1-2ec51bac5a91, confidence 0.85, mode direct]