# GenCreator Learning Path

Path: learn_4bdf5555
Canonical: https://gencreator.ai/learn

Architect path for scalable product: turn the current draft packet state into a self-serve operating path before increasing service dependency.

## First Win

In seven days, move from artifact to product packet, assistant habit, proof loop, and the right offer or community handoff.

## Stage Frame

- Stage: Architect
- Signal: The creator can now map product, tools, memory, and community as one system.
- Risk: The product can feel powerful but still be hard to buy if the first win is not concrete.
- Next move: Package the self-serve kit and one assistant habit.

## Transformation Frame

The scalable product path is diagnose, create, package, install, practice, and then add human judgment only when proof makes the review valuable.

## Modules

### Day 1: Name the operating thesis

Route: https://gencreator.ai/products/creator-os
Product: Creator OS Contract
Job: Translate the goal into one operating thesis, one buyer promise, and one proof standard.
Exercise: Write the sentence a buyer, member, or assistant should be able to repeat.
Output: Scalable product thesis with promise, proof, and support boundary.
Proof: The sentence names the creator, the first win, and the evidence needed.
MCP resource: gencreator-creator-operating-system
Skill pack: creator-vault-librarian
Community practice: Share the thesis only after it points to an artifact someone can inspect.
Support boundary: Strategy stays self-serve until a real artifact exposes a decision that needs review.

### Day 2: Make the artifact product-ready

Route: https://gencreator.ai/products/kit
Product: Self-Serve Kit Composer
Job: Strengthen the artifact so it can become a self-serve product module.
Exercise: Create or refine the smallest artifact that proves the path is not just an idea.
Output: Product-ready packet with first win, deliverables, and proof check.
Proof: One source, example, screenshot, buyer question, or usage note is attached.
MCP resource: gencreator-self-serve-kit
Skill pack: creator-vault-librarian
Community practice: Ask whether the artifact is specific enough for a member to test or critique.
Support boundary: No paid promise should depend on private explanation that is missing from the artifact.

### Day 3: Package the self-serve deliverable

Route: https://gencreator.ai/products/kit
Product: Self-Serve Kit Composer
Job: Turn the artifact into modules, prompts, MCP resources, checkout handoff, and activation rhythm.
Exercise: Define the first sitting, the reusable files, and the point where human approval is required.
Output: Buyer-ready kit with first win, modules, assistant prompt, and product handoff.
Proof: The first sitting can be completed without a private call.
MCP resource: gencreator-self-serve-kit
Skill pack: campaign-pack-producer
Community practice: Bring the kit promise and ask which support boundary is still vague.
Support boundary: Self-serve products include instructions and updates, not unlimited implementation.

### Day 4: Install one governed assistant habit

Route: https://gencreator.ai/products/skill-packs
Product: Skill Pack Library
Job: Select one skill pack, one MCP resource, one starter prompt, and one approval boundary.
Exercise: Run the starter prompt against the artifact and keep all public actions behind review.
Output: Campaign Pack Producer installed with a first task and risk note.
Proof: The assistant knows whether it can inspect, draft, or request approval.
MCP resource: gencreator-self-serve-kit
Skill pack: campaign-pack-producer
Community practice: Ask if the selected mode matches the artifact risk.
Support boundary: Agents draft and prepare records; humans approve external action.

### Day 5: Prepare the community proof loop

Route: https://gencreator.ai/community/proof-loop
Product: Community Proof Loop Engine
Job: Turn the artifact into one precise review request and a weekly proof rhythm.
Exercise: Write the review request with artifact, proof available, what changed, and one decision.
Output: Community-ready review packet with weekly proof loop.
Proof: The request asks for one decision, not broad feedback.
MCP resource: gencreator-community-proof-loop
Skill pack: approval-flow-operator
Community practice: What is the smallest change that makes this self-serve product more useful in the first sitting?
Support boundary: Community provides practice and examples, not unlimited private consulting.

### Day 6: Choose the commercial route

Route: https://gencreator.ai/offers
Product: GenCreator.community
Job: Decide whether the next move is pricing, offers, community, or Studio based on proof.
Exercise: Write the buyer action, the fulfillment promise, and the escalation condition.
Output: Offer handoff with buyer action and review boundary.
Proof: The route is justified by artifact state, proof level, and support mode.
MCP resource: gencreator-product-manifest
Skill pack: approval-flow-operator
Community practice: Ask which route is earned by proof rather than ambition.
Support boundary: 1:1 help begins after a clear artifact, proof signal, and review question exist.

## Recommended Skill Packs

- Creator Vault Librarian (read_only): https://gencreator.ai/products/delivery#creator-vault-kit
  First win: Fill one memory row and return the missing proof questions before a campaign is drafted.
  Lesson: Teach the creator why assistants need voice, offer, proof, and policy before drafting.
- Campaign Pack Producer (draft_only): https://gencreator.ai/campaigns
  First win: Create one campaign packet with the same mechanism across LinkedIn, X, newsletter, and short script.
  Lesson: Teach the creator to preserve the same idea across platforms instead of making disconnected posts.
- Approval Flow Operator (approval_required): https://gencreator.ai/approvals
  First win: Create one approval record with action, sources, risk, human decision, and next handoff.
  Lesson: Teach the creator when an assistant must stop and ask for a decision.

## Product Handoff

