# PromptVault V16 — Verification Engine + Daily Vault Pipeline

## Status hierarchy
- Community: submitted by a user; no PromptVault verification claim.
- PV Reviewed: structurally reviewed for category-specific prompt quality; no claim that an output was produced.
- PV Verified: exact prompt/model version/settings are linked to a real approved output.

## Daily Vault gate
A prompt is eligible only when it has: PV score >=92, real attached output, exact provider/model version, category + genre metadata, verified-output status, and human approval. Reviewed-only prompts may appear as preview content in the local prototype but are never labeled verified.

## Taxonomy
Every production prompt should record Category → Subcategory → Genre → Use case → Provider → Exact model/version → Prompt type. Filters in V16 expose the key dimensions.

## Scoring
Production scoring must use category-specific rubrics. Video/image/business/text prompts must not share one generic rubric. Structural score and output verification remain separate.

## Provenance
Core prompts should be PromptVault-authored/refined or otherwise have explicit provenance. Do not republish scraped third-party prompts verbatim without permission/licensing.

## Backend
Run `backend/supabase/v16-verification-migration.sql` after the existing production foundation schema when ready. Review the SQL against the live schema before executing.
