# GenCreator Community Proof Loop

Packet: community_proof_37048b80
Canonical: https://gencreator.ai/community/proof-loop

GenCreator.community should turn finished artifacts into better operating behavior, not passive access or broad feedback.

## First Win

Leave with a precise review request for "Activation plan for the Agent and MCP Pack", a weekly proof loop, and the right next route.

## Entry Rule

Bring one artifact, one decision question, one proof signal, and one support boundary.

## Review Request

Title: Support boundary review for Activation plan for the Agent and MCP Pack

Artifact: Activation plan: Activation plan for the Agent and MCP Pack

Summary: A creator has one product packet, an assistant role, and a draft approval task, but needs the community to review the support boundary before public launch.

Decision: What belongs in self-serve, community review, or Studio direct judgment?

Proof: A draft artifact exists and can be reviewed before public or paid use.

Source credit: Credit the draft artifact that shaped "Activation plan for the Agent and MCP Pack" before asking for review.

Smallest useful feedback: Review only the support boundary decision and name the smallest useful change.

## Weekly Proof Loop

1. Source pulse
   - Job: Name the source material and the proof that would change the plan.
   - Output: Credit the draft artifact that shaped "Activation plan for the Agent and MCP Pack" before asking for review.
   - Prompt: What source made "Activation plan for the Agent and MCP Pack" worth building, and what proof would change your mind?
   - Route: https://gencreator.ai/community/onboarding#proof-loop
   - Agent role: Signal Analyst
   - MCP resource: gencreator-community-proof-loop
2. Build block
   - Job: Improve one artifact before asking for review.
   - Output: One revised activation plan with the decision field visible.
   - Prompt: Improve the artifact only around support boundary. Do not expand the scope.
   - Route: https://gencreator.ai/activate
   - Agent role: Community Concierge
   - MCP resource: gencreator-activation-plan
3. Review thread
   - Job: Ask for one decision instead of broad feedback.
   - Output: Review only the support boundary decision and name the smallest useful change.
   - Prompt: What belongs in self-serve, community review, or Studio direct judgment?
   - Route: https://gencreator.ai/community/onboarding#review-request
   - Agent role: Community Concierge
   - MCP resource: gencreator.community_review_request
4. Friday proof
   - Job: Post what changed, what proof exists, and what remains constrained.
   - Output: Friday proof note for Activation plan for the Agent and MCP Pack.
   - Prompt: State what changed, what evidence supports it, what is still uncertain, and the next constraint.
   - Route: https://gencreator.ai/community
   - Agent role: Approval Operator
   - MCP resource: gencreator.request_approval
5. Digest
   - Job: Save the best example back into operating memory.
   - Output: One member-library note with source, decision, result, and reusable pattern.
   - Prompt: Turn the final artifact into a reusable example for the member library with source credit and approval status.
   - Route: https://gencreator.ai/workspace
   - Agent role: Vault Librarian
   - MCP resource: gencreator-creation-workspace-session

## Community Post Draft

```text
Artifact: Activation plan: Activation plan for the Agent and MCP Pack

What changed:
A creator has one product packet, an assistant role, and a draft approval task, but needs the community to review the support boundary before public launch.

Decision I want reviewed:
What belongs in self-serve, community review, or Studio direct judgment?

Proof I have:
A draft artifact exists and can be reviewed before public or paid use.

Source credit:
Credit the draft artifact that shaped "Activation plan for the Agent and MCP Pack" before asking for review.

Smallest useful feedback:
Review only the support boundary decision and name the smallest useful change.
```

## Product Path

- Activation Engine: https://gencreator.ai/activate
  Role: Create the first operating path.
  When to use: Use before community if no seven-day path exists.
- Community Proof Loop Engine: https://gencreator.ai/community/proof-loop
  Role: Turn the artifact into a review request and weekly loop.
  When to use: Use when an artifact exists but the review ask is still broad.
- Skill Pack Library: https://gencreator.ai/products/skill-packs
  Role: Install the assistant habit.
  When to use: Use when a creator needs a repeatable workflow, not a one-off prompt.
- GenCreator.community onboarding: https://gencreator.ai/community/onboarding
  Role: Bring the artifact into practice.
  When to use: Use after the artifact, decision, and proof signal are named.
- Community OS: https://gencreator.ai/community/os
  Role: Compose the proof loop, rooms, offer bridge, GTM moves, MCP plan, and Studio boundary.
  When to use: Use when the artifact is ready to become a community operating state.
- Pricing: https://gencreator.ai/pricing
  Role: Choose the support layer without blurring self-serve, community, and Studio.
  When to use: Use when the creator needs to compare free tools, OS Circle, and Studio.
- Offers: https://gencreator.ai/offers
  Role: Pick the starter packet, delivery asset, or service boundary that fits the artifact.
  When to use: Use when the proof-loop packet reveals a concrete product need.

## Stage Handoff

Current stage: Architect

Identity moment: I have a named structure for my creator operating system.

Threshold: One artifact, one question, and one proof metric are ready.

Next route: https://gencreator.ai/community/onboarding

Next action: Enter the weekly proof loop with one review request.

## MCP Plan

Resources:
- gencreator-community-proof-loop: https://gencreator.ai/api/community/proof-loop
  Use: Read the review request, weekly proof loop, product path, and assistant handoff.
- gencreator-activation-plan: https://gencreator.ai/api/products/activation-plan
  Use: Confirm the seven-day operating path before entering community.
- gencreator-agent-mcp-pack: https://gencreator.ai/api/products/agent-pack
  Use: Install the Community Concierge or Approval Operator role before review.
- gencreator-product-manifest: https://gencreator.ai/api/products/manifest
  Use: Check product status, delivery artifacts, paid access blockers, and support boundaries.

Tools:
- gencreator.generate_community_proof_loop: Create a review packet and weekly proof loop from one artifact.
- gencreator.request_approval: Create a human review record for public, paid, customer-facing, or risky actions.

Prompts:
- gencreator.community_review_request: Convert a finished artifact into a precise review ask.
- gencreator.install_agent_pack: Install the Community Concierge, Approval Operator, or Eve operating role.

## Support Boundary

- Self-serve: Self-serve creates the artifact, markdown, prompt, kit, approval task, or agent role without private implementation.
- Community: Community gives review cadence, examples, source pulse, proof loops, and sharper questions. It is not unlimited consulting.
- Studio: Studio is direct judgment for active creator systems when revenue, audience, or reputation risk changes the outcome.

## Assistant Prompt

```text
You are the GenCreator Community Concierge.

Artifact: Activation plan: Activation plan for the Agent and MCP Pack
Stage: Architect
Support intent: Community review
Decision need: Support boundary
Proof level: Draft artifact

Create a community review request with:
- Artifact summary.
- One decision question.
- Proof available.
- Source credit.
- Smallest useful feedback ask.

Then run the weekly proof loop:
- Source pulse: Credit the draft artifact that shaped "Activation plan for the Agent and MCP Pack" before asking for review.
- Build block: One revised activation plan with the decision field visible.
- Review thread: Review only the support boundary decision and name the smallest useful change.
- Friday proof: Friday proof note for Activation plan for the Agent and MCP Pack.
- Digest: One member-library note with source, decision, result, and reusable pattern.

Boundary:
- Community gives cadence, examples, and review prompts.
- Do not promise unlimited private implementation.
- Route to Studio only when proof exists and direct judgment would change the outcome.
- Current stage handoff: Enter the weekly proof loop with one review request.
```