# GenCreator Community OS

Operating state: community_os_e232a613
Canonical: https://gencreator.ai/community/os

Yes: GenCreator should lead with scalable digital products, use Community OS as the practice layer, expose MCP resources for assistants, and reserve 1:1 help for proof-backed moments where judgment changes the outcome.

Community becomes the room where artifacts improve: vault memory creates context, proof loops create cadence, member examples create culture, and Studio remains a selective escalation path.

## First Win

Open the launch room with one artifact, one decision, one proof signal, and the next paid or free route.

## Readiness

Score: 43
Label: draft_room
Reason: The operating loop exists, but proof, gating, or paid membership wiring still needs a clean handoff.

Missing:
- Confirm community product ID
- Wire Skool gating
- Point Whop success redirect to this success route
- Add paid member proof-loop template
- Add member artifact library persistence

## Product Handoff

GenCreator.community ($49/mo)

Product: https://gencreator.ai/community/os
Buy or inspect: https://gencreator.ai/products/buy?product=gencreator-community
Readiness: https://gencreator.ai/products/checkout?product=gencreator-community

Next action: Connect Whop membership purchase to Community OS, onboarding, Skool access, and the weekly proof loop.

Blockers:
- Confirm community product ID
- Wire Skool gating
- Point Whop success redirect to this success route
- Add paid member proof-loop template
- Add member artifact library persistence

## Operating Rooms

- Source Pulse: https://gencreator.ai/community/onboarding#proof-loop
  Access: public
  Job: Turn motivation into source, signal, and proof before the room starts reviewing.
  Output: One source note and one falsifiable proof question.
  Agent role: Signal Analyst
  Proof signal: Built from Creator Vault state, Community Proof Loop, product manifest, pricing, offers, and the GenCreator strategy.
- Review thread: https://gencreator.ai/community/proof-loop
  Access: member
  Job: Improve one decision, not the entire creator business at once.
  Output: A support boundary decision with the smallest useful change.
  Agent role: Community Concierge
  Proof signal: draft artifact
- Member artifact library: https://gencreator.ai/workspace
  Access: member
  Job: Save the best examples back into operating memory so the community gets smarter.
  Output: Reusable pattern: source, artifact, decision, result, approval status.
  Agent role: Vault Librarian
  Proof signal: member example ready for reuse
- GTM room: https://gencreator.ai/offers
  Access: member
  Job: Convert proof-loop artifacts into offer copy, launch notes, and reply material.
  Output: One proof-backed offer move with checkout readiness visible.
  Agent role: Campaign Producer
  Proof signal: GenCreator.community OS Circle
- Studio gate: https://gencreator.ai/studio/apply
  Access: studio
  Job: Escalate only when proof exists and direct judgment changes the business outcome.
  Output: A bounded review ask with artifact, proof, risk, and desired decision.
  Agent role: Approval Operator
  Proof signal: community-first boundary

## Weekly Operating Loop

- Monday: Open the Source Pulse
  Output: Name what is being built and what proof would change the decision.
  Open: https://gencreator.ai/community/onboarding#proof-loop
- Tuesday: Run the self-serve build block
  Output: Improve the artifact with Creator Vault, Activation Engine, or Campaign Studio before asking people.
  Open: https://gencreator.ai/vault
- Wednesday: Post one review request
  Output: Ask the community to review support boundary only.
  Open: https://gencreator.ai/community/proof-loop
- Friday: Publish Friday proof
  Output: Share what changed, what evidence exists, and what stays constrained.
  Open: https://gencreator.ai/community
- Sunday: Save the digest
  Output: Record the best example in the library with source, result, and approval status.
  Open: https://gencreator.ai/workspace

## Product Ladder

- Activation Engine (Free): https://gencreator.ai/activate
  Role: Create the first operating path.
  Boundary: Use before community if the artifact is still only an idea.
- Creator Vault Kit ($29 proposed): https://gencreator.ai/products/buy?product=creator-vault-kit
  Role: Create the memory layer.
  Boundary: Self-serve templates and updates, not private implementation.
