Project ct voice profile productization gaps

URL: https://mkdocs.justinsforge.com/memory/general/project_ct_voice_profile_productization_gaps/

Identified 2026-07-15 during the CreatorTrack social-meta-ingest + voice-profile build (workspace 85, Gus Outdoor). The data architecture is fully multi-tenant by design (every table workspace-scoped with RLS, no hardcoded Gus references, reviewers actively enforce this), but the access layer has four deliberate Justin-only shortcuts that let the build move fast on real data:

  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. Other users need a TikTok production audit (5-10 days, requires a demo video). Same app/code, audit is paperwork.
  3. Transcripts via yt-dlp — works for one channel on a residential IP, one-time scrape. Doesn't scale across many users (per-IP rate limits). Open question: per-user OAuth + captions API, or Whisper on GPU for caption-less creators. Flagged as the biggest open product question.
  4. LLM calls on Justin's Claude subscription — free at his margin. CreatorTrack already has BYO-key infra (user_llm_keys, encrypted); extraction/profile/generation jobs need to resolve per-workspace providers instead of hardcoding Justin's subscription.

Why: Justin asked directly whether this build would be duplicable for other users one day. None of the shortcuts require rework, the seams are already in the right places, but none of them are free — each is a distinct piece of future work (OAuth flow, platform audit, ingestion strategy, billing wiring).

How to apply: when scoping a phase-3 plan for CreatorTrack's Scripts/voice-profile feature (or any social-ingest expansion) for multi-user rollout, this is the starting checklist. Don't assume the pipeline is ready for other users just because it's multi-tenant at the data layer.

[Claude Code]