# AutoShorts Dashboard generation-button readiness audit

Use this when the user asks whether the AutoShorts/TrueTraceShorts Dashboard can already generate the next Short from a button, or asks for proposals to simplify the video-creation/publication process.

## Core distinction

Do not collapse these into one vague “yes, automation exists” answer:

1. **Recommendation/queue button** — builds candidate topics and locks the next item.
2. **Concept button** — proposes hook/script/visual concept and approval command.
3. **Production approval button** — marks the concept as approved for generation.
4. **Generation/package button** — actually starts a render job, creates `storage/incoming/<package_id>/`, imports it, attaches it to the queue item, and moves it to review.
5. **Publish/website buttons** — private YouTube upload, TikTok manual export, and website companion after separate approval.

If only steps 1–3 exist, say clearly: the dashboard is concept/approval-ready but not yet a true one-button generation system.

## Readiness audit steps

1. Inspect the local repo/UI/API rather than answering from memory.
2. Confirm backend agent endpoints exist:
   - `GET /api/agent/production/next`
   - `POST /api/agent/production/{id}/concept-proposed`
   - `POST /api/agent/production/{id}/approve-generation`
   - `POST /api/agent/production/{id}/mark-started`
   - `POST /api/agent/production/{id}/attach-package`
   - `POST /api/agent/production/{id}/mark-ready-for-review`
3. Inspect the Production Queue UI for actual buttons and labels. Distinguish `Send to concept` / `APPROVE_PRODUCTION` from a real `Generate review package` action.
4. Query or inspect the active queue state and current locked item, but do not treat a locked item as production approval.
5. Verify with real build/test output where possible. For this repo, use the project environment (`uv run ...`) for backend tests and `npm run build` for frontend.
6. Report local-vs-remote state separately if relevant; do not imply local commits are deployed.

## Recommended product shape

Prefer a safe staged cockpit over a blind auto-publish button:

```text
Recommendations
→ Lock next
→ Generate concept/script proposal
→ Approve concept
→ Generate review package
→ Dashboard review
→ Private YouTube upload after explicit approval
→ TikTok manual export
→ Website companion after final approval
```

The missing/next implementation piece is usually a **Generate review package** job system:

- `ProductionGenerationJob` / `GenerationRequest` model or equivalent
- Dashboard button visible only after `concept_approved`
- backend route to queue generation, not upload or publish
- Hermes/JARVIS worker or script consumes job and renders package
- package written under `storage/incoming/<expected_package_id>/`
- importer scans and attaches package
- queue item moves to `in_review`
- failures remain visible in Dashboard status/logs

## Quality gates for the generation button

The generation button must not bypass the TrueTraceShorts quality standard:

- Director plan before render
- first-frame/visual-hook QA before import
- premium AI image/styleframe layer for final review videos
- no PowerPoint/template/mockup-looking main visuals
- no platform upload, TikTok API call, or website push as a side effect
- manifest includes package ID, queue item ID, script/hook, metadata, synthetic-media disclosure, and quality report references
- final review state requires video quality gates, not merely “MP4 file exists”

## How to answer the user

Use plain capability language:

- **Already works:** topic recommendations, lock-next, concept/script proposal, approval gate.
- **Not yet complete:** true button-triggered final video generation/package import, unless verified in code/UI.
- **Recommended next sprint:** one-button approved package generation, stopping at Dashboard review.

Avoid overpromising “one click creates and publishes the next Short.” For this channel, the right automation boundary is **one click to create a review package after concept approval**, with publishing and website sync still explicit separate approvals.