Bring one artifact
Start with a Creation Engine packet, Activation Engine plan, Campaign Studio packet, generated kit, filled vault row, agent role, or approval task. Community begins from proof, not passive access.
OpenThe community should compound the self-serve products. Bring one artifact, ask one precise question, run the weekly proof loop, and install the agent habit that keeps future work approval-safe.
Onboarding contract
Artifact, question, proof, review
Bring one artifact
Activation plan
Choose the path
Learning path
Compose the decision
Creator Intelligence packet
Package the offer
Product Offer packet
Ask one precise question
Review request
Run the weekly proof loop
Proof loop
Open the operating room
Community OS
Install the agent habit
Skill pack
Artifact-first entry
Self-serve products create the artifact. Community creates cadence, taste, peer review, and the confidence to keep improving the system.
Start with a Creation Engine packet, Activation Engine plan, Campaign Studio packet, generated kit, filled vault row, agent role, or approval task. Community begins from proof, not passive access.
OpenUse the Learning Path Engine when the creator needs the education, skill, MCP, product, community, pricing, and Studio sequence before buying or asking for 1:1 help.
OpenUse the Creator Intelligence System when the creator asks what GenCreator should build, sell, install, practice, or escalate next.
OpenUse the Product Offer System when the creator needs a scalable digital product, offer ladder, launch assets, checkout truth, MCP handoff, and a clean support boundary before 1:1 help.
OpenName the decision you want reviewed: voice, offer, proof, campaign mechanism, tool mode, or support boundary.
OpenSource pulse, build block, review thread, Friday proof, digest. The rhythm turns isolated work into operating memory.
OpenUse Community OS to route the artifact through rooms, pricing, offers, launch moves, MCP resources, and the Studio boundary.
OpenUse the Skill Pack Library and Agent Pack so assistants read context, draft safely, and create approval records before public work.
OpenWeekly proof loop
The culture shaping part is not a slogan. It is a weekly operating rhythm where creators show artifacts, name decisions, review each other with taste, and save the best examples back into the library.
Review request
That is how community stays useful at scale. The ask is precise enough for peers, agents, and Studio reviewers to improve the work.
What did you make? Link the vault row, campaign packet, agent role, approval task, or proof note.
What should change before public use: voice, offer, proof, mechanism, tool mode, or support boundary?
What source, number, screenshot, customer quote, or previous artifact supports the decision?
Agent-assisted practice
Not private consulting by default. The assistant helps frame review requests, route artifacts, and keep support boundaries clear. Studio remains the capped human judgment layer.
Keep voice, offer, audience, proof, and policy memory clean before any campaign is drafted.
Turn outlier content, customer questions, and creator notes into a clear campaign mechanism.
Create platform-specific campaign packets that stay in draft until the creator approves them.
Convert risky actions into review records with source, risk, and human decision fields.