Privacy standard
Customer names, faces, private messages, addresses, and personal context should be public only with explicit permission. Otherwise proof stories should be anonymized.
Proof library
Trust should be visible.
The proof engine turns real orders and workshops into permissioned stories: brief, concept, craft detail, finished work, and customer reaction.
Proof modules
Every proof story needs a job.
Raw photos are useful, but proof becomes persuasive only when it explains the customer context, the creative decision, and the final outcome.
Brief to giftThe customer problem and desired feeling
Process detailMaterial, personalization, or packaging decision
Finished workThe final presentation standard
ReactionWords from the buyer or participant with permission
Proof engine workflow
Collect raw collateral after each strong order, label it with the order context, record permission status, then promote only approved assets into the public site.
Where to add collaterals
Use a private raw library first, then publish selected proof.
Do not put every customer photo directly on the website. Keep raw proof organized privately, then copy only approved, edited, web-ready files into the public assets folder.
1. Raw order archive
Add original photos, screenshots, notes, and permission records under data/proof-engine/raw-orders/. This is the working archive for future proof stories.
2. Manifest
Track every proof candidate in data/proof-engine/proof_collateral_manifest.csv so another agent can filter by offer lane, occasion, permission, quality, and publish status.
3. Public web assets
Copy only approved, compressed, customer-safe images into website/assets/proof/. Those files can then be referenced from this page or future case-study pages.