# Creator-facing dashboard product framing — AutoShorts sprint notes

Use these notes when building dashboards that sit on top of an internal content-production pipeline but must present as a professional creator/publishing workspace.

## Durable lesson

The dashboard is not the machinery room. It should expose the creator's control objects: prepared packages, review, metadata, schedule, topic pipeline, approval, audit. It should not expose internal agent names, bot/AI production framing, or implementation gate labels.

## Visible-copy neutralization pattern

Before calling the UI polished, scan user-facing files (`README.md`, `docs/*.md`, `frontend/src/**/*.vue`, `frontend/src/**/*.ts`) for internal/product-leaking words such as:

- internal assistant/system names;
- bot/automation-agent labels;
- "human gate" / "human approval" implementation language;
- "AI-generated pipeline" production framing.

Replace with objects/actions the creator controls:

- Prepared package imports / Recent prepared packages;
- Import settings;
- Prepared package manifest;
- Internal production pipeline only in internal developer docs;
- Creator approval / Approval required;
- Prepared video package workflow;
- Synthetic media / AIGC disclosure only where legally or platform-relevant.

## Product-first dashboard cockpit pattern

A useful operations home should show actual next actions, not only empty SaaS cards:

- Ready for approval;
- Needs metadata;
- Scheduled private uploads;
- Uploaded private / uploaded draft;
- Failed actions;
- Recent prepared packages;
- Next topic;
- Ideas waiting for review;
- Current content pipeline;
- Quick actions: Review, Schedule, Add idea, Import packages.

## Prepared package workflow shape

Prefer a neutral import contract:

```text
storage/incoming/package_2026_06_06_001/
  video.mp4
  manifest.json
  thumbnail.jpg optional
  transcript.txt optional
```

```json
{
  "package_id": "package_2026_06_06_001",
  "source": "prepared_package",
  "working_title": "Example title",
  "language": "de",
  "topic_id": null,
  "series": null,
  "suggested_tiktok_caption": "Editable TikTok caption",
  "suggested_youtube_title": "Editable YouTube title",
  "suggested_youtube_description": "Editable YouTube description",
  "suggested_hashtags": ["#example"],
  "disclosure": {
    "synthetic_media": true,
    "commercial_content": false
  },
  "status": "ready_for_review"
}
```

Add importer logs, error messages, and dedupe by `package_id` plus checksum. Link package cards directly to review pages.

## Review page should be the strongest page

Frame uploads as a controlled approval process, not autoposting. Primary actions should be:

- Save metadata;
- Approve private upload;
- Upload as private;
- Create platform draft;
- Schedule;
- Reject / needs changes.

Include video preview, thumbnail/cover, working title, topic/series assignment, TikTok/YouTube metadata tabs, account selector, privacy/private-upload setting, schedule time, synthetic/commercial disclosure, status timeline, metadata version history, and audit log.

## Topic/ideas database is strategic

Build `/topics` as a real steering surface, not a placeholder. Include topics, ideas, links, keywords, notes, pillar/series, priority, status, actions (`Use next`, `Hold`, `Needs research`, `Archive`, `Add source link`, `Add idea`), and relationships from Topic → packages and Idea → Topic.

## Verification

- Backend tests/lint and frontend build.
- API smokes for dashboard summary, imports, videos, topics, ideas.
- Browser snapshots for dashboard, inbox, review, topics.
- Copy scan passes with no internal production names in UI/README/product docs.
- Use seed/demo data for stakeholder review; a clean empty dashboard is not enough.