- Agent and MCP Pack ($149 proposed): https://gencreator.ai/products/agent-pack
  Role: Install the assistant operating roles.
  Boundary: Install guidance and updates. Custom agent builds belong in Studio.
- GenCreator.community ($49/mo planned): https://gencreator.ai/products/buy?product=gencreator-community
  Role: Practice the weekly proof loop.
  Boundary: Review rituals, examples, and cadence. Studio handles direct judgment.
- Pricing (Compare): https://gencreator.ai/pricing
  Role: Choose the support layer.
  Boundary: Keep self-serve, community, and Studio visibly separate.
- Offers (Compare): https://gencreator.ai/offers
  Role: Pick the packet or delivery path that matches the artifact.
  Boundary: Buy the concrete asset before asking for direct implementation help.
- Studio ($297/mo confirmed): https://gencreator.ai/studio/apply
  Role: Direct judgment after proof.
  Boundary: Application-led review for active creator systems.

## GTM Moves

- Publish the proof-thread hook
  Channel: X, LinkedIn, newsletter, and short-form script
  Proof: One artifact: Community launch room for the Agent and MCP Pack
  Action: Show the artifact before inviting people into the Circle.
- Open a public sample room
  Channel: Community OS page and free Lounge
  Proof: A generated proof-loop packet and markdown export.
  Action: Let the buyer see the room before the paid gate.
- Turn one member artifact into a library example
  Channel: Weekly digest and offers page
  Proof: Source, decision, result, and approval status.
  Action: Sell the practice through examples, not vague access.
- Make 1:1 help proof-earned
  Channel: Pricing, offers, and Studio application
  Proof: Measured result, customer signal, or reputation risk.
  Action: Keep community scalable and make Studio feel selective.

## MCP Plan

Resources:
- gencreator-community-operating-system: https://gencreator.ai/api/community/os
  Use: Read the composed community state, rooms, ladder, GTM moves, MCP plan, and support boundaries.
- gencreator-community-proof-loop: https://gencreator.ai/api/community/proof-loop
  Use: Generate the review request and weekly proof loop from one artifact.
- gencreator-creator-vault-operating-state: https://gencreator.ai/api/vault/state
  Use: Read memory, product handoff, approval backlog, and community readiness before review.
- gencreator-product-manifest: https://gencreator.ai/api/products/manifest
  Use: Confirm product status, fulfillment artifacts, checkout blockers, and support policies.

Tools:
- gencreator.generate_community_os: Compose Creator Vault, Community Proof Loop, product ladder, GTM moves, and Studio boundary into one operating room state.
- gencreator.generate_community_proof_loop: Generate the review packet that feeds the Community OS.

Prompts:
- gencreator.community_os_review: Review a community operating state before membership, launch, or Studio escalation.
- gencreator.community_review_request: Convert one artifact into a precise review ask.

## Assistant Prompt

```text
You are the GenCreator Community OS operator.

Creator: GenCreator Operator
Artifact: Community launch room for the Agent and MCP Pack
Audience: AI-native creators and founder-led media teams who want repeatable creator intelligence, not scattered prompts.
Offer: GenCreator.community OS Circle
Mode: Launch room
Readiness: draft_room

Use the Creator Vault state before writing community copy. Generate or inspect the Community Proof Loop before asking for feedback. Route the creator through self-serve product first, community review second, and Studio only when proof exists and direct judgment would change the outcome. Make launch blockers visible. Do not promise unlimited private implementation, autonomous posting, or live member persistence until those systems are wired.
```

## Boundaries

- Self-serve: Self-serve products generate the artifact, state, prompt, packet, approval task, or learning path before support is requested.
- Community: Community gives cadence, examples, peer review, artifact library, source pulse, and sharper questions. It is not unlimited private implementation.
- Studio: Studio is the capped direct-judgment layer for revenue, audience, reputation, or implementation decisions that are already backed by proof.
- Not yet automated: Live member persistence, Skool gating, Whop product ID, paid template library, and automated member digest are still explicit launch blockers.