live
GenCreator.community onboarding
Enter the community with one artifact, one question, and one weekly proof loop.
Open route
Fulfillment preview
GenCreator.community 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
planned
productGenCreator.community
providerwhop
eventcheckout_intent_gencreator_community
entitlementgencreator_community
email contract/api/products/fulfillment?product=gencreator-community
success route/products/checkout/success?product=gencreator-community
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
- Community OS packet
- Weekly proof loop
- Source pulse ritual
- Review thread entry
- Member artifact library
Delivery steps
01Confirm Whop membership event
02Gate Skool access
03Send fulfillment email from the product contract
04Ask for first artifact
05Generate the Community OS packet and proof loop
Before public checkout
- Confirm community product ID
- Wire Skool gating
- Point Whop success redirect to this success route
- Add paid member proof-loop template
- Add member artifact library persistence
Fulfillment contract
Welcome to GenCreator.community
Enter with one artifact, one review question, one Community OS packet, and one weekly proof loop.
Community practice, examples, and review rituals. Studio is the direct review layer.
Member Community OS template
Member proof loop template
Review request format
Source pulse calendar
Artifact library access