# Creator-facing dashboard product framing

Session learning from AutoShorts Dashboard bootstrap.

## Trigger

Use this note when building or polishing a creator/customer-facing dashboard that sits on top of internal automation, AI generation, bots, agents, or production pipelines.

## Lesson

Do not let the UI expose the internal production machinery unless the user explicitly wants an operator console. A technically correct MVP can still feel wrong if the visible language says “bot”, “AI pipeline”, “Jarvis”, “Hermes”, “human gate”, etc. when the product is supposed to look like a professional workflow app.

## Preferred framing pattern

Instead of internal automation language, frame the product around the user-visible work objects and decisions:

- prepared packages / prepared videos
- content inbox / review queue
- metadata review and editing
- account selection
- schedule / timing
- private upload approval
- upload status and audit trail
- topic pipeline / topic library
- idea backlog with links, keywords, notes, short explanations

## Practical implementation steps

1. Add a durable repo document such as `docs/product-direction.md` that captures product framing, forbidden UI terms, preferred terms, primary workflow, and immediate UX backlog.
2. Scan visible frontend files for internal terms before claiming the UI is product-ready.
3. Keep internal integration names in backend/docs only if needed, but avoid surfacing them in navigation, page headings, cards, and empty states.
4. Build empty states around real next actions: upload prepared package, scan import folder, review metadata, approve private upload, add topic/idea.
5. For content-operation dashboards, prioritize topic/idea database and review/approval workflow before provider API glamour.

## Example visible copy replacements

- “Jarvis imports” → “Recent prepared packages”
- “Jarvis briefs” → “Topic pipeline”
- “Human gate” → “Creator approval” / “Approval required”
- “AI-generated videos” → “Prepared videos” unless platform disclosure requires AIGC/synthetic-media wording
- “Bot produced” → omit production source; show package source/status instead

## Verification

- Run frontend build/typecheck.
- Browser-QA actual dashboard route, not only source scan.
- Console must have no JS errors.
- Snapshot/search visible frontend for forbidden terms.