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.
OpenGenCreator.community onboarding
Enter with proof, not passive access.
The 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
1
Bring one artifact
Activation plan
2
Choose the path
Learning path
3
Compose the decision
Creator Intelligence packet
4
Package the offer
Product Offer packet
5
Ask one precise question
Review request
6
Run the weekly proof loop
Proof loop
7
Open the operating room
Community OS
8
Install the agent habit
Skill pack
Artifact-first entry
The first screen should make members more capable.
Self-serve products create the artifact. Community creates cadence, taste, peer review, and the confidence to keep improving the system.
Choose the path
Use 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.
OpenCompose the decision
Use the Creator Intelligence System when the creator asks what GenCreator should build, sell, install, practice, or escalate next.
OpenPackage the offer
Use 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.
OpenAsk one precise question
Name the decision you want reviewed: voice, offer, proof, campaign mechanism, tool mode, or support boundary.
OpenRun the weekly proof loop
Source pulse, build block, review thread, Friday proof, digest. The rhythm turns isolated work into operating memory.
OpenOpen the operating room
Use Community OS to route the artifact through rooms, pricing, offers, launch moves, MCP resources, and the Studio boundary.
OpenInstall the agent habit
Use the Skill Pack Library and Agent Pack so assistants read context, draft safely, and create approval records before public work.
OpenWeekly proof loop
A movement needs a repeatable rhythm.
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.
Beat 1Source pulse: state what you are building and what proof would change your mind.
Beat 2Build block: create one artifact from the vault, campaign, agent, or approval layer.
Beat 3Review thread: ask for one decision, not broad feedback.
Beat 4Friday proof: post the artifact, what changed, and the next constraint.
Beat 5Digest: record the best example back into the member artifact library.
Review request
Ask for one decision, not general feedback.
That is how community stays useful at scale. The ask is precise enough for peers, agents, and Studio reviewers to improve the work.
Artifact
What did you make? Link the vault row, campaign packet, agent role, approval task, or proof note.
Decision
What should change before public use: voice, offer, proof, mechanism, tool mode, or support boundary?
Evidence
What source, number, screenshot, customer quote, or previous artifact supports the decision?
Agent-assisted practice
The Community Concierge is the scalable support layer.
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.
Vault Librarian
Keep voice, offer, audience, proof, and policy memory clean before any campaign is drafted.
Signal Analyst
Turn outlier content, customer questions, and creator notes into a clear campaign mechanism.
Campaign Producer
Create platform-specific campaign packets that stay in draft until the creator approves them.
Approval Operator
Convert risky actions into review records with source, risk, and human decision fields.