Receipts

What a receipt proves

• The opportunity identifier
• The approved package relationship
• The receipt version and creation time
• The public visibility state
• The sanitized summary published at that route

What it does not prove

• Guaranteed virality or revenue
• Ownership of third-party material
• Permission to reuse every source
• The complete private score or source set
• That an old source remains online

Public fields

Public receipts may include the opportunity ID, title, timing state, platform and language fit, score band, why-now summary, package counts, safe source note, risk note, and limitations.

Private fields

Exact sources, detailed scores, customer identity, full package content, provider metadata, operator notes, and workflow events remain within authorized package and operator boundaries.

Corrections

Published receipts are not silently overwritten. A corrected record supersedes the earlier receipt while preserving the prior version.