sample
Creator Vault Kit starter
Create the first memory layer: voice, offer, audience, proof, and approval policy.
Open markdown
Fulfillment preview
Creator Vault Kit delivery should start with a usable artifact.
This route is the future checkout success target. Today it previews the delivery experience and keeps paid access honest until the provider product, success redirect, and paid bundle are wired.
Receipt state
preview until provider is wired
productCreator Vault Kit
providerwhop
eventcheckout_intent_creator_vault_kit
entitlementcreator_vault_kit
email contract/api/products/fulfillment?product=creator-vault-kit
success route/products/checkout/success?product=creator-vault-kit
Buyer receipt
The first screen after payment should reduce doubt.
A buyer should immediately see what they bought, what opened, what arrives by email, and where the next practice layer begins.
You receive
- Vault schema
- Voice rule worksheet
- Offer map
- Proof table
- Approval policy
Delivery steps
01Confirm Whop payment event
02Send fulfillment email from the product contract
03Open starter packet
04Invite upgrade path into community review
Before public checkout
- Create Whop product
- Set checkout URL env var
- Point Whop success redirect to this success route
- Add paid template bundle
Fulfillment contract
Your Creator Vault Kit is open
Create the voice, offer, audience, proof, and approval memory layer before any assistant drafts.
Self-serve setup, product updates, and community review path. No private implementation support.
Full Notion-ready vault tables
Voice rule examples
Offer map examples
Approval policy expansion
Artifacts
The preview opens the starter now. Paid checkout can later open the full bundle.
This keeps the public promise clean: samples are accessible, paid assets are named as future fulfillment work, and community or Studio is an upgrade path after proof.