# PromptVault V7 — Stabilization backend contract

V7 deliberately separates **reviewed prompt text** from **verified generated output**.

## Production services
- Supabase/Postgres: accounts, profiles, prompts, model variants, scores, likes, saves, worked-for-me, ratings, threaded comments and moderation.
- Cloudflare R2/Stream (or equivalent): approved image/video result delivery.
- Cloudflare Worker/Cron: publishes Daily Vault only from `verified_outputs.quality_status = 'approved'`.

## Verification states
1. `draft` — not public.
2. `reviewed` — structure/model fit analyzed; no claim that it produced the shown result.
3. `tested` — generation exists but has not passed editorial review.
4. `verified` — exact prompt/model/settings are tied to an approved output.

Only state 4 may show **PV VERIFIED OUTPUT**.

## Prototype persistence
The front end stores likes, saves, Worked for Me, ratings, comments, helpful votes and replies in localStorage so interactions survive reloads during development. These are intentionally user-local demo interactions and contain no fake public totals.

## Scaling rule
A core prompt is one unique creative concept. Model variants are children of that core prompt and do not increase the advertised core-prompt count. Production import should be batched, deduplicated and versioned rather than embedding 100,000 rows into the HTML bundle.
