project creatortrack scripts multitenant productization gaps 20260715T173100

name: CreatorTrack Scripts/voice-profile build: multi-tenant productization gaps description: Four Justin-only shortcuts in the CreatorTrack social-data/voice-profile pipeline block other users from using it as-is; data layer itself is already multi-tenant. type: project

The CreatorTrack Scripts app (voice-profile-from-social-data pipeline: YouTube/IG/FB/TikTok ingestion + structure extraction + voice profile + script generation) has a fully multi-tenant data architecture (workspace-scoped RLS, no hardcoded Gus references, per-workspace pipeline args), but four access-layer shortcuts were taken to move fast on Gus's data and need productizing before other users can onboard:

  1. Meta system-user token — Justin's Business Manager pre-authorized his own assets. Other users need Facebook Login for Business OAuth + Meta App Review per scope.
  2. TikTok sandbox app — Gus is the registered test user. Needs TikTok production audit (5-10 days, requires demo video).
  3. Transcripts via yt-dlp — one channel, residential IP, one-time scrape; doesn't scale (per-IP rate limits across many users). Open question: per-user OAuth + captions API, or Whisper on GPU for caption-less creators. Biggest open product question.
  4. LLM calls on Justin's Claude subscription — free at his margin; needs metered billing. CreatorTrack already has BYO-key infra (user_llm_keys, encrypted) — extraction/profile/generation jobs just need to resolve per-workspace providers instead of hardcoding the subscription.

Also known build gaps (not blockers): IG retention is NULL (Instagram hides duration) but could borrow duration from a cross-post-linked YouTube twin for a free retention win; cross-platform rollup analytics (one concept's combined performance across all 4 platform uploads) isn't built, only per-platform link chips; IG/TikTok DM sync stubbed; voice profile trains on YouTube transcripts only (correct, but worth remembering as a scope decision not an oversight).

Why: Justin asked directly whether this build is duplicable for other users someday — this is the honest ledger of what needs to change before it is, and would otherwise require re-deriving from scattered code/comments.

How to apply: Before pitching CreatorTrack's social/voice-profile pipeline as multi-tenant-ready, check these four items first. When Task 19 (docs pass) runs, this should get logged as its own phase-3 plan file (Meta review, TikTok audit, transcript strategy, BYO-LLM wiring) as a decision queue — confirm that happened, or write it if it didn't.

[auto-memory session 60d132de-4659-485c-8044-427af0ccce7f, confidence 0.70, mode staged]