A complete self-serve creator operating system: diagnose, package, install, operate, practice, orchestrate, and add human judgment only when proof exists.
Operating sequence
From diagnosis to judgment
Mission
Help AI-native creators build systems that raise the quality of what they make.
Vision
A generative culture where creators use agents with taste, evidence, memory, attribution, and human approval.
Positioning
The creator intelligence OS: not a course, scheduler, prompt dump, or agency retainer.
Promise
One creator can operate with the discipline of an AI Center of Excellence without losing their own voice.
Brand foundation
GenCreator needs a brand system that behaves like software: accessible SVG marks, stable colors, sentence-case typography, clear support boundaries, and artifacts people can inspect.
A vector generator loop with center rail and approval arrow. It must work as favicon, app icon, nav mark, one-color master, and full-color lockup.
Deep architectural dark with architecture blue, trust blue, signal cyan, approval green, and ice highlights. Avoid warm yellow hero states and purple SaaS haze.
Sentence case, calm labels, no default all-caps marketing. Dense data labels may use mono caps only when scan speed clearly matters.
Liquid glass belongs on command decks, proof chips, media frames, and controls. Body copy sits on stable dark surfaces.
GenCreator vector mark
Primary loop mark for nav, product cards, app icon contexts, and small-size brand proof.
Open asset
GenCreator one-color mark
One-color master for favicon validation, document exports, monochrome UI, and high-contrast contexts.
Open asset
GenCreator wordmark
Horizontal lockup for brand kits, partner docs, and premium product delivery surfaces.
Open asset
GenCreator icon primitive sheet
Inspectable vector sheet for the creation, activation, MCP, community, approval, gratitude, Studio, and core mark primitives.
Open asset
GenCreator social template sheet
Inspectable vector sheet for carousel, vertical video, OG, newsletter, and wide product-proof crops.
Open asset
Brand foundation page
Public brand, product, MCP, community, and service-boundary system for humans.
Open asset
Brand social system
Public logo, type, social format, carousel, video, GTM, and assistant prompt system for production.
Open asset
Brand foundation API
Assistant-readable contract for brand assets, tokens, icon primitives, product ladder, MCP software layer, and service boundaries.
Open asset
Creator OS API
Public JSON contract for brand behavior, identity primitives, product layers, MCP resources, Eve, community, and roadmap.
Open asset
Creator OS markdown
Downloadable brand and product contract for assistants, collaborators, and future product packaging.
Open asset
Product architecture
Every layer answers a buyer question, creates a first win, names the evidence, and points to the next action. This is the product spine for digital products, education, community, and Studio.
public
What should this creator build, sell, install, practice, or escalate next?
Generate a routed operating packet with product decision, composed engines, MCP plan, skill path, community route, pricing, offers, and approval policy.
Use Creator Intelligence System as the command surface when the creator asks how the whole business and product path should work.
public
How does this signal become a scalable product people can actually buy?
Generate an offer ladder, first ten-minute artifact, delivery contract, launch assets, MCP plan, community bridge, and Studio boundary.
Use Product Offer System as the sales and packaging layer before paid checkout, community membership, or direct review.
public
Can one signal become a useful artifact before the buyer needs a call?
Generate a creation brief, draft artifacts, proof checks, assistant role plan, MCP plan, offer path, and community review question.
Use Creation Engine as the primary self-serve front door, then route into diagnostic, kit, pricing, community, or Studio.
public
What should the creator do for the next seven days after the packet exists?
Generate a seven-day plan with product path, MCP plan, assistant prompt, community handoff, education path, and Studio escalation rules.
Use Activation Engine to turn the first packet into product behavior, community readiness, and direct-review boundaries.
public
What should this creator learn, install, practice, buy, or escalate next?
Generate modules, skill-pack routing, MCP resources, product handoff, community bridge, and a clear 1:1 boundary.
Use Learning Path Engine as the connective tissue between education, self-serve product, community, pricing, offers, MCP, and Studio routing.
public
What is the current operating score and what should route first?
Get a readiness score, weakest layer, recommended product, product path, MCP resources, Eve prompt, and community handoff.
Run the readiness diagnostic when the creator is unsure which constraint should route first.
self_serve
Can one artifact become a buyer-ready packet without private support?
Generate modules, prompts, MCP resources, checkout handoff, and a seven-day activation rhythm.
Use the kit as the free self-serve entry before pitching community or Studio.
self_serve
What should the assistant know how to do safely?
Download one mode-safe skill file, read the right MCP resources, and run the starter prompt.
Install one skill before adding more automation or paid bundle complexity.
paid
How do roles, tools, prompts, and approvals stay governed?
Install a role file, MCP config, approval policy, Eve role, and first dry approval task.
Keep public bundle inspectable, then gate paid updates behind checkout when products are live.
community
Where does finished work get reviewed and sharpened?
Turn one artifact into a review request, weekly proof loop, community post draft, and next route before entering GenCreator.community.
Use the Proof Loop Engine as the community front door, then connect Whop membership and Skool access after the artifact-first flow is stable.
future
What should the assistant ask, read, draft, approve, and hand off?
Generate proof questions, role stack, MCP plan, approval task, product path, and assistant prompt.
Make Eve persistent only after vaults, entitlements, installs, and community handoff persist per user.
studio
When does the creator need direct review instead of more self-serve material?
Apply with an active artifact, campaign, offer, or agent workflow that already produced proof.
Keep Studio capped and downstream from self-serve proof.
Diagnostics and offers
The answer is not always a heavier product. Sometimes the buyer needs Factory, sometimes Blueprint, sometimes a kit, and sometimes direct review.
The creator has a signal and needs a usable artifact packet now.
Creation brief, draft artifacts, proof checks, agent plan, MCP plan, offer path, and community review.
The creator has a packet and needs a self-serve operating path before community or Studio.
Seven-day activation plan, product path, MCP plan, community handoff, education path, and Studio escalation rules.
The creator asks what to learn, install, practice, buy, or escalate next.
Learning modules, skill-pack path, MCP resources, product handoff, community bridge, and Studio boundary.
The creator has an artifact but the review ask, proof signal, or support boundary is still broad.
Review request, weekly proof loop, community post draft, product path, assistant prompt, and MCP plan.
The creator asks what to build, install, buy, or practice first.
Operating score, weakest layer, recommended product, product path, MCP resources, Eve prompt, and community handoff.
The creator needs the right stack and first route.
Stack recommendation, vault configuration, reading path, and skill export.
The creator has an idea but not an operating path.
First artifact, product path, agent stack, MCP resources, Eve brief, and community handoff.
The creator needs continuity across one artifact session.
Browser-local session connecting Blueprint, Eve, checkout handoff, MCP resources, and community review.
Learning Path Engine, Creator Readiness Diagnostic, Factory, Blueprint, Kit Composer, Community Proof Loop Engine, Skill Pack Library, Eve brief, MCP resources, and markdown exports.
Public tools and exports only. No private implementation support or paid entitlement claims.
InspectVault kit, campaign pack, agent pack, examples, install files, prompt contracts, and fulfillment emails.
Self-serve instructions and updates. Custom implementation belongs in Studio.
InspectCommunity Proof Loop Engine, weekly proof loop, review request format, Source Pulse, member examples, and artifact library.
Practice, examples, and review rituals. Not unlimited personal consulting.
InspectPrivate review, offer critique, campaign judgment, and agent workflow design.
Capped direct review for active creator businesses.
InspectMCP, prompts, and Eve
The API exposes the operating system as resources and prompt contracts. Eve stays bounded until persistence, entitlements, installs, and approval state are real.
Eve does not publish, message, charge, delete, or change external systems without a human-approved downstream action.
A persistent operator that reads the creator vault, asks for missing proof, drafts safely, creates approval records, and routes work into practice.
gencreator-creator-operating-system
Read the whole brand, product, service, community, Eve, and roadmap architecture.
gencreator-creator-intelligence-system
Compose one signal into the product decision, MCP plan, skill path, campaign handoff, community route, pricing, offers, and approval policy.
gencreator-product-offer-system
Turn the product decision into offer ladder, delivery contract, launch assets, MCP plan, community bridge, and support boundary.
gencreator-brand-social-system
Read logo rules, type rules, social formats, carousel systems, motion systems, GTM plays, and assistant prompts.
gencreator-product-manifest
Confirm current product status, artifacts, checkout blockers, and support boundaries.
gencreator-creation-engine
Turn one signal into a creation brief, draft artifacts, proof checks, agent plan, MCP plan, offer path, and community review.
gencreator-activation-plan
Turn a creation packet into seven days of product, agent, approval, community, and Studio routing.
gencreator-learning-path
Choose the modules, skill packs, MCP resources, product handoff, community bridge, and 1:1 boundary from creator state.
gencreator-community-proof-loop
Turn one artifact into a review request, weekly proof loop, community post draft, product path, and assistant prompt.
gencreator-creator-readiness-diagnostic
Score the creator operating system and route the next self-serve product, MCP resource, community step, or Studio gate.
gencreator-skill-pack-library
Install mode-safe creator workflows and lessons.
gencreator-agent-mcp-pack
Install roles, prompt contracts, MCP resources, and community handoff.
Community and roadmap
GenCreator.community becomes powerful when people bring proof, ask sharper questions, and return the best examples to the system.
Workspace and kit sessions are browser-local or API-generated.
Save vault rows, kit outputs, skill installs, and approval records per member.
Paid products have readiness contracts, resolver paths, fulfillment previews, and public starter artifacts.
Create Whop products, set checkout URLs, wire success redirects, and gate paid bundle updates.
Community onboarding and the Proof Loop Engine generate artifact-first review packets and weekly proof loops.
Post review requests and proof-loop outputs into the gated member space after purchase.
Eve is a deterministic workbench and role brief.
Give Eve member memory, entitlements, skill installs, tool modes, and approval queue state.
