ready
Creator OS Contract
Read the full operating architecture before choosing a diagnostic, skill, agent role, community handoff, or Studio path.
The Creator OS route and API publish brand, product, MCP, Eve, community, and roadmap contracts.
This is the install surface for GenCreator roles, MCP resources, prompt contracts, tool modes, approval rules, and the community handoff. It turns the product suite into something an assistant can actually run.
Protocol shape
Tools, resources, prompts, approval
Tools
Creator profile, outlier content, hook decoder, campaign pack, schedule draft, approval record
Resources
Product manifest, checkout contract, skill library, agent pack, install bundle, starter artifacts
Prompts
Approval task, role install, community review request
Policy
No external writes, no public action without approval, no secrets in prompts
Install targets
The pack is designed to travel: Claude Code skill, JSON contract, MCP gateway, and Eve as the future operating role once the substrate is stable.
Read the full operating architecture before choosing a diagnostic, skill, agent role, community handoff, or Studio path.
The Creator OS route and API publish brand, product, MCP, Eve, community, and roadmap contracts.
Use the logo, type, social format, carousel, video, GTM, and assistant prompt contract before creating public brand assets.
The Brand Social route and API publish platform formats, motion systems, vector template sheet, and MCP hooks.
Compose one creator signal into a product decision, MCP plan, skill path, campaign handoff, community route, offers, pricing, and approval policy.
The Intelligence route and API publish the connected self-serve operating packet for humans and assistants.
Turn the intelligence packet into a buyer-ready offer ladder, delivery contract, launch assets, checkout truth, MCP plan, community route, and Studio boundary.
The Product Offer route and API publish the scalable digital product, sales, GTM, and support-boundary packet.
Turn one source signal into a creation packet with draft artifacts, proof checks, MCP resources, assistant prompt, and offer path.
The Creation Engine route and API publish the market-facing self-serve creation packet.
Turn a creation packet into a seven-day plan, product path, MCP plan, assistant prompt, community handoff, and Studio escalation rules.
The Activation Engine route and API publish the self-serve activation path that bridges product, community, and direct review.
Generate the self-serve education, product, skill, MCP, community, pricing, offers, and Studio sequence from one creator state.
The Learning Path route and API publish modules, skill-pack routing, MCP resources, product handoff, and 1:1 boundaries.
Turn one artifact into a review request, weekly proof loop, product path, stage handoff, assistant prompt, and MCP plan.
The proof-loop route and API publish the community review packet before the membership gate.
Compose one artifact into the operating room with rooms, weekly cadence, offer bridge, launch moves, MCP plan, and Studio boundary.
The Community OS route and API publish the self-serve operating state before paid membership.
Score the operating system before choosing a self-serve product, assistant role, community practice, or Studio gate.
The diagnostic route and API publish score dimensions, product path, MCP resources, Eve prompt, and support boundary.
Choose one mode-safe creator skill, download the skill file, read MCP resources, and produce the first proof artifact.
Skill Pack route and API publish installable skill files, lessons, prompts, and resource contracts.
Generate one buyer-ready operating packet with modules, MCP resources, checkout handoff, approval prompt, and activation rhythm.
Kit route and API now publish JSON and markdown from the same product engine.
Save one artifact session that connects Blueprint, Eve, checkout handoff, MCP resources, and community review.
Workspace route and API now publish the composed operating packet.
Read one vault state with memory, proof, product handoff, approval backlog, and community review before drafting.
Vault route and API now publish the self-serve memory layer and MCP-readable operating state.
Download the bundle, install one role, add the read-only MCP config, and create the first approval task.
Bundle API now publishes role files, MCP config, Eve role, approval policy, and checklist.
Drop the role file into a project and ask it to create the first approval task.
Factory already exports personalised Claude Code skills.
List tools, resources, and prompts before an assistant drafts anything public.
Public JSON-RPC endpoint exposes GenCreator tools and policy.
Inspect the JSON manifest and wire roles into your preferred assistant.
Agent pack API publishes roles, resources, prompts, and support boundaries.
Eve reads the vault, asks for proof, drafts campaigns, and opens approval queues.
Eve stays a role until vault, MCP, checkout, and community loops are stable.
Generate one operating brief with proof questions, role stack, MCP plan, approval task, and community handoff.
The Eve brief engine and API are deterministic, downloadable, and MCP-readable.
Install bundle
The bundle separates role files, MCP config, approval policy, Eve, and setup order. That makes the product installable in Claude Code, MCP-aware assistants, and future member workbenches without blurring safety modes.
Ask the assistant to inspect voice, offer, audience, proof, and approval fields before drafting.
Turn one outlier, customer question, or creator note into a campaign mechanism.
Create platform drafts that stay local until the creator approves them.
Convert any public, customer-facing, or risky action into a review record.
Turn finished artifacts into precise review requests for the weekly proof loop.
Add the GenCreator MCP endpoint as read-only before granting draft or approval modes.
Define which assistant actions can inspect, draft, or require human approval.
Use Eve as the operating role that reads context, asks for proof, drafts safely, and creates approval records.
Install one role, connect the MCP config, run a dry approval task, and route one artifact into review.
Agent roles
Each role has a job, mode, source list, and first prompt. That keeps assistants useful without letting them impersonate judgment or publish without review.
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.
Route finished artifacts into the weekly proof loop, review threads, and source pulse ritual.
Eve direction
The future agent is not a character pasted onto the site. Eve is the operating loop: read memory, ask for proof, call tools safely, prepare approvals, and move finished work into practice.
Community handoff
The agent pack creates drafts and approval tasks. GenCreator.community turns finished artifacts into weekly proof, review, and better operating taste.
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.
Open stepUse 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.
Open stepUse the Creator Intelligence System when the creator asks what GenCreator should build, sell, install, practice, or escalate next.
Open stepUse 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.
Open stepName the decision you want reviewed: voice, offer, proof, campaign mechanism, tool mode, or support boundary.
Open stepSource pulse, build block, review thread, Friday proof, digest. The rhythm turns isolated work into operating memory.
Open stepUse Community OS to route the artifact through rooms, pricing, offers, launch moves, MCP resources, and the Studio boundary.
Open stepUse the Skill Pack Library and Agent Pack so assistants read context, draft safely, and create approval records before public work.
Open step