Feedback creatortrack no hardcoded single tenant

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

Observed across the CreatorTrack social-meta-ingest build (2026-07-15): even though the entire feature was built and tested exclusively against one real brand (Gus Outdoor, workspace 85), the code-review passes actively enforced that nothing anywhere hardcodes that brand or workspace, every table stays RLS/workspace-scoped, and pipeline scripts take workspace args rather than defaults.

Why: CreatorTrack is a multi-tenant product; Justin's own data is the only real dataset available during a build, so the natural failure mode is code that quietly assumes "the workspace" means workspace 85. Catching this at review time, not at future-customer-onboarding time, is cheaper.

How to apply: when reviewing or writing CreatorTrack app code (any app, not just social/scripts), flag hardcoded brand names, workspace IDs, or account-specific defaults as a should-fix even if the feature currently only serves one user. This is a standing review criterion, not specific to this feature.

[Claude Code]