- Learning Path Engine: https://gencreator.ai/learn
  Buy or inspect: https://gencreator.ai/learn
  Contract: https://gencreator.ai/products/checkout?product=learning-path-engine
  Stage: free
  Reason: The path chooses education, product, MCP, community, and Studio sequence before the buyer gets lost.
- Self-Serve Kit Composer: https://gencreator.ai/products/kit
  Buy or inspect: https://gencreator.ai/products/kit
  Contract: https://gencreator.ai/products/checkout?product=self-serve-kit
  Stage: free
  Reason: The artifact needs modules, assistant prompt, MCP resources, and buyer handoff.
- Skill Pack Library: https://gencreator.ai/products/skill-packs
  Buy or inspect: https://gencreator.ai/products/skill-packs
  Contract: https://gencreator.ai/products/checkout?product=skill-pack-library
  Stage: free
  Reason: The assistant needs a governed workflow before automation expands.
- Community Proof Loop Engine: https://gencreator.ai/community/proof-loop
  Buy or inspect: https://gencreator.ai/community/proof-loop
  Contract: https://gencreator.ai/products/checkout?product=community-proof-loop
  Stage: community
  Reason: The artifact should become a precise review request before membership or private support.
- GenCreator.community: https://gencreator.ai/community/os
  Buy or inspect: https://gencreator.ai/products/buy?product=gencreator-community
  Contract: https://gencreator.ai/products/checkout?product=gencreator-community
  Stage: community
  Reason: The work is ready for weekly proof loops, examples, and member cadence.

## MCP Plan

Resources:
- gencreator-learning-path: https://gencreator.ai/api/learn/path
  Use: Read the self-serve education, product, MCP, community, and Studio routing plan.
- gencreator-activation-plan: https://gencreator.ai/api/products/activation-plan
  Use: Read the seven-day operating plan that anchors this learning path.
- gencreator-skill-pack-library: https://gencreator.ai/api/products/skill-packs
  Use: Install the skill packs selected by the path.
- gencreator-product-manifest: https://gencreator.ai/api/products/manifest
  Use: Confirm current product status, checkout readiness, fulfillment, and support boundaries.

Tools:
- gencreator.generate_learning_path: Generate a self-serve learning path from stage, goal, artifact state, support preference, and time budget.
- gencreator.generate_activation_plan: Generate the operating week after the path chooses the constraint.
- gencreator.generate_community_proof_loop: Turn the first artifact into a review request before community entry.

Prompts:
- gencreator.learning_path_review: Critique the path for product clarity, skill-pack fit, MCP completeness, community readiness, and Studio boundary.
- gencreator.install_agent_pack: Install the next mode-safe skill after the learning path chooses it.

## Community Bridge

Route: https://gencreator.ai/community/proof-loop

Artifact rule: Bring one artifact, what changed, what proof exists, and one decision for review.

Review question: What is the smallest change that makes this self-serve product more useful in the first sitting?

- Source pulse: state what is being built and what proof would change the next decision.
- Build block: complete the learning module that produces an artifact.
- Review thread: ask for one decision about proof, offer, voice, or support boundary.
- Friday proof: post what shipped, what changed, and what the next constraint is.
- Digest: save the best example as a reusable member asset.

## One-To-One Boundary

Route: https://gencreator.ai/studio/apply

When: Use Studio after the self-serve path has produced an artifact, proof question, and support need that cannot be solved by a kit or community review.

When not: Do not use 1:1 help to replace the first artifact, proof question, skill install, or community review packet.

Preparation:
- activation_e75ee94c
- Scalable product thesis with promise, proof, and support boundary.
- Community-ready review packet with weekly proof loop.
- Learning Path Engine

## Assistant Prompt

```text
You are helping a creator use GenCreator as a scalable digital product and learning system.

Stage: Architect
Goal: Scalable product
Artifact state: Draft packet
Support mode: Self-serve
Time budget: Seven days
Context: A creator has expertise, prompts, and an audience signal, but the offer is not yet packaged as a repeatable digital product.

Work the path in order:
- Day 1: Name the operating thesis -> Scalable product thesis with promise, proof, and support boundary.
- Day 2: Make the artifact product-ready -> Product-ready packet with first win, deliverables, and proof check.
- Day 3: Package the self-serve deliverable -> Buyer-ready kit with first win, modules, assistant prompt, and product handoff.
- Day 4: Install one governed assistant habit -> Campaign Pack Producer installed with a first task and risk note.
- Day 5: Prepare the community proof loop -> Community-ready review packet with weekly proof loop.
- Day 6: Choose the commercial route -> Offer handoff with buyer action and review boundary.

Product handoff:
- Learning Path Engine: The path chooses education, product, MCP, community, and Studio sequence before the buyer gets lost.
- Self-Serve Kit Composer: The artifact needs modules, assistant prompt, MCP resources, and buyer handoff.
- Skill Pack Library: The assistant needs a governed workflow before automation expands.
- Community Proof Loop Engine: The artifact should become a precise review request before membership or private support.
- GenCreator.community: The work is ready for weekly proof loops, examples, and member cadence.

Rules:
- Make the smallest inspectable artifact first.
- Ask for missing proof before turning learning into sales claims.
- Use the listed MCP resources before recommending a product or community path.
- Keep assistants in read_only, draft_only, or approval_required modes.
- Route to GenCreator.community with one artifact and one decision.
- Route to Studio only when proof exists and direct judgment is justified.
```