# GenCreator Creator Operating System Canonical: https://gencreator.ai/products/creator-os Version: 1.0.0 ## 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. ## First Read - GenCreator is a self-serve creator operating system. - Creator Intelligence composes the product path before the creator buys, joins community, or asks for direct help. - Product Offer System turns the product decision into a sellable ladder, delivery contract, launch assets, MCP plan, community bridge, and Studio boundary. - Creation comes before the pitch: one signal should become a packet before support is sold. - Activation turns the packet into a week of product, agent, approval, community, and Studio routing. - Learning Path chooses the modules, skills, MCP resources, product handoff, community bridge, and 1:1 boundary from the creator state. - The Community Proof Loop turns one artifact into a precise review ask before membership or 1:1 support. - Readiness still routes uncertainty: score the system when the next constraint is unclear. - The first product path is intelligence, offer system, create, activate, learn, diagnose when needed, package, install, operate, proof-loop, practice, orchestrate, review. - Agents draft; humans approve. ## Brand Behavior - Evidence before hype. - Drafts before writes. - Human approval before public action. - Community as practice, not passive access. - Agents as collaborators inside a governed operating model. - Gratitude, attribution, and proof are part of the product. ## Brand Assets - GenCreator vector mark: https://gencreator.ai/brand/gencreator-mark.svg Use: Primary loop mark for nav, product cards, app icon contexts, and small-size brand proof. - GenCreator one-color mark: https://gencreator.ai/brand/gencreator-mark-mono.svg Use: One-color master for favicon validation, document exports, monochrome UI, and high-contrast contexts. - GenCreator wordmark: https://gencreator.ai/brand/gencreator-wordmark.svg Use: Horizontal lockup for brand kits, partner docs, and premium product delivery surfaces. - GenCreator icon primitive sheet: https://gencreator.ai/brand/gencreator-icon-sheet.svg Use: Inspectable vector sheet for the creation, activation, MCP, community, approval, gratitude, Studio, and core mark primitives. - GenCreator social template sheet: https://gencreator.ai/brand/gencreator-social-template-sheet.svg Use: Inspectable vector sheet for carousel, vertical video, OG, newsletter, and wide product-proof crops. - Brand foundation page: https://gencreator.ai/brand Use: Public brand, product, MCP, community, and service-boundary system for humans. - Brand social system: https://gencreator.ai/brand/social Use: Public logo, type, social format, carousel, video, GTM, and assistant prompt system for production. - Brand foundation API: https://gencreator.ai/api/brand Use: Assistant-readable contract for brand assets, tokens, icon primitives, product ladder, MCP software layer, and service boundaries. - Creator OS API: https://gencreator.ai/api/products/creator-os Use: Public JSON contract for brand behavior, identity primitives, product layers, MCP resources, Eve, community, and roadmap. - Creator OS markdown: https://gencreator.ai/api/products/creator-os?format=markdown Use: Downloadable brand and product contract for assistants, collaborators, and future product packaging. ## Identity Primitives ### Mark 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. ### Color Deep architectural dark with architecture blue, trust blue, signal cyan, approval green, and ice highlights. Avoid warm yellow hero states and purple SaaS haze. ### Type Sentence case, calm labels, no default all-caps marketing. Dense data labels may use mono caps only when scan speed clearly matters. ### Material Liquid glass belongs on command decks, proof chips, media frames, and controls. Body copy sits on stable dark surfaces. ## Product Layers ### 1. Compose the product decision Mode: public Route: https://gencreator.ai/intelligence API: https://gencreator.ai/api/intelligence/system Buyer question: What should this creator build, sell, install, practice, or escalate next? First win: Generate a routed operating packet with product decision, composed engines, MCP plan, skill path, community route, pricing, offers, and approval policy. Product IDs: creator-intelligence-system, creation-engine, activation-engine, campaign-studio, skill-pack-library, community-os Evidence: - Creator Intelligence route - Creator Intelligence API - Markdown export - MCP resource contract Next action: Use Creator Intelligence System as the command surface when the creator asks how the whole business and product path should work. ### 2. Package the offer system Mode: public Route: https://gencreator.ai/products/offers API: https://gencreator.ai/api/products/offers Buyer question: How does this signal become a scalable product people can actually buy? First win: Generate an offer ladder, first ten-minute artifact, delivery contract, launch assets, MCP plan, community bridge, and Studio boundary. Product IDs: product-offer-system, creator-intelligence-system, self-serve-kit, creator-vault-kit, campaign-pack-system, agent-mcp-pack, gencreator-community, studio Evidence: - Product Offer System route - Product Offer API - Markdown export - MCP resource contract Next action: Use Product Offer System as the sales and packaging layer before paid checkout, community membership, or direct review. ### 3. Create the first packet Mode: public Route: https://gencreator.ai/create API: https://gencreator.ai/api/products/creation-engine Buyer question: Can one signal become a useful artifact before the buyer needs a call? First win: Generate a creation brief, draft artifacts, proof checks, assistant role plan, MCP plan, offer path, and community review question. Product IDs: creation-engine, campaign-studio Evidence: - Creation Engine route - Creation Engine API - Markdown export - MCP resource contract Next action: Use Creation Engine as the primary self-serve front door, then route into diagnostic, kit, pricing, community, or Studio. ### 4. Activate the operating path Mode: public Route: https://gencreator.ai/activate API: https://gencreator.ai/api/products/activation-plan Buyer question: What should the creator do for the next seven days after the packet exists? First win: Generate a seven-day plan with product path, MCP plan, assistant prompt, community handoff, education path, and Studio escalation rules. Product IDs: activation-engine, creation-engine, campaign-studio, self-serve-kit, skill-pack-library, gencreator-community, studio Evidence: - Activation Engine route - Activation plan API - Markdown export - MCP resource contract Next action: Use Activation Engine to turn the first packet into product behavior, community readiness, and direct-review boundaries. ### 5. Choose the learning path Mode: public Route: https://gencreator.ai/learn API: https://gencreator.ai/api/learn/path Buyer question: What should this creator learn, install, practice, buy, or escalate next? First win: Generate modules, skill-pack routing, MCP resources, product handoff, community bridge, and a clear 1:1 boundary. Product IDs: learning-path-engine, activation-engine, skill-pack-library, community-proof-loop, gencreator-community, studio Evidence: - Learning Path route - Learning Path API - Markdown export - MCP resource contract Next action: Use Learning Path Engine as the connective tissue between education, self-serve product, community, pricing, offers, MCP, and Studio routing. ### 6. Diagnose the creator system Mode: public Route: https://gencreator.ai/products/diagnostic API: https://gencreator.ai/api/products/diagnostic Buyer question: What is the current operating score and what should route first? First win: Get a readiness score, weakest layer, recommended product, product path, MCP resources, Eve prompt, and community handoff. Product IDs: creator-readiness-diagnostic, factory, self-serve-kit Evidence: - Creator Readiness Diagnostic - Readiness API - Creation Blueprint route - Factory skill export Next action: Run the readiness diagnostic when the creator is unsure which constraint should route first. ### 7. Package one operating kit Mode: self_serve Route: https://gencreator.ai/products/kit API: https://gencreator.ai/api/products/kit Buyer question: Can one artifact become a buyer-ready packet without private support? First win: Generate modules, prompts, MCP resources, checkout handoff, and a seven-day activation rhythm. Product IDs: self-serve-kit, campaign-studio, creator-vault-kit, campaign-pack-system Evidence: - Self-Serve Kit Composer - Markdown export - Product manifest Next action: Use the kit as the free self-serve entry before pitching community or Studio. ### 8. Install creator skills Mode: self_serve Route: https://gencreator.ai/products/skill-packs API: https://gencreator.ai/api/products/skill-packs Buyer question: What should the assistant know how to do safely? First win: Download one mode-safe skill file, read the right MCP resources, and run the starter prompt. Product IDs: skill-pack-library, agent-mcp-pack Evidence: - Skill Pack Library - Skill markdown exports - MCP resource contract Next action: Install one skill before adding more automation or paid bundle complexity. ### 9. Operate with agents and MCP Mode: paid Route: https://gencreator.ai/products/agent-pack API: https://gencreator.ai/api/products/agent-pack Buyer question: How do roles, tools, prompts, and approvals stay governed? First win: Install a role file, MCP config, approval policy, Eve role, and first dry approval task. Product IDs: agent-mcp-pack Evidence: - Agent Pack page - Agent Pack API - Install bundle API Next action: Keep public bundle inspectable, then gate paid updates behind checkout when products are live. ### 10. Practice inside community Mode: community Route: https://gencreator.ai/community/onboarding API: https://gencreator.ai/api/community/proof-loop Buyer question: Where does finished work get reviewed and sharpened? First win: Turn one artifact into a review request, weekly proof loop, community post draft, and next route before entering GenCreator.community. Product IDs: community-proof-loop, gencreator-community Evidence: - Community Proof Loop Engine - Proof Loop API - Community onboarding - Cohort structure Next action: Use the Proof Loop Engine as the community front door, then connect Whop membership and Skool access after the artifact-first flow is stable. ### 11. Orchestrate with Eve Mode: future Route: https://gencreator.ai/eve API: https://gencreator.ai/api/eve/brief Buyer question: What should the assistant ask, read, draft, approve, and hand off? First win: Generate proof questions, role stack, MCP plan, approval task, product path, and assistant prompt. Product IDs: agent-mcp-pack, gencreator-community, studio Evidence: - Eve Workbench - Eve brief API - Approval task model Next action: Make Eve persistent only after vaults, entitlements, installs, and community handoff persist per user. ### 12. Add human judgment Mode: studio Route: https://gencreator.ai/studio/apply Buyer question: When does the creator need direct review instead of more self-serve material? First win: Apply with an active artifact, campaign, offer, or agent workflow that already produced proof. Product IDs: studio Evidence: - Studio application route - Support boundary - Manual review scope Next action: Keep Studio capped and downstream from self-serve proof. ## Diagnostics - Creation Engine: https://gencreator.ai/create Best when: The creator has a signal and needs a usable artifact packet now. Output: Creation brief, draft artifacts, proof checks, agent plan, MCP plan, offer path, and community review. Handoff: Move into Self-Serve Kit, Campaign Pack, Agent Pack, pricing, offers, community, or Studio based on the packet. - Activation Engine: https://gencreator.ai/activate Best when: The creator has a packet and needs a self-serve operating path before community or Studio. Output: Seven-day activation plan, product path, MCP plan, community handoff, education path, and Studio escalation rules. Handoff: Move into Kit Composer, Skill Packs, Community onboarding, or Studio only when proof exists. - Learning Path Engine: https://gencreator.ai/learn Best when: The creator asks what to learn, install, practice, buy, or escalate next. Output: Learning modules, skill-pack path, MCP resources, product handoff, community bridge, and Studio boundary. Handoff: Move into Skill Packs, Proof Loop, Pricing, Offers, Community, or Studio based on artifact state and proof. - Community Proof Loop Engine: https://gencreator.ai/community/proof-loop Best when: The creator has an artifact but the review ask, proof signal, or support boundary is still broad. Output: Review request, weekly proof loop, community post draft, product path, assistant prompt, and MCP plan. Handoff: Move into Community onboarding, Pricing, Offers, or Studio based on proof and support intent. - Creator Readiness Diagnostic: https://gencreator.ai/products/diagnostic Best when: The creator asks what to build, install, buy, or practice first. Output: Operating score, weakest layer, recommended product, product path, MCP resources, Eve prompt, and community handoff. Handoff: Move into Blueprint, Kit Composer, Skill Packs, Community, or Studio gate based on the weakest layer. - Factory: https://gencreator.ai/factory Best when: The creator needs the right stack and first route. Output: Stack recommendation, vault configuration, reading path, and skill export. Handoff: Move into Blueprint or Self-Serve Kit after the stack is known. - Creation Blueprint: https://gencreator.ai/blueprint Best when: The creator has an idea but not an operating path. Output: First artifact, product path, agent stack, MCP resources, Eve brief, and community handoff. Handoff: Move into Kit Composer or Eve Workbench. - Creation Workspace: https://gencreator.ai/workspace Best when: The creator needs continuity across one artifact session. Output: Browser-local session connecting Blueprint, Eve, checkout handoff, MCP resources, and community review. Handoff: Persist to member profiles once auth and vault state are wired. ## Offers And Services - Free self-serve operating layer ($0): https://gencreator.ai/products Deliverable: Learning Path Engine, Creator Readiness Diagnostic, Factory, Blueprint, Kit Composer, Community Proof Loop Engine, Skill Pack Library, Eve brief, MCP resources, and markdown exports. Boundary: Public tools and exports only. No private implementation support or paid entitlement claims. Upgrade: Move to Creator Vault Kit, Campaign Pack System, Agent and MCP Pack, or community when a first artifact and proof question exist. - Paid digital products ($29-$149): https://gencreator.ai/products/delivery Deliverable: Vault kit, campaign pack, agent pack, examples, install files, prompt contracts, and fulfillment emails. Boundary: Self-serve instructions and updates. Custom implementation belongs in Studio. Upgrade: Community for practice, Studio for direct judgment. - GenCreator.community ($49/mo): https://gencreator.ai/community/onboarding Deliverable: Community Proof Loop Engine, weekly proof loop, review request format, Source Pulse, member examples, and artifact library. Boundary: Practice, examples, and review rituals. Not unlimited personal consulting. Upgrade: Studio after the creator has proof, pressure, and a review-worthy system. - Studio ($297/mo): https://gencreator.ai/studio/apply Deliverable: Private review, offer critique, campaign judgment, and agent workflow design. Boundary: Capped direct review for active creator businesses. Upgrade: Retreat, partner licensing, or deeper Starlight/Arcanea pathways only after proof. ## MCP Resources - gencreator-creator-operating-system: https://gencreator.ai/api/products/creator-os Use: Read the whole brand, product, service, community, Eve, and roadmap architecture. - gencreator-creator-intelligence-system: https://gencreator.ai/api/intelligence/system Use: Compose one signal into the product decision, MCP plan, skill path, campaign handoff, community route, pricing, offers, and approval policy. - gencreator-product-offer-system: https://gencreator.ai/api/products/offers Use: Turn the product decision into offer ladder, delivery contract, launch assets, MCP plan, community bridge, and support boundary. - gencreator-brand-social-system: https://gencreator.ai/api/brand/social Use: Read logo rules, type rules, social formats, carousel systems, motion systems, GTM plays, and assistant prompts. - gencreator-product-manifest: https://gencreator.ai/api/products/manifest Use: Confirm current product status, artifacts, checkout blockers, and support boundaries. - gencreator-creation-engine: https://gencreator.ai/api/products/creation-engine Use: Turn one signal into a creation brief, draft artifacts, proof checks, agent plan, MCP plan, offer path, and community review. - gencreator-activation-plan: https://gencreator.ai/api/products/activation-plan Use: Turn a creation packet into seven days of product, agent, approval, community, and Studio routing. - gencreator-learning-path: https://gencreator.ai/api/learn/path Use: Choose the modules, skill packs, MCP resources, product handoff, community bridge, and 1:1 boundary from creator state. - gencreator-community-proof-loop: https://gencreator.ai/api/community/proof-loop Use: Turn one artifact into a review request, weekly proof loop, community post draft, product path, and assistant prompt. - gencreator-creator-readiness-diagnostic: https://gencreator.ai/api/products/diagnostic Use: Score the creator operating system and route the next self-serve product, MCP resource, community step, or Studio gate. - gencreator-skill-pack-library: https://gencreator.ai/api/products/skill-packs Use: Install mode-safe creator workflows and lessons. - gencreator-agent-mcp-pack: https://gencreator.ai/api/products/agent-pack Use: Install roles, prompt contracts, MCP resources, and community handoff. ## Assistant Prompts ### Diagnose the product path Use: Use when a creator asks what to build or buy first. ```text Audit my creator operating system. Return the missing memory layer, signal source, campaign mechanism, approval risk, community question, and first GenCreator route to use. ``` ### Compose the intelligence system Use: Use when a creator asks what GenCreator should build, sell, install, practice, or escalate next. ```text Create my GenCreator Creator Intelligence System packet. Start from one signal, then return the product decision, composed engines, MCP resources, skill pack, campaign handoff, community route, pricing or offers path, approval policy, and 1:1 boundary. ``` ### Package a digital product Use: Use when turning expertise, prompts, media, or templates into a self-serve product. ```text Turn this expertise into a scalable GenCreator digital product. Name the promise, first win, deliverables, support boundary, checkout handoff, agent prompt, and community practice question. ``` ### Choose the learning path Use: Use when a creator asks what to learn, install, practice, buy, or escalate next. ```text Create my GenCreator learning path. Name the current stage, goal, artifact state, first module, skill pack, MCP resource, product handoff, community proof-loop question, and 1:1 boundary. ``` ### Add gratitude and proof Use: Use when the work risks sounding generic or extractive. ```text Name the sources, collaborators, customers, teachers, and proof this artifact should honor. Turn gratitude into credits, retention, product trust, and a better approval checklist. ``` ### Eve operating check Use: Use before treating Eve as an autonomous agent. ```text Before Eve operates, list the vault fields, tool modes, proof questions, approval records, entitlement checks, and community handoff needed. Do not allow external writes. ``` ## Community System The product gives creators a working operating model. The Proof Loop Engine creates the review packet. The community adds cadence, examples, review threads, and proof loops. Proof rule: Community begins from an artifact, proof metric, and decision question. - Source pulse: state what you are building and what proof would change your mind. - Build block: create one artifact from the vault, campaign, agent, or approval layer. - Review thread: ask for one decision, not broad feedback. - Friday proof: post the artifact, what changed, and the next constraint. - Digest: record the best example back into the member artifact library. ## Eve System Current role: A deterministic workbench that creates proof questions, role stack, MCP plan, approval task, product path, assistant prompt, and community handoff. Future role: A persistent operator that reads the creator vault, asks for missing proof, drafts safely, creates approval records, and routes work into practice. Safety boundary: Eve does not publish, message, charge, delete, or change external systems without a human-approved downstream action. ## Service Boundary - Self-serve: Public tools, markdown exports, APIs, starter packets, product updates, and clear setup instructions. - Community: Artifact-first practice, examples, proof loops, review prompts, and member cadence. - Studio: Capped direct judgment for creators whose self-serve system is already producing work. ## Roadmap - Persist member vaults Now: Workspace and kit sessions are browser-local or API-generated. Next: Save vault rows, kit outputs, skill installs, and approval records per member. Proof needed: Authenticated member profile with server-side access checks and no client-side secret exposure. - Gate paid bundles cleanly Now: Paid products have readiness contracts, resolver paths, fulfillment previews, and public starter artifacts. Next: Create Whop products, set checkout URLs, wire success redirects, and gate paid bundle updates. Proof needed: Successful purchase event creates entitlement, delivery, and access to the right gated assets. - Connect community practice Now: Community onboarding and the Proof Loop Engine generate artifact-first review packets and weekly proof loops. Next: Post review requests and proof-loop outputs into the gated member space after purchase. Proof needed: Member joins with artifact, review question, proof metric, support boundary, and routed thread. - Turn Eve into a persistent operator Now: Eve is a deterministic workbench and role brief. Next: Give Eve member memory, entitlements, skill installs, tool modes, and approval queue state. Proof needed: Eve can read context, ask proof questions, draft locally, and create approval records without external writes.