Digital product
A vault, campaign packet, delivery room, install bundle, or practice loop the buyer can use in one sitting.
Open layerCreation blueprint
GenCreator Blueprint for the system you should build next.
Answer five product questions. Get the next artifact, product path, agent stack, MCP resources, Eve brief, and community handoff. It is the bridge from creator ambition to a self-serve operating system.
Blueprint console
Choose the creation system.
Who is building?
What should it produce?
How mature is the system?
What is blocking momentum?
What support mode fits now?
Founder operator blueprint for social content
One approved campaign packet with three hooks, two platform drafts, one reply bank, and one approval record.
Measure: how many assistant actions create review records before external work
Product path
Agent stack
Vault Librarian
Keep voice, offer, audience, proof, and policy memory clean before any campaign is drafted.
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.
Eve Operator
Coordinate memory, signal, campaign, approval, and community handoff as one operating role.
Eve brief
You are Eve for GenCreator. Read the creator vault, product manifest, and this Creation Blueprint. The creator is a founder operator building social content. The main bottleneck is automation. Your first objective: help produce One approved campaign packet with three hooks, two platform drafts, one reply bank, and one approval record. Measure progress by how many assistant actions create review records before external work. Before drafting, ask for missing proof. Use read_only for inspection, draft_only for local drafts, and approval_required for public, customer-facing, paid, destructive, or reputation-sensitive work. Return the next product step, the assistant role to install, and one approval record.
First week plan
Day 1
Map the memory layer
Voice, offer, audience, proof, and approval fields filled for the next artifact.
Day 2
Select one signal
A source note, hook mechanism, and missing-proof question.
Day 3
Build the first artifact
One approved campaign packet with three hooks, two platform drafts, one reply bank, and one approval record.
Day 4
Install the assistant role
One role file installed with read-only MCP config and a dry approval task.
Day 5
Decide the upgrade path
A clear next product: kit, campaign pack, agent pack, community, or Studio.
Why this exists
The right first product depends on the operating bottleneck.
Some creators need memory. Some need campaigns. Some need an assistant with rules. Some need community cadence. The blueprint makes that choice explicit and turns it into a first-week plan.
Agent stack
Role files, MCP config, Eve operating brief, and approval policy so assistants work inside clear boundaries.
Open layerCreation engine
Signals become briefs, briefs become campaigns, campaigns become reviewed output and product evidence.
Open layerCommunity practice
Finished artifacts enter weekly proof loops, precise review requests, member examples, and shared taste.
Open layerBusiness shape
Self-serve first. Community second. Studio only after proof.
This keeps GenCreator scalable and honest. The digital product creates an artifact. The community improves the artifact through practice. Studio adds direct judgment for creators whose system is already moving.
FreeBlueprint and Factory identify the first useful artifact.
Kits and packsTemplates, role files, MCP config, and approval workflows. Pricing is published when checkout is live.
CommunityGenCreator.community turns artifacts into weekly proof and review.
StudioReviews active systems, offers, campaigns, and agent workflows. By application.