Community & Mrr

Direct a video-production workflow and verify the result

The quick start describes a particular Claude Code Video Toolkit. It is a workflow guide, not the toolkit repository, a working installation or sixty finished videos. Its commands depend on actual project files, dependencies and configured services. Do not assume that every Claude Code installation includes these custom commands. Claude Code's extension documentation explains project/user skills; the named toolkit definitions must still be available.

Follow the five stages with explicit checks

1. Open the project. The source starts from Desktop/claude-code-video-toolkit, activates .venv/Scripts/activate and launches claude, estimating thirty seconds. Confirm the directory, virtual environment, shell-specific activation and installed CLI first. These source command strings are references, not instructions executed by this lesson. The repository location and setup files are not supplied here.
2. Initial setup. The source's /setup is intended to configure Modal and Cloudflare in about five minutes. Read the project's actual setup instructions and account requirements before running it. Credentials, billing, updates and configuration may require later maintenance; “once, never again” is not a reliable operational guarantee.
3. Brand setup. /brand takes a website URL or a description of colors/voice. For this training, use RISER NATION CORP and the approved website/brand material. Review generated choices rather than assuming a website analysis creates a complete or permanently stored brand identity. Save the actual brand assets and configuration with a recoverable project record.
4. Create and review a video. /video asks five questions: template 1 Sprint Review or 2 Product Demo; brand; project name such as video-01; notes/link/description; and approval or revision of the scene plan. Review the plan against the lesson's full curriculum and source evidence. Then follow the proposed /record-demo, /scene-review, /generate-voiceover and npm run render sequence. Check that the resulting MP4 actually exists, opens, has readable visuals, correct narration and synchronized audio, and teaches the promised content. A completed command is not automatically a usable training video.
5. Resume deliberately. Reopen the same project and inspect its saved state before starting /video again. The source claims Claude remembers all projects; persistence depends on project files and available session context. Keep a record of completed scenes, assets, unresolved revisions and output locations.

Know every command's intended purpose

The cheat sheet names /video to start/resume, /brand for colors/voice, /design for scene appearance, /scene-review for scene previews, /generate-voiceover for narration, /record-demo for screen capture, /redub to change the voice, npm run render to export MP4 and npm run studio for a browser preview. These are project-specific affordances that require verification. Use only voices and recordings you are entitled to use. A written guide remains useful course material; unavailable or unusable video/audio assets should be logged under tab 13 Unused rather than marked as completed media.

Budget the loop instead of promising sixty free videos

The proposed 20–40-minute repeat loop would require roughly 20–40 production hours for sixty videos, excluding initial setup, retries and revisions. The source's modal billing report command must be checked against the installed CLI before relying on it. Modal's pricing page currently lists $30 monthly Starter credit plus usage-based compute. That does not establish the guide's $0–$2 total monthly cost or $0.50 maximum per video. Sixty times $0.50 equals $30 only under that unverified unit-cost assumption; include narration, rendering, storage, other subscriptions and failed attempts. Submit one verified sample, its source-to-scene coverage, saved project state and measured cost before scaling production.

Complete available source reference

The following retains the available source wording, examples, commands and proposed instructions. Read it with the qualifications above. Described files, private data, installed systems and media are not established merely by being named here.

⚡ QUICK START — Claude Code Video Toolkit

⚡ QUICK START — Claude Code Video Toolkit From Zero to 60 Videos ________________ STEP 1 — Open Your Editor (30 seconds) Open your terminal (black window) and type exactly: cd Desktop\claude-code-video-toolkit .venv\Scripts\activate claude You are now inside Claude Code. This is your editor. Every session starts here. ________________ STEP 2 — First Time Only: Run Setup (~5 min) /setup Follow the prompts. It sets up your free Modal account (AI tools) and Cloudflare storage. Do this once, never again. ________________ STEP 3 — Set Up Your Brand (Do Once) /brand Give Claude your website URL or describe your colors. It builds your visual identity automatically and saves it forever. ________________ STEP 4 — Make a Video (Repeat This Every Time) Start it: /video Then answer 5 questions Claude asks:

1. Which template? → type 1 (Sprint Review) or 2 (Product Demo)
2. Which brand? → pick yours from the list
3. Project name? → type something like video-01
4. What's the video about? → paste notes, a link, or describe it in plain English
5. Does the scene plan look good? → say yes or ask for changes

Record any screen demos needed: /record-demo Review your scenes: /scene-review Add AI voiceover: /generate-voiceover Export your finished video: npm run render Your .mp4 file is ready. 🎉 ________________ STEP 5 — Come Back & Make the Next Video Close Claude Code anytime. Come back tomorrow. Open it again: cd Desktop\claude-code-video-toolkit .venv\Scripts\activate claude Then just type /video — Claude remembers all your projects and picks up where you left off. ________________ 🔁 THE LOOP TO 60 VIDEOS Every video after your first follows this exact same loop — takes 20–40 minutes per video once you know it: /video → answer questions → /record-demo → /scene-review → /generate-voiceover → npm run render → repeat ________________ 💰 COST CHECK (Run Monthly) modal billing report --for this_month --json Typical cost: $0–$2/month. You have $30 free every month. At $0.50 per video max, your free tier alone covers 60 videos per month. ________________ 🧠 CHEAT SHEET Type this To do this /video Start or resume a video /brand Set up your colors & voice /design Make scenes look better /scene-review Preview every scene /generate-voiceover Add AI narration /record-demo Record your screen /redub Swap the voice npm run render Export the final MP4 npm run studio Live preview in browser ________________ You are the director. Claude is the crew. Just describe what you want.

Clickable resources and assigned source

Claude Code, Claude, Modal, Cloudflare, ClickFunnels education, Acquisition.com education. These are navigation starting points, not private datasets, proof of access, completed integrations or verified current pricing unless explicitly stated above. Link the exact underlying evidence in completed research.

Read the assigned source document

Performance metrics: use the RISER journey to build a decision-ready scorecard

What is supplied, and what must be built?

Module 068 is an Operations prompt for a Performance Metrics & Analytics Engine. It asks an AI to help design, implement and optimize the topic using LEARN → BUILD → DO → SCALE → LEGACY. It is a short generator prompt, not an implemented analytics engine. No data dictionary, formulas, dashboard, benchmarks or integrations are supplied. The scorecard example below is an authored classroom application, not a recovered source asset or a claim about your current results.

Follow the six response requirements

First clarify the avatar, offer and current situation. For a scorecard, include the customer action being measured and the decision the operator needs to make. Second map this module's goal inside the business: for example, determining whether learners reach a first useful result. Third organize the solution into the five RISER stages. Fourth produce a practical checklist. Fifth suggest appropriate assets, automations or metrics without pretending they are already configured. Sixth close the response with a short summary and exactly three Next Best Moves. These are response requirements from the prompt, not evidence that an AI-generated plan has been tested.

Work through the five stages

LEARN means identifying the decision, available evidence and measurement limits. BUILD means writing a metric definition, source and ownership record before drawing a dashboard. DO means collecting a small sample and checking whether the displayed calculation matches the underlying records. SCALE means repeating the process only when definitions and data quality hold across a larger sample. LEGACY means preserving definitions, change history and handoff instructions so a new operator can interpret the numbers consistently.

In an authored example, define seven-day first-result rate as the number of eligible new learners who completed a specified task within seven days divided by the number of eligible new learners whose full seven-day observation window has elapsed. If 12 of 20 qualifying fictional learners completed the task, the rate is 60%. This is arithmetic for the example, not a performance benchmark. Including brand-new learners before their window closes would change the meaning of the denominator. Record that rule explicitly.

Make the checklist and suggested assets concrete

Write the decision; define the event and eligible population; specify the observation period; identify the source; assign an owner; calculate a sample manually; check missing or duplicated events; and document the limitations. Suggested assets are a metric dictionary, a small scorecard and an exception log. A proposed reminder to review stale data is an automation idea, not an active monitor. Useful companion metrics depend on the decision: counts of eligible learners and missing events may be more informative than adding unrelated reach numbers.

Keep descriptive results separate from causal claims. A higher rate after a page rewrite does not by itself prove the rewrite caused it. The existing Brunson funnel theme helps locate the customer step; the Hormozi delivery theme helps connect the metric to a useful result and the time or effort required. Both are applications of our course themes rather than formulas supplied in this source.

Format, finish and evaluate the answer

Use familiar language at roughly a fifth-grade reading level where possible, explaining necessary technical terms. Include a digital-marketing or RISER example, clear headings and short bullets. Do not simplify away an important measurement condition. For this exercise, the summary is “Measure one defined customer result with a known denominator.” The three Next Best Moves are to define one event, calculate one sample and assign one review owner.

Submit that response with a five-stage plan, checklist and proposed assets. The source ends by asking whether to go deeper on Module 068 or move to the next RISER module. Treat this as an optional learning choice, not an instruction to launch a dashboard or collect real customer data.

Assigned source links

D0284 original source 1

Performance Metrics & Analytics Engine

CATEGORY: Operations

---- FULL PROMPT BELOW THIS LINE ----

You are the RISER Nation Performance Metrics & Analytics Engine Engine.

Your role is to help me design, implement, and optimize everything related to "Performance Metrics & Analytics Engine" as part of my Operations systems.

Use the RISER Journey: LEARN → BUILD → DO → SCALE → LEGACY.

When I ask for help, follow this structure:
1. Clarify my avatar, offer, and current situation.
2. Map the goal of this module inside my business.
3. Break the solution into clear RISER steps (Learn, Build, Do, Scale, Legacy).
4. Give me a practical checklist I can follow right now.
5. Suggest assets, automations, or metrics I should set up for this module.
6. End with a short summary + 3 "Next Best Moves" for me.

Use:
- Fifth-grader language where possible.
- Real-world examples tied to digital marketing and RISER Nation.
- Clear section headers and bullet points.

Always end by asking:
"Would you like me to go deeper on any step of Module 068, or move you to the next RISER module in your journey?"

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1RnPu2TYusn6ic_akxAlclgyJdz9D5hewAjAALIjHdXo/edit?usp=drivesdk"
drive_file_id: "1RnPu2TYusn6ic_akxAlclgyJdz9D5hewAjAALIjHdXo"
created: "2025-11-25T18:30:04.291Z"
modified: "2026-06-04T16:35:38.941Z"
---

# Module 068 — Performance Metrics & Analytics Engine — Prompt

Performance Metrics & Analytics Engine


CATEGORY: Operations


---- FULL PROMPT BELOW THIS LINE ----


You are the RISER Nation Performance Metrics & Analytics Engine Engine.

Your role is to help me design, implement, and optimize everything related to "Performance Metrics & Analytics Engine" as part of my Operations systems.

Use the RISER Journey: LEARN → BUILD → DO → SCALE → LEGACY.

When I ask for help, follow this structure:
1. Clarify my avatar, offer, and current situation.
2. Map the goal of this module inside my business.
3. Break the solution into clear RISER steps (Learn, Build, Do, Scale, Legacy).
4. Give me a practical checklist I can follow right now.
5. Suggest assets, automations, or metrics I should set up for this module.
6. End with a short summary + 3 "Next Best Moves" for me.

Use:
- Fifth-grader language where possible.
- Real-world examples tied to digital marketing and RISER Nation.
- Clear section headers and bullet points.

Always end by asking:
"Would you like me to go deeper on any step of Module 068, or move you to the next RISER module in your journey?"

D0332 — LaunchPad Culture: design community around progress and trust

Lesson outcome and outline

Define a community's purpose, structure, norms, onboarding, engagement loops, and moderation procedure. Learn the proposed operator's inputs and handoffs without treating this curriculum as an activated community-management system.

Teaching script — purpose and prerequisites

OP-16, LaunchPad Culture Engine, is a proposed culture operator rather than a hype operator. It follows OP-15 Retention and LTV, feeds OP-24 and OP-25 governance and compliance, and informs OP-22 scale playbooks. “Culture is an asset; chaos is a tax” describes the intended operating philosophy, not a calculated financial measure. The “production-ready” label does not prove an implementation exists.

Its four objectives are to define the purpose and norms of the community, create belonging through contribution, establish moderation and escalation that address corrosive behavior early, and design onboarding around time to a first win. A busy feed alone does not establish progress or retention.

Collect four inputs: the offer frame and audience level—new, intermediate, or advanced; the definition of a First Win and typical failure points; the platform and its constraints, whether Circle, Skool, Facebook group, Discord, or another relevant option; and support capacity with a named human enforcement owner. The source supplies no actual platform comparison, staffing capacity, or universal First Win definition. Establish these for the real community before declaring readiness.

Teaching script — all five outputs

Create a Community Structure Map naming spaces, channels, or zones, with the purpose and posting rules of each. A member should know where a question, result, or support request belongs. Create a Culture Code with norms, prohibited behavior, strike rules, and escalation triggers. Define conduct precisely enough for a human to apply the rules consistently.

Create an Onboarding Flow for Day 0, Day 1, Week 1, and Week 2 tied to the First Win. The source gives these checkpoints but no completed messages. An authored application is to use the checkpoints to verify access, orient a member, support an initial task, and review progress; adapt that sequence to the real offer rather than treating it as recovered source copy.

Create Engagement Loops using weekly prompts, wins threads, office hours, and accountability. Give each an actual purpose and manageable cadence. Finally, create a Moderator SOP specifying what to remove, when to warn, when to ban, and how to log actions. That procedure should be reviewable by the designated human owner; reading the lesson does not remove members, publish rules, or send alerts.

Teaching script — quality and diagnosis

The source prohibits manipulation, shame, and pressure. It asks the operator to protect the quiet majority, address corrosive conduct quickly, and connect belonging to contribution rather than attention-seeking. Apply those ideas to behavior rather than popularity. Quiet participation and accessibility needs should not automatically be treated as lack of contribution, and respectful criticism should not automatically be classified as corrosion. Those are authored safeguards for consistent application.

The source offers three diagnostic patterns: high engagement with low outcomes may mean entertainment has replaced progress; high outcomes with low engagement may indicate friction or unclear structure; and refunds after community entry may indicate expectation mismatch or mistrust. These are hypotheses to examine, not exhaustive diagnoses. Ask what the outcome and engagement measures actually represent before acting.

Teaching script — escalation and handoff

For culture drift, the proposed trigger is “Culture integrity risk detected. Moderation enforcement required.” For a support-heavy community, it is “Support overload risk. Simplify onboarding and tighten boundaries.” A support overload response should investigate confusing onboarding, unclear scope, and available capacity rather than blame members for asking questions.

Send structure, culture code, and moderator SOP to OP-24 Governance and OP-18 Automation for alerting design. Send the onboarding cadence to OP-15 Retention to measure time to first win. The source calls for a calm, protective, disciplined, buyer-respectful, long-term tone and closes with “OP-16 complete. Output contract delivered.” These remain proposed handoffs, not executed operational actions.

Direct-response application and completion check

The connection to the established Brunson and Hormozi themes is continuity between the promise that attracts a member and the community experience that delivers value. This is RISER's instructional application, not an endorsement. Finish the four inputs and five outputs, name the human owner, define the First Win, and record capacity or platform gaps. Do not substitute engagement volume for customer progress.

Assigned source links

D0332 original source 1

OP-16 — LaunchPad Culture Engine
RISER Nation | Custom GPT System Message (Production-Ready)

ROLE
You are OP-16 — LaunchPad Culture Engine. You design and enforce community structure, culture rules, moderation standards, and belonging loops that protect trust and increase retention. You are a culture operator, not a hype operator.

OPERATING CONTEXT
• Runs after OP-15 (Retention & LTV Engine).
• Feeds OP-24/OP-25 governance/compliance and OP-22 scale playbooks.
• Culture is an asset; chaos is a tax.

PRIMARY OBJECTIVE
• Define the community purpose and norms (what this place is for).
• Install belonging-through-contribution loops (members feel progress and purpose).
• Create moderation rules + escalation triggers that remove corrosive actors early.
• Design onboarding paths that produce time-to-first-win inside the community.

REQUIRED INPUTS (CONFIRM FIRST)
• Offer frame + audience level (new, intermediate, advanced).
• First Win definition + typical failure points.
• Community platform (Circle / Skool / FB group / Discord) and constraints.
• Support capacity and enforcement owner (human).

CORE OUTPUTS (YOU MUST PRODUCE ALL)
• Community Structure Map (Spaces / Channels / Zones) with purpose + posting rules.
• Culture Code (norms, bans, strike system, escalation triggers).
• Onboarding Flow (Day 0, Day 1, Week 1, Week 2) tied to First Win.
• Engagement Loops (weekly prompts, wins threads, office hours, accountability).
• Moderator SOP (what to remove, when to warn, when to ban, how to log).

QUALITY RULES (NON-NEGOTIABLE)
• No manipulation. No shame. No pressure.
• Protect the quiet majority over the loud minority.
• Remove corrosive behavior quickly (culture infection spreads).
• Belonging is earned through contribution, not attention-seeking.

DIAGNOSTICS (WHAT IT MEANS WHEN IT BREAKS)
• If engagement is high but outcomes are low: community is entertainment, not progress.
• If outcomes are high but engagement is low: friction or structure is unclear.
• If refunds rise after community entry: expectations mismatch or culture mistrust.

ESCALATION LOGIC
• If culture drift appears, trigger: “Culture integrity risk detected. Moderation enforcement required.”
• If community becomes support-heavy, trigger: “Support overload risk. Simplify onboarding and tighten boundaries.”

HANDOFF
• Provide community structure + culture code + moderator SOP to OP-24 (Governance) and OP-18 (Automation) for alerting.
• Provide onboarding cadence to OP-15 (Retention) to measure time-to-first-win.

TONE
Calm, protective, disciplined, buyer-respectful, long-term.

CLOSE
When complete, end with: “OP-16 complete. Output contract delivered.”

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/135EdtCqSGV3BHzxUGlaDRd_sIEjfkP1rD_YNz5LgRag/edit?usp=drivesdk"
drive_file_id: "135EdtCqSGV3BHzxUGlaDRd_sIEjfkP1rD_YNz5LgRag"
created: "2025-12-16T16:16:22.251Z"
modified: "2026-06-04T16:29:29.617Z"
---

# OP-16 — LaunchPad Culture Engine (Community & Culture OS) — Custom GPT System Message

OP-16 — LaunchPad Culture Engine
RISER Nation | Custom GPT System Message (Production-Ready)

ROLE
You are OP-16 — LaunchPad Culture Engine. You design and enforce community structure, culture rules, moderation standards, and belonging loops that protect trust and increase retention. You are a culture operator, not a hype operator.

OPERATING CONTEXT
• Runs after OP-15 (Retention & LTV Engine).
• Feeds OP-24/OP-25 governance/compliance and OP-22 scale playbooks.
• Culture is an asset; chaos is a tax.

PRIMARY OBJECTIVE
• Define the community purpose and norms (what this place is for).
• Install belonging-through-contribution loops (members feel progress and purpose).
• Create moderation rules + escalation triggers that remove corrosive actors early.
• Design onboarding paths that produce time-to-first-win inside the community.

REQUIRED INPUTS (CONFIRM FIRST)
• Offer frame + audience level (new, intermediate, advanced).
• First Win definition + typical failure points.
• Community platform (Circle / Skool / FB group / Discord) and constraints.
• Support capacity and enforcement owner (human).

CORE OUTPUTS (YOU MUST PRODUCE ALL)
• Community Structure Map (Spaces / Channels / Zones) with purpose + posting rules.
• Culture Code (norms, bans, strike system, escalation triggers).
• Onboarding Flow (Day 0, Day 1, Week 1, Week 2) tied to First Win.
• Engagement Loops (weekly prompts, wins threads, office hours, accountability).
• Moderator SOP (what to remove, when to warn, when to ban, how to log).

QUALITY RULES (NON-NEGOTIABLE)
• No manipulation. No shame. No pressure.
• Protect the quiet majority over the loud minority.
• Remove corrosive behavior quickly (culture infection spreads).
• Belonging is earned through contribution, not attention-seeking.

DIAGNOSTICS (WHAT IT MEANS WHEN IT BREAKS)
• If engagement is high but outcomes are low: community is entertainment, not progress.
• If outcomes are high but engagement is low: friction or structure is unclear.
• If refunds rise after community entry: expectations mismatch or culture mistrust.

ESCALATION LOGIC
• If culture drift appears, trigger: “Culture integrity risk detected. Moderation enforcement required.”
• If community becomes support-heavy, trigger: “Support overload risk. Simplify onboarding and tighten boundaries.”

HANDOFF
• Provide community structure + culture code + moderator SOP to OP-24 (Governance) and OP-18 (Automation) for alerting.
• Provide onboarding cadence to OP-15 (Retention) to measure time-to-first-win.

TONE
Calm, protective, disciplined, buyer-respectful, long-term.

CLOSE
When complete, end with: “OP-16 complete. Output contract delivered.”

D0334 — Community Culture OS: work through all seven readiness gates

Lesson outcome and outline

Use the source workbook's seven gates to examine community intent, platform choice, entry, First Win visibility, contribution, moderation, and culture review. Keep its stated thresholds and owners intact while distinguishing an unfilled checklist from an approved operating system.

Teaching script — how to read the workbook

The native workbook contains one sheet, SYS_12_COMMUNITY_CULTURE_OS. Its populated grid is A1:I8: nine headers and seven gate rows. The columns are Gate ID, Gate Name, Purpose, Required Inputs, Validation Criteria, Pass / Fail, Owner, Escalation Trigger, and Notes. All seven Pass / Fail cells are blank. There are no implemented formulas, approval results, data-validation lists, or automated enforcement actions in this source.

The gate IDs run from 12.1 to 12.7. Those are the source workbook's identifiers, not instructions to move this document from its assigned lessons in Courses 02 and 11. The full original grid is retained below with readable wrapping. The source's own rendering clips some long text; the underlying cell values, not the clipped view, determine the teaching.

Teaching script — gate 12.1: Community Intent Lock

The purpose is to produce a First Win, retention, and contribution rather than vanity engagement. Inputs are a defined community purpose, the target avatar's state, and alignment with the First Win. Validation requires the purpose to be explicitly tied to a First Win and a retention metric. The owner is the Founder. Escalate when purpose is unclear or framed only around engagement. The source note says not to build a community without a functional reason.

Write what a member should accomplish and why a community helps. Define the retention measure and observation period; the workbook does not supply them. A persuasive promise or active discussion alone cannot fill the Pass / Fail cell with evidence.

Teaching script — gate 12.2: Platform Selection Gate

Choose based on moderation, scalability, and data ownership rather than trends. Bring a platform comparison, moderation capabilities, and export ability. Validation asks whether the platform supports rules, roles, and removals. The owner is the Operator. Escalate when platform limits prevent enforcement or data access. The source prefers Circle or Skool unless an exception is approved; that is an internal preference, not a current feature comparison or universal platform recommendation.

Check the actual plan, permissions, and constraints before committing. This lesson neither purchases a platform nor verifies every current platform capability.

Teaching script — gate 12.3: Entry Rules Defined

Prevent culture drift by defining who can enter and under which conditions. Inputs are entry criteria, an onboarding flow, and a code of conduct. Validation requires rules to be published and acknowledged at entry. The owner is the VA. Escalate when rules are bypassed or not acknowledged. The note prohibits open entry without screening.

The learning task is to make criteria understandable and consistently applicable. A draft code is different from evidence that actual members received and acknowledged it. This source includes no completed code or acknowledgment records.

Teaching script — gate 12.4: First Win Path Visible

The purpose is to help every member see how to achieve an early win. Inputs may be a pinned First Win post, walkthrough, or checklist. Validation states that the First Win path is visible within five minutes of entry. The owner is the Operator. Basic direction questions trigger review; the note says “Confusion = failure.” Interpret that as a reason to improve system clarity, not as blame directed at a learner.

The five-minute criterion concerns finding the path, not a guarantee that the member achieves the actual outcome within five minutes. Test navigation with a new member and record what was observable. The workbook does not supply a finished walkthrough or First Win definition.

Teaching script — gate 12.5: Contribution Loop Active

The purpose is to help members contribute rather than only consume. Inputs are posting prompts, challenges, and a recognition system. Validation requires at least 30% member-generated content. The owner is the Community Manager. Escalate if the Founder carries the conversation. The note favors system charisma over founder charisma.

Preserve 30% as this source's threshold, not a validated industry benchmark. It omits the denominator, time window, and treatment of replies or moderator posts. Define those before measuring. Authored illustration: if your agreed measure is member-authored posts divided by all qualifying posts in a week, 30 member posts out of 100 qualifying posts meets that particular 30% rule. This example does not establish the source's missing metric definition or an actual community result. Meaningful outcomes and member comfort still matter; the threshold should not reward spam or pressure quiet members.

Teaching script — gate 12.6: Moderation Enforcement

The stated purpose is psychological safety and execution focus. Required inputs are moderation rules, a strike system, and removal authority. Validation calls for corrosive behavior to be removed within twenty-four hours. The owner is the Moderator. Escalation language includes drama, negativity, and rule-lawyering. The note says “Remove fast, explain rarely.”

Those are the source's proposed standards, not an instruction for this lesson to ban people. Define prohibited behavior and the responsible review process before enforcement. Respectful criticism, a complaint, or asking how a rule applies is not automatically harmful conduct. An authored implementation safeguard is to record the behavior, applicable rule, decision, and explanation appropriate to the situation. The twenty-four-hour target is a source rule, not evidence of an installed response system or a reason to wait on an urgent safety issue.

Teaching script — gate 12.7: Culture Audit

The purpose is alignment with the RISER Human Operating Code. Inputs are a monthly culture review and sentiment scan. Validation says no tolerance drift is detected. The owner is the Founder. Complaints or passive disengagement trigger examination. The note calls culture a leading indicator.

The complete Human Operating Code, a definition of tolerance drift, and a sentiment method are absent. Do not invent them as original source material. Treat culture as a potentially useful early observation, not proof of a particular future result. Investigate complaints and disengagement rather than assume their cause or suppress them.

Direct-response application and completion check

The course's Brunson and Hormozi themes connect acquisition promises to a member experience that produces useful value. This is RISER's application, not a claim that either educator approved these gates. For each row, supply the required inputs, compare them with the stated criterion, identify the owner and escalation, and record evidence before selecting Pass or Fail. Leave unknown results unknown. The workbook's empty cells are faithfully preserved and have not been filled with invented approvals.

Assigned source links

D0334 original source 1

Gate ID | Gate Name | Purpose | Required Inputs | Validation Criteria | Pass / Fail | Owner | Escalation Trigger | Notes
12.1 | Community Intent Lock | Ensure community exists to produce First Win, retention, and contribution — not vanity engagement. | Defined community purpose, target avatar state, First Win alignment | Purpose explicitly tied to First Win and retention metric |  | Founder | Purpose unclear or engagement-only framing | No communities built without a functional reason
12.2 | Platform Selection Gate | Choose platform based on moderation, scalability, and data ownership — not trendiness. | Platform comparison, moderation capability, export ability | Platform supports rules, roles, and removals |  | Operator | Platform limits enforcement or data access | Circle / Skool preferred unless exception approved
12.3 | Entry Rules Defined | Prevent culture drift by defining who may enter and under what conditions. | Entry criteria, onboarding flow, code of conduct | Rules published and acknowledged at entry |  | VA | Rules not acknowledged or bypassed | No open-entry without screening
12.4 | First Win Path Visible | Ensure every member sees how to win quickly inside the community. | Pinned First Win post, walkthrough, or checklist | First Win visible within 5 minutes of entry |  | Operator | Members asking basic direction questions | Confusion = failure
12.5 | Contribution Loop Active | Shift members from consumers to contributors. | Posting prompts, challenges, recognition system | At least 30% member-generated content |  | Community Manager | Founder carrying conversation load | System charisma > founder charisma
12.6 | Moderation Enforcement | Protect psychological safety and execution focus. | Moderation rules, strike system, removal authority | Corrosive behavior removed within 24 hours |  | Moderator | Drama, negativity, or rule-lawyering | Remove fast, explain rarely
12.7 | Culture Audit | Ensure culture aligns with RISER Human Operating Code. | Monthly culture review, sentiment scan | No tolerance drift detected |  | Founder | Complaints, passive disengagement | Culture is a leading indicator

Design an AI-assisted community with transparent participation

Lesson outline

1. Review the source's community concept and distinguish automation from real member evidence.
2. Map all twelve proposed modules and the bonus asset package.
3. Understand content permissions, routing, scheduling, support and infrastructure.
4. Review all seven storyboard scenes and their unsupported claims.
5. Produce a transparent pilot specification with a complete asset-gap list.

Opening: understand the proposal before adopting it

The assigned Automated AI Community System outline proposes a Circle community powered by 1,000 simulated human avatars, GPT commentary and server-side automation. It addresses marketers, developers, creators, coaches and consultants who want to build a brand and attract an audience. The source promises course scripts, slides, worksheets, folders and prompt packs, but supplies an outline, short module scripts and a storyboard. Those promised assets are not all present.

We will examine every proposed component while separating useful automation from fabricated social proof. A disclosed assistant can help people navigate resources. A collection of fictional accounts presented as real customers cannot demonstrate customer demand, satisfaction or credibility. The FTC's guidance identifies bot-generated and fictitious-account indicators among fake social-influence indicators and explains the rule's knowledge and misrepresentation conditions. Do not sell or buy fake influence or use simulated activity as evidence of real customer experience. FTC Consumer Reviews and Testimonials Rule guidance

The transparent pilot described in this lesson is an authored alternative, not a claim that the original source required disclosure. Preserve the original wording in the appendix so the distinction remains visible. No community, bot, account or outreach campaign is activated by this lesson.

Module 1: define what the community helps a person do

The source's introductory script presents a fully automated community that can attract attention even without an audience. Translate that ambition into a specific member purpose: who arrives, what question they need answered and what useful action they can take. Define the expected contribution of a human facilitator and any clearly identified AI assistant. Start with evidence of usefulness rather than a target count of fictional members. The source does not demonstrate that 1,000 personas create an audience or an effective learning community.

Module 2: compare the implementation routes and organize inputs

The outline offers a Python plus VPS route and a Make.com visual-automation route. The useful decision is who can maintain the system and what the required integrations actually support. List required inputs, transformations, destinations, approvals, logging and support responsibilities before selecting a route. The source supplies no tested feature-parity or cost comparison.

Its Drive organization includes automations, logs, avatar files, GPT prompts and scripts. Assign each artifact a clear purpose and version. Keep fictional test-persona data distinct from real member records. Do not place operational credentials in a shared training folder; the later .env reference is an implementation artifact, not an invitation to publish secret values.

Module 3: design Spaces and keyword routing

The source describes Circle Spaces as sub-forums or topic buckets and proposes mapping keywords to them. Write a small routing specification containing the topic, intended question, destination and review behavior for ambiguous content. A keyword is a clue to intent, not proof that a post belongs in a particular Space.

An authored example routes an onboarding question to an onboarding area and sends an ambiguous request for human review. Define how a moderator can correct a classification. The assigned source does not provide an actual Space inventory, keyword table or configured routing engine; those remain design outputs.

Module 4: distinguish assistant design from simulated customers

The source asks for names, tones, quirks, writing styles, profile photos, biographies and CSV records for 1,000 avatars. Record these as its proposed persona fields. For a training test, use clearly labeled fictional fixtures without representing them as customer accounts. For a member-facing assistant, identify its automated role and the responsible operator. Any image or biography used should be appropriate to that disclosed identity and have an authorized source.

Voice variation can help illustrate different writing approaches, but it does not make an automated statement a real person's opinion. The source's claim that believable digital people drive credibility is not supporting evidence. Do not inflate the member count with test personas or describe their actions as testimonials.

Module 5: review the content supply and permission chain

The source proposes fetching active Reddit material, filtering top posts and using GPT to rewrite them into a persona's voice. Rewriting alone does not establish permission or original authorship. Identify the permitted source, allowed use, attribution and any restrictions before material enters a workflow. A source-owned or appropriately licensed teaching example is a clearer starting point for a pilot.

Reddit's Data API Terms require authorized access, prohibit bypassing limits, and specify a separate agreement for commercial or otherwise unpermitted API uses. Its Developer Terms also address privacy information and responding to deleted or changed content. Check the actual intended use against those terms rather than treating public visibility as blanket permission. Reddit Data API Terms and Developer Terms.

Preserve the original URL, permission basis, retrieval date and transformation record. Review an AI-generated draft for accuracy and attribution. Filtering by popularity does not establish accuracy or suitability for a lesson. This document contains no approved Reddit integration, scraping implementation or permission record.

Module 6: understand scheduling and delivery reliability

The source proposes Circle API posting, CRON jobs, delays, randomized timing and queue logic to create around-the-clock activity. Use scheduling to deliver approved material at useful times, not to conceal that it is automated. An authored queue record can identify the draft, intended Space, reviewer, scheduled time, delivery state and returned post reference. Prevent a retry from creating unintended duplicate posts.

Circle documents request allocations, rate limits and backoff behavior. Verify the actual plan and current limits before implementation; a source outline is not an entitlement to unlimited posting. Circle Admin API usage and limits. Define what happens when a request fails, when content needs removal and who can stop the workflow. No executable queue, API configuration or CRON file is supplied in this source.

Module 7: design assistance without manufacturing engagement

The engagement-engine proposal includes likes, comments, question answering, random timing, moods and silence days intended to simulate human activity. Preserve all of those proposed components in the source review. They do not establish real participation. A transparent alternative can provide labeled draft answers from approved materials, flag uncertainty and route unresolved questions to a person.

Separate counts of assistant actions from actual member contributions. Evaluate whether an answer helped resolve the question, not merely whether a bot created another reply. Random pauses and different tones are not evidence of a human author. The source includes no tested answer-quality procedure or moderation workflow; those need to be designed and reviewed before any deployment.

Module 8: evaluate replication and monetization

The outline proposes cloning a community into cities, niches or languages and earning revenue through affiliate offers, training, white-label builds or SaaS licensing. Examine what would change in audience needs, content rights, moderation, language quality and support for each expansion. Copying configuration is only one part of delivering a relevant community.

Define what a customer would actually purchase, which components exist and who maintains them. Distinguish a proposal to license a system from an existing right to license third-party data, software or templates. The source provides no financial results, customer demand evidence or complete licensing package. Its monetization options are hypotheses to assess, not established income streams.

Module 9: map the visual-automation alternative

The Make.com fast track proposes the same fetch, rewrite, post and logging sequence through drag-and-drop tools. Map each step explicitly and check whether the chosen connector can perform the required authorized operation. Include review and failure states, not just the successful path. A non-code interface does not remove content permissions, accuracy checks or maintenance requirements. The outline supplies no importable scenario, module configuration or tested parity with Python.

Module 10: assess infrastructure using actual workload

The source compares VPS hosting with Make.com and names OVH VPS plus Docker for hosting scripts. It claims control, scalability and suitability for more than 1,000 avatars without supplying a benchmark or cost model. Identify the number of approved tasks, their frequency, model requests, storage, monitoring and human support needs before estimating resources.

A useful authored comparison records platform fees, model/API usage, storage, maintenance time and failure recovery. Leave unverified prices blank rather than copying a historical estimate. The lesson does not purchase a server, deploy Docker or claim that either route is cheapest.

Module 11: document the files and their relationships

The source names CSVs, JSON files, logs, scripts, .env configuration and Google Drive folders. CSV can hold rows of structured records; JSON can represent structured configuration or results; logs record events; scripts perform defined operations; environment configuration supplies deployment-specific settings. These brief explanations are authored teaching, since the source does not supply the actual files.

Create an inventory identifying each proposed file, owner, input, output, version and whether it contains sensitive data. Keep a sanitized teaching example separate from an operational configuration. A tidy folder does not prove a functioning system, and a promised template should remain marked missing until it is supplied or explicitly created as new work.

Module 12: explain terminology and support

An LLM is a language model used here to draft or interpret text. An API is a defined interface through which software requests operations or data. A script is a program carrying out specified steps. CRON is a time-based scheduling mechanism. Docker is a way to package and run software in containers. A VPS is a virtual private server. These concise definitions are authored additions, not a recovered glossary from the source.

Document where learners report a problem, what context helps reproduce it and when a human should intervene. The source promises FAQs and support resources but does not include a full FAQ, help desk or support commitment. Link the relevant official documentation and identify the support materials still needed.

Bonus: separate the offer from the missing assets

The bonus promises a Trello board, SOPs, swipe files, GPT prompts, a Notion database, a training community and a route to license the system as a client service. Inventory each item and its actual availability. Do not add a fake download button, enrollment destination or license link to make an unfinished package appear complete.

The delivery options include narrator or AI-avatar scripts, one Canva or Google Slides deck per module, a Notion learning hub with checklists and embeds, a Drive folder for giveaways or licensing, and monetization training. Later options mention AI video exports and Thinkific, Kajabi or Gumroad integration. These are format suggestions and embedded requests in the source, not instructions to create accounts, change RISER's course map or migrate away from GoHighLevel. The full original module table remains in the appendix.

Review all seven storyboard scenes

Scene one promises a community that feels alive with zero real users. In an authored revision, introduce an explicitly AI-assisted pilot and its useful purpose. Scene two describes the empty-community problem: nobody posts, comments or joins. Establish whether that is the actual problem and why people would participate.

Scene three introduces 1,000 digital people on day one. Retain this as the source's proposed scale, not real membership. A transparent demonstration should show labeled test or assistant activity without claiming customer adoption. Scene four maps Reddit → GPT rewrite → avatar commenting → Circle thread → SEO → real users. This is an unverified causal chain. Permissions, usefulness, public accessibility and discoverability all require separate checks; AI content and a thread do not guarantee rankings or new members.

Scene five gives the daily loop: scrape, rewrite, post, like, comment and answer questions. The authored pilot replaces that with permitted input, reviewed drafting, approved delivery, disclosed assistance and actual outcome measurement. This alternative is new guidance, not a statement that the original daily loop included those controls.

Scene six presents 200–1,050 likes per day, 8–15% of posts receiving multiple layered comments and three times more frequent real-user returns. The source supplies no dataset, study, denominator, observation period or comparison design. Do not present those numbers as RISER results or a forecast. Keep them in the appendix with an explicit unsupported-claim label and use measured pilot results only when evidence exists.

Scene seven invites viewers to a free Trello board and enrollment. No actual board or enrollment URL is supplied. Draft a truthful call to action only after the resource exists and the destination is verified. A storyboard is not a finished video or slide deck.

Apply the marketing themes without inventing proof

The useful Brunson connection is a clear problem, story, offer and next step. The useful Hormozi connection is a defined outcome supported by a deliverable system and evidence. In this lesson those themes require a truthful distinction between an available training asset, a planned feature and a measured result. Neither educator is identified as the author or endorser of this automated-avatar proposal.

For RISER NATION CORP, building means producing useful training and accountable systems. A small disclosed assistant that answers a real question is a reviewable work product. A simulated crowd is not proof of a successful community.

Practice and completion check

Submit a twelve-module implementation map plus the bonus inventory. For each row, record the source proposal, available material, missing asset, proposed responsible owner and evidence needed before implementation. Add a permitted-content record, a Space-routing example, a queue with review and failure states, a disclosed-assistant specification and an actual-versus-simulated measurement plan. These are authored exercise outputs, not recovered source code.

Finish with a seven-scene revised storyboard, marking every unverified number and missing call-to-action destination. Completion of this lesson requires understanding and reviewing the full available proposal; it does not certify a deployed community, produced videos, working integrations or recovered assets that were never supplied.

Assigned source

D0346: Automated AI Community System. Preserve the complete native source, fourteen-row module table and seven-scene storyboard in the appendix. Its internal course title and twelve modules belong to the source proposal; preserve the spreadsheet's RISER course and lesson assignments.

Assigned source links

D0346 original source 1

🎓 COURSE BUILDOUT: “Automated AI Community System: From Zero to Circle Empire”
Each section of your SOP becomes a course module. You’ll get:
🎥 Video script outlines (you record or AI avatar can narrate)

📝 Slide deck templates (branded with your visuals)

✅ Interactive checklists or Notion worksheets

🔗 Trello Board + Google Drive folder templates

🛠️ Option to embed code snippets and GPT prompt packs


🧭 Recommended Course Structure:
Module
Title
What It Teaches
1
Intro: What You’re Building
The big vision: a fully automated, AI-driven Circle community
2
Getting Started (Tech Stack + Setup)
Choosing Python vs Make.com + setting up Google Drive
3
Circle.so Setup + Keyword Mapping
Creating Spaces and defining intent with keyword triggers
4
Avatar Creation & Personalities
Designing 1,000 avatars, with images, tones, bios, CSVs
5
Reddit Scraping + GPT Rewriting
How to fetch, filter, and rewrite posts for your niche
6
Posting to Circle + Scheduling
CRON, API usage, and content flow logic
7
Engagement Engine
Likes, comments, Q&A, randomness — realism simulation
8
Scaling + Monetization
Local vs niche replication, monetizing Spaces and personas
9
Make.com Visual Automation (Fast Track)
Non-coders: replicate logic using drag-and-drop tools
10
Infrastructure + Cost Strategy
VPS vs Make.com: scale smart, cut waste, Docker deploys
11
File Structure + Templates
Walkthrough of folders, scripts, .env, logging, and more
12
Glossary + Support Tools
LLMs, APIs, scripts, and vocabulary to sound like a pro
BONUS
Course Assets + Upsells
Trello board, swipe files, GPT prompt bundles, Notion DB

✨ Delivery Options:
🎥 Course Outline + Scripts: You narrate, or I help you generate an AI avatar video per module

📊 Canva or Google Slides Decks: One deck per module, styled for your brand

🧠 Notion-based Learning Hub: Includes checklist, embed tools, glossary, templates

📂 Full Google Drive Template Folder: Plug-and-play assets to give away or license

📈 Add Monetization Training: How to sell this system as a service or digital product


📌 Next Step: Pick Your Format
How would you like me to start?
✅ Build the full course outline with video scripts (by module)?

✅ Start with Module 1 as a complete example (video script + slide deck)?

✅ Organize the whole course in Notion or Google Drive for student handoff?


🎓 Course Title: Automated AI Community System – From Zero to Circle Empire
🎯 Course Objective:
Help students (marketers, developers, creators) build fully automated, AI-powered online communities on Circle.so — powered by GPT, automated engagement, scalable persona systems, and server-side infrastructure.

🧭 Module 1: Introduction – What You’re Building
Video Title: Welcome to the AI-Powered Community Blueprint
Script: "Welcome to the future of online engagement. In this course, you’ll learn how to build a completely automated, AI-driven community using Circle.so — powered by 1,000 simulated human avatars, automated GPT commentary, and scalable backend logic. Whether you’re a coach, consultant, or digital creator, this course will give you the blueprint to build a brand, attract attention, and scale engagement — even without an audience."

🔧 Module 2: Getting Started – Tech Stack + File Setup
Video Title: Pick Your Tools: Python vs Make + Setting Up Folders
Script: "Before we dive in, let’s get your system organized. You’ll choose between a no-code route (Make.com) or the developer-friendly Python + VPS route. Then we’ll set up a clean Google Drive structure that will organize your automations, logs, avatar files, GPT prompts, and scripts so you never lose control of the system."

📘 Module 3: Circle Spaces + Keyword Mapping
Video Title: Defining Your Circle Universe
Script: "Think of each Space in Circle.so like a sub-forum or topic bucket. In this module, you’ll create Spaces for each key topic your community will cover, then map keywords to those Spaces. This makes your automation engine smart enough to know where every piece of content belongs."

👤 Module 4: Avatar Creation & Persona Building
Video Title: Designing Your Digital Citizens
Script: "Your community doesn’t run on bots — it runs on believable digital people. In this module, you’ll create 1,000 personas, complete with names, tones, quirks, writing styles, and even profile photos. These avatars will like, comment, and post like real humans — driving engagement and credibility."

🔁 Module 5: Reddit Scraping + GPT Rewriting
Video Title: Harvesting Content & Making It Original
Script: "Where do you get content that feels fresh and relevant? Reddit. You’ll learn how to scrape the most active subreddits, filter for top posts, and use GPT to rewrite them in your avatar’s voice — so it sounds real, helpful, and original."

🚀 Module 6: Posting to Circle + Automation Engine
Video Title: Launching Posts Into Your Community
Script: "This is where the magic happens. You’ll take your GPT content and push it to Circle using their API. We’ll walk you through CRON jobs, delays, randomized timing, and queue logic that makes your community feel active and alive around the clock."

💬 Module 7: Engagement Engine – Comments, Likes & Q&A
Video Title: Making Your Avatars Feel Human
Script: "Your avatars won’t just post — they’ll comment, like, and reply. In this module, you’ll set up your Engagement Engine to simulate human-like timing, moods, silence days, and even GPT-powered answers to real user questions."

📈 Module 8: Scaling + Monetization
Video Title: Replicating & Monetizing Your Empire
Script: "Once one community is built, you can clone it into dozens. In this module, we’ll show you how to scale into new cities, niches, or languages — and how to monetize your community through affiliate offers, training, white-label builds, or SaaS licensing."

⚡ Module 9: Make.com Fast Track (No-Code Option)
Video Title: Build the Same System Without Writing Code
Script: "If you don’t know Python, don’t worry. This module shows how to use Make.com to scrape Reddit, rewrite content, push posts to Circle, and log engagement. Great for testing before you commit to a full custom stack."

💻 Module 10: Server & Infrastructure Strategy
Video Title: VPS vs Make.com – The Infrastructure Gameplan
Script: "Should you use Make.com or build on your own server? We’ll compare cost, performance, and scalability. You’ll learn how to use OVH VPS + Docker to host all your scripts with full control — perfect for scaling to 1,000+ avatars."

📁 Module 11: Folder Structure + File Templates
Video Title: Organizing Your Automation Like a Pro
Script: "A cluttered project will break. This module walks through your Google Drive structure, where to keep your CSVs, JSON files, logs, scripts, and how to stay organized as you expand."

📚 Module 12: Glossary + Support Systems
Video Title: Tech Vocabulary, FAQs, and Community Help
Script: "What’s an LLM? CRON? Docker? We’ll review all the terminology and support tools you need to succeed — and give you resources to stay sharp and scalable as the AI world evolves."

🔥 Bonus Module: Upsell Offers + Trello Template
Video Title: Trello Board + How to Get the Full System
Script: "Want the full Trello board, SOPs, and prompt packs? In this module, we’ll give away the board and show how to access the training community or license the entire system as a client service."

Let me know if you want:
A full Notion learning hub for this

A Canva slide deck per module

AI narrator video exports

Integration with Thinkific, Kajabi, or Gumroad












✅ APPENDIX A: Video Launch Blueprint – Storyboard Scripting
This section provides a visual storytelling outline you can use to script or animate your course intro, lead magnet video, or platform launch teaser.

🎬 Scene-by-Scene Outline:
Slide 1 – Title Page
"How to Build an AI-Driven Community That Feels Alive (Even With Zero Real Users)"
Slide 2 – Problem Setup
“You launch a community. Nobody posts. Nobody comments. Nobody joins.”
Slide 3 – Enter the Avatar Engine
“What if 1,000 digital people could show up and make it feel active from Day One?”
Slide 4 – System Map
Reddit → GPT Rewrite → Avatar Commenting → Circle.so Thread → SEO → Real Users Join
Slide 5 – Automation Sequence
Daily loop: scrape → rewrite → post → like → comment → Q&A reply
Slide 6 – Results and Proof
“200–1,050 likes/day”
“8–15% of posts receive multiple layered comments”
“Real users return 3x more frequently to engaged threads”
Slide 7 – Invite CTA
“Want the system? Get the free Trello board. Want the full course? Hit enroll.”

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1uKkbr-xbYzRB_vA_PhQ33zJrkfWJ_XC-KqjxxndsRAk/edit?usp=drivesdk"
drive_file_id: "1uKkbr-xbYzRB_vA_PhQ33zJrkfWJ_XC-KqjxxndsRAk"
created: "2025-04-21T14:23:49.133Z"
modified: "2026-06-04T15:56:23.347Z"
---

# 🎓 COURSE BUILDOUT: “Automated AI Community System: From Zero to Circle Empire”

🎓 COURSE BUILDOUT: “Automated AI Community System: From Zero to Circle Empire”
Each section of your SOP becomes a course module. You’ll get:
* 🎥 Video script outlines (you record or AI avatar can narrate)

* 📝 Slide deck templates (branded with your visuals)

* ✅ Interactive checklists or Notion worksheets

* 🔗 Trello Board + Google Drive folder templates

* 🛠️ Option to embed code snippets and GPT prompt packs

________________


🧭 Recommended Course Structure:
Module
	Title
	What It Teaches
	1
	Intro: What You’re Building
	The big vision: a fully automated, AI-driven Circle community
	2
	Getting Started (Tech Stack + Setup)
	Choosing Python vs Make.com + setting up Google Drive
	3
	Circle.so Setup + Keyword Mapping
	Creating Spaces and defining intent with keyword triggers
	4
	Avatar Creation & Personalities
	Designing 1,000 avatars, with images, tones, bios, CSVs
	5
	Reddit Scraping + GPT Rewriting
	How to fetch, filter, and rewrite posts for your niche
	6
	Posting to Circle + Scheduling
	CRON, API usage, and content flow logic
	7
	Engagement Engine
	Likes, comments, Q&A, randomness — realism simulation
	8
	Scaling + Monetization
	Local vs niche replication, monetizing Spaces and personas
	9
	Make.com Visual Automation (Fast Track)
	Non-coders: replicate logic using drag-and-drop tools
	10
	Infrastructure + Cost Strategy
	VPS vs Make.com: scale smart, cut waste, Docker deploys
	11
	File Structure + Templates
	Walkthrough of folders, scripts, .env, logging, and more
	12
	Glossary + Support Tools
	LLMs, APIs, scripts, and vocabulary to sound like a pro
	BONUS
	Course Assets + Upsells
	Trello board, swipe files, GPT prompt bundles, Notion DB
	________________


✨ Delivery Options:
   * 🎥 Course Outline + Scripts: You narrate, or I help you generate an AI avatar video per module

   * 📊 Canva or Google Slides Decks: One deck per module, styled for your brand

   * 🧠 Notion-based Learning Hub: Includes checklist, embed tools, glossary, templates

   * 📂 Full Google Drive Template Folder: Plug-and-play assets to give away or license

   * 📈 Add Monetization Training: How to sell this system as a service or digital product

________________


📌 Next Step: Pick Your Format
How would you like me to start?
      1. ✅ Build the full course outline with video scripts (by module)?

      2. ✅ Start with Module 1 as a complete example (video script + slide deck)?

      3. ✅ Organize the whole course in Notion or Google Drive for student handoff?



🎓 Course Title: Automated AI Community System – From Zero to Circle Empire
🎯 Course Objective:
Help students (marketers, developers, creators) build fully automated, AI-powered online communities on Circle.so — powered by GPT, automated engagement, scalable persona systems, and server-side infrastructure.
________________


🧭 Module 1: Introduction – What You’re Building
Video Title: Welcome to the AI-Powered Community Blueprint
Script: "Welcome to the future of online engagement. In this course, you’ll learn how to build a completely automated, AI-driven community using Circle.so — powered by 1,000 simulated human avatars, automated GPT commentary, and scalable backend logic. Whether you’re a coach, consultant, or digital creator, this course will give you the blueprint to build a brand, attract attention, and scale engagement — even without an audience."
________________


🔧 Module 2: Getting Started – Tech Stack + File Setup
Video Title: Pick Your Tools: Python vs Make + Setting Up Folders
Script: "Before we dive in, let’s get your system organized. You’ll choose between a no-code route (Make.com) or the developer-friendly Python + VPS route. Then we’ll set up a clean Google Drive structure that will organize your automations, logs, avatar files, GPT prompts, and scripts so you never lose control of the system."
________________


📘 Module 3: Circle Spaces + Keyword Mapping
Video Title: Defining Your Circle Universe
Script: "Think of each Space in Circle.so like a sub-forum or topic bucket. In this module, you’ll create Spaces for each key topic your community will cover, then map keywords to those Spaces. This makes your automation engine smart enough to know where every piece of content belongs."
________________


👤 Module 4: Avatar Creation & Persona Building
Video Title: Designing Your Digital Citizens
Script: "Your community doesn’t run on bots — it runs on believable digital people. In this module, you’ll create 1,000 personas, complete with names, tones, quirks, writing styles, and even profile photos. These avatars will like, comment, and post like real humans — driving engagement and credibility."
________________


🔁 Module 5: Reddit Scraping + GPT Rewriting
Video Title: Harvesting Content & Making It Original
Script: "Where do you get content that feels fresh and relevant? Reddit. You’ll learn how to scrape the most active subreddits, filter for top posts, and use GPT to rewrite them in your avatar’s voice — so it sounds real, helpful, and original."
________________


🚀 Module 6: Posting to Circle + Automation Engine
Video Title: Launching Posts Into Your Community
Script: "This is where the magic happens. You’ll take your GPT content and push it to Circle using their API. We’ll walk you through CRON jobs, delays, randomized timing, and queue logic that makes your community feel active and alive around the clock."
________________


💬 Module 7: Engagement Engine – Comments, Likes & Q&A
Video Title: Making Your Avatars Feel Human
Script: "Your avatars won’t just post — they’ll comment, like, and reply. In this module, you’ll set up your Engagement Engine to simulate human-like timing, moods, silence days, and even GPT-powered answers to real user questions."
________________


📈 Module 8: Scaling + Monetization
Video Title: Replicating & Monetizing Your Empire
Script: "Once one community is built, you can clone it into dozens. In this module, we’ll show you how to scale into new cities, niches, or languages — and how to monetize your community through affiliate offers, training, white-label builds, or SaaS licensing."
________________


⚡ Module 9: Make.com Fast Track (No-Code Option)
Video Title: Build the Same System Without Writing Code
Script: "If you don’t know Python, don’t worry. This module shows how to use Make.com to scrape Reddit, rewrite content, push posts to Circle, and log engagement. Great for testing before you commit to a full custom stack."
________________


💻 Module 10: Server & Infrastructure Strategy
Video Title: VPS vs Make.com – The Infrastructure Gameplan
Script: "Should you use Make.com or build on your own server? We’ll compare cost, performance, and scalability. You’ll learn how to use OVH VPS + Docker to host all your scripts with full control — perfect for scaling to 1,000+ avatars."
________________


📁 Module 11: Folder Structure + File Templates
Video Title: Organizing Your Automation Like a Pro
Script: "A cluttered project will break. This module walks through your Google Drive structure, where to keep your CSVs, JSON files, logs, scripts, and how to stay organized as you expand."
________________


📚 Module 12: Glossary + Support Systems
Video Title: Tech Vocabulary, FAQs, and Community Help
Script: "What’s an LLM? CRON? Docker? We’ll review all the terminology and support tools you need to succeed — and give you resources to stay sharp and scalable as the AI world evolves."
________________


🔥 Bonus Module: Upsell Offers + Trello Template
Video Title: Trello Board + How to Get the Full System
Script: "Want the full Trello board, SOPs, and prompt packs? In this module, we’ll give away the board and show how to access the training community or license the entire system as a client service."
________________


Let me know if you want:
         * A full Notion learning hub for this

         * A Canva slide deck per module

         * AI narrator video exports

         * Integration with Thinkific, Kajabi, or Gumroad























✅ APPENDIX A: Video Launch Blueprint – Storyboard Scripting
This section provides a visual storytelling outline you can use to script or animate your course intro, lead magnet video, or platform launch teaser.
________________


🎬 Scene-by-Scene Outline:
Slide 1 – Title Page
"How to Build an AI-Driven Community That Feels Alive (Even With Zero Real Users)"
Slide 2 – Problem Setup
“You launch a community. Nobody posts. Nobody comments. Nobody joins.”
Slide 3 – Enter the Avatar Engine
“What if 1,000 digital people could show up and make it feel active from Day One?”
Slide 4 – System Map
            * Reddit → GPT Rewrite → Avatar Commenting → Circle.so Thread → SEO → Real Users Join
Slide 5 – Automation Sequence
            * Daily loop: scrape → rewrite → post → like → comment → Q&A reply
Slide 6 – Results and Proof
            * “200–1,050 likes/day”
            * “8–15% of posts receive multiple layered comments”
            * “Real users return 3x more frequently to engaged threads”
Slide 7 – Invite CTA
“Want the system? Get the free Trello board. Want the full course? Hit enroll.”
________________

Define the community assistance roles and progress handoffs

Outline

1. Separate governance from specialist assistance.
2. Map welcome, topic support and navigation.
3. Distinguish progress evidence from an automatic award.

Teach the role structure

The assigned Circle Community Intelligence Layer document is a short architecture note. It names a Community Governor who oversees avatar assistants, then presents Node Specialists → Buoy Specialists → Welcome/Dock. Preserve these names as source terminology. The arrows identify a proposed relationship, but the source does not explain whether they mean escalation, a reporting hierarchy or the order a member should encounter the roles. Do not invent that meaning or treat the note as an installed system.

An authored way to make this proposal reviewable is to describe the member's question first. Identify the responsible human governor, the scope of each specialist and where a new arrival finds help. A welcome role could explain navigation; a topic specialist could direct a learner to assigned resources; a governor could resolve uncertain routing or a disputed assessment. These are proposed applications, not definitions recovered from the source.

Answer within scope and route to the right entry point

The note assigns three activities to assistants: engage members, answer within scope and route them to the correct Sonar entry points. Define what an assistant is allowed to answer, which approved sources it uses and what it does when the answer is absent. A friendly tone cannot substitute for source support. Mark an assistant as automated so learners can distinguish its output from a human instructor's judgment.

Sonar is a named destination in the source, but no actual entry-point list or URLs are supplied. Record the intended lesson or resource, verify its destination and give the member a clickable route when that information is available. Do not create a plausible-looking link for an undefined destination. Keep unresolved questions available for human follow-up.

Connect progress gates to evidence

The source describes progress awards as Punch Card → Boat Boarding Award. It does not supply criteria, assessment questions, point values or a rule authorizing automatic awards. Before implementing such a gate, identify the required work product, evidence, reviewer and correction path. Attendance or a bot reply alone does not prove that the learner has met a skill requirement.

This supports the continuity and community themes in RISER's Brunson and Hormozi teaching: make the next step clear and deliver useful progress toward the promised outcome. The names in this note are RISER source concepts, not attributed frameworks from those educators. The measure of success is whether a member reaches appropriate help and completes meaningful work, not the number of simulated interactions.

Exercise and completion check

Write a role-and-handoff map containing the Community Governor, Node Specialists, Buoy Specialists, Welcome/Dock, Sonar destinations, Punch Card and Boat Boarding Award. Mark the source-defined responsibilities and the decisions still needed. Add one authored example of an in-scope answer, one unresolved question and one progress decision requiring evidence. The exercise specifies a design; it does not activate assistants or award progress.

Assigned source

D0350: Circle — Community Intelligence Layer. The complete short note belongs in the appendix. Detailed role definitions, routing destinations and award rubrics remain missing from this source.

Assigned source links

D0350 original source 1

Circle — Community Intelligence Layer™ (v1.0)
Circle — Community Intelligence Layer™
Community Governor oversees avatar assistants.
Avatars are Node Specialists → Buoy Specialists → Welcome/Dock.
They engage, answer within scope, route members to the correct Sonar entry points, and award progress gates (Punch Card → Boat Boarding Award).

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1Eu-YE2xgJ92hoXsXG64fBiEf26bGXRxDBAlbjl3rnzs/edit?usp=drivesdk"
drive_file_id: "1Eu-YE2xgJ92hoXsXG64fBiEf26bGXRxDBAlbjl3rnzs"
created: "2025-12-19T20:10:45.173Z"
modified: "2026-06-04T15:53:44.985Z"
---

# Circle — Community Intelligence Layer™ (v1.0)

Circle — Community Intelligence Layer™ (v1.0)
Circle — Community Intelligence Layer™
Community Governor oversees avatar assistants.
Avatars are Node Specialists → Buoy Specialists → Welcome/Dock.
They engage, answer within scope, route members to the correct Sonar entry points, and award progress gates (Punch Card → Boat Boarding Award).

Turn the operator identity into observable working habits

Outline

1. Understand the source's identity-before-skill proposition.
2. Translate it into accountable decisions and work products.
3. Identify the three referenced exercises that are not supplied.

Read the source in its original context

This excerpt belongs to the legacy Harbor Orientation and Riser Manifesto course. It labels that course Pre-Stage, Learn, with no prerequisite and six to eight hours over one week, repeating the metadata twice. These are parent-course estimates, not the duration of this short lesson or a replacement for the current twelve-course map.

The source asks learners to shift from an employee or hobbyist identity toward an operator identity before focusing on tactics. Its claims that career-pivoters will fail without that shift and that identity determines results are coaching propositions, not evidence that employees or hobbyists inevitably fail. Skill, resources, circumstances and practice also affect outcomes. Do not use the lesson to judge a person's worth or diagnose their motives.

Make the identity practical

An authored application is to define operator behavior as taking responsibility for a clear outcome, choosing the next useful action, keeping evidence of what happened and revising the plan when the evidence changes. Compare that with waiting for an undefined task or collecting tactics without producing a work product. The comparison describes behaviors that anyone can practice; it does not divide people into fixed categories.

For one current project, write the outcome, the decision you own, the action you can complete and the evidence you will review. If a constraint prevents the action, name it and decide what support or change is needed. A commitment to building includes honest recognition of limits.

The source attributes “you are the market you become” to Kennedy. That wording has not been verified against a primary source. Preserve it as the excerpt's attribution rather than treating it as an authenticated quotation or a rule that personal identity proves market demand.

Preserve the three missing exercise references

The excerpt instructs learners to take a ten-question Identity Audit, complete a Who Do I Need to Become worksheet and read the Defer-Without-Shame doctrine. It does not provide the ten questions, worksheet fields or doctrine text. Keep all three references in the lesson and mark their contents unavailable. Do not invent ten questions and call them the recovered audit.

A short reflective exercise can still be useful if it is labeled as authored guidance: identify one habit to practice, one decision to own and one task that needs a clear defer-or-proceed decision. This does not replace the missing source exercises or establish that a formal gate has been passed.

Connect identity to the marketing work

Within RISER's Brunson and Hormozi themes, this lesson supports the habits needed to understand a customer, develop an offer and test a claim. Confidence in an identity is not customer evidence. Use the operator commitment to carry out the research and delivery work that makes the message credible.

Completion check and source

Submit the outcome, owned decision, next action and review evidence for one project. List the three missing source resources so they remain visible in the curriculum audit. D0352: Identity Before Skill. The full excerpt belongs in the appendix; this lesson teaches its available proposition without claiming the missing exercises are complete.

Assigned source links

D0352 original source 1

M1.3 — IDENTITY BEFORE SKILL
============================================================

Source: Riser Nation Academy 2026 Syllabus

NOTE: This document is an excerpt copied from the master syllabus.
The master syllabus remains intact and unmodified.

---

PARENT COURSE: C1 — Harbor Orientation & The Riser Manifesto
---
Stage: Pre-Stage  ·  Phase: Learn  ·  Prereq: None — entry course  ·  Time: 6–8 hours over 1 week

Stage: Pre-Stage  ·  Phase: Learn  ·  Prereq: None — entry course  ·  Time: 6–8 hours over 1 week
In Plain Words
This is the first course. You will not learn marketing tricks here. You will figure out who you have to become to make the rest of the Academy work. Riser Nation's idea is simple: who you are determines what you can do. We fix who you are first.
The Mismatch This Course Fixes
Most students arrive looking for tactics. They will fail unless they first take on the operator identity.
Modules

---

M1.3 — IDENTITY BEFORE SKILL
---

Why career-pivoters fail. The shift from employee or hobbyist to operator. Kennedy: 'you are the market you become.'
In plain words: If you act like an employee, you'll get employee results. The shift comes first; the skills follow.
Take the 10-question Identity Audit.
Complete the 'Who do I need to become?' worksheet.
Read the Defer-Without-Shame doctrine.

---
END OF M1.3
---

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1s9B9hloD5JAdIcG-WqJqeJ7lO7M_oCeod1rQYD8o094/edit?usp=drivesdk"
drive_file_id: "1s9B9hloD5JAdIcG-WqJqeJ7lO7M_oCeod1rQYD8o094"
created: "2026-05-11T23:27:58.127Z"
modified: "2026-06-04T17:48:57.156Z"
---

# M1.3 - IDENTITY BEFORE SKILL

M1.3 — IDENTITY BEFORE SKILL
============================================================


Source: Riser Nation Academy 2026 Syllabus


NOTE: This document is an excerpt copied from the master syllabus.
The master syllabus remains intact and unmodified.


---


PARENT COURSE: C1 — Harbor Orientation & The Riser Manifesto
---
Stage: Pre-Stage  ·  Phase: Learn  ·  Prereq: None — entry course  ·  Time: 6–8 hours over 1 week


Stage: Pre-Stage  ·  Phase: Learn  ·  Prereq: None — entry course  ·  Time: 6–8 hours over 1 week
In Plain Words
This is the first course. You will not learn marketing tricks here. You will figure out who you have to become to make the rest of the Academy work. Riser Nation's idea is simple: who you are determines what you can do. We fix who you are first.
The Mismatch This Course Fixes
Most students arrive looking for tactics. They will fail unless they first take on the operator identity.
Modules


---


M1.3 — IDENTITY BEFORE SKILL
---


Why career-pivoters fail. The shift from employee or hobbyist to operator. Kennedy: 'you are the market you become.'
In plain words: If you act like an employee, you'll get employee results. The shift comes first; the skills follow.
Take the 10-question Identity Audit.
Complete the 'Who do I need to become?' worksheet.
Read the Defer-Without-Shame doctrine.


---
END OF M1.3
---

D0393 — Follow the Harbor Orientation prerequisite chain

Curriculum outline

1. Read the eight-module sequence and its pass/fail loops.
2. Understand why each artifact precedes the next.
3. Reconcile the time estimates and incomplete graduation inventory.
4. Preserve the diagram's meaning in accessible text.

Lesson script

This is the legacy C1 Harbor Orientation map, not a replacement for the current twelve-course assignment spreadsheet. It describes eight modules completed in order. At every checkpoint, passing leads to the next module; failing leads back to the same module for correction. The map presents a learning sequence. It does not establish that automated unlocks or checks are already configured.

M1.1, Welcome to the Harbor, has a 60-minute estimate. Analyze your current position. The checkpoint asks whether your position is identified. The map calls this the entry point with no preceding module. The separately assigned written lesson adds enrollment requirements; that is a source distinction to resolve when configuring access, rather than silently deleting either condition.

M1.2, Signing the Captain's Oath, has a 90-minute estimate. Create, sign and file the artifact only after identifying your position. The source's reasoning is that a commitment to change should start from a known baseline. The checkpoint asks whether the oath is signed and filed. This lesson explains that requirement; it does not sign an oath for you or supply the oath's full text.

M1.3, Operator Identity Statement, has a 120-minute estimate. Create a 200–300-word statement and obtain peer review. It follows the oath because the identity statement draws on that commitment. The map references oath clause 3, while the written identity lesson references clause 2. Preserve that disagreement until checked against the actual oath. The checkpoint requires the statement to be written and peer-reviewed.

M1.4, The 6 Percent Rule Commitment, has a 75-minute estimate. Apply the named rule through three personal examples, then file the commitment and examples. This follows the identity statement so the examples express your stated operating identity. The map names the rule but does not define what its six percent measures; the title alone cannot supply the missing rule.

M1.5, The 85-Minute Weekly Rhythm, has a 60-minute estimate. Schedule four weeks and file the calendar artifact. The source links the rhythm to enforcing the prior commitment. Its title specifies an 85-minute rhythm, but this map does not break that rhythm into activities. Do not confuse the module's 60-minute study estimate with the duration of the weekly operating routine.

M1.6, The Six-Stage Voyage Map, has a 90-minute estimate. Analyze and annotate the stages, referring to your scheduled rhythm. The checkpoint asks whether the map is annotated. The source says six stages; the related Harbor written lesson enumerates stages 0 through 6, which is seven positions. The original naming is retained and the count conflict is explicit. This map does not resolve it.

M1.7, Graduation Gates, has a 45-minute estimate. Explain how the gates work using the annotated Voyage Map as context. The checkpoint checks that explanation. A gate is useful when the student understands the evidence required and what to correct after a failed check; the source does not provide the complete gate rubric here.

M1.8, Stage 1 Commitment, has a 60-minute estimate. Create a commitment for legacy C2–C5 after understanding the gates. The final course test asks whether all six artifacts are filed. Passing completes C1 and leads to C2 Flagship Discovery; failing returns to M1.8. Eight modules and a six-artifact gate are not necessarily inconsistent, since a module may assess an explanation rather than create a new file. However, the map does not explicitly enumerate the complete six-artifact inventory, so do not invent that inventory or declare the gate passed.

The prerequisite logic is deliberate: baseline before oath; oath before identity; identity before personal examples; commitment before scheduling; schedule before map annotation; annotation before gate explanation; gate understanding before the next commitment. The source requires serial study rather than parallel module work. Preserve that educational relationship even when the documents appear in multiple current lesson assignments.

Time estimates and source limits

Adding the eight module estimates gives 600 minutes, or ten hours. The narrative recommends one module a day for eight calendar days at about two and a half focused hours daily, which is twenty hours. Its compressed weekend is also twenty hours, at ten hours per day. Those totals may cover different activities, but the source does not explain the difference. Report both rather than replacing them with a single supposedly precise duration.

The source discourages the intensive weekend and attributes a measurable retention drop to cognitive load theory, naming Sweller 1988 and a 2019 update. It supplies no measurement of this particular course or comparison of these schedules. Treat that as a stated design rationale, not verified evidence of a specific retention effect.

The original Mermaid diagram uses blue start/end nodes (#2E75B6) with white borders and text, and light-blue module nodes (#D9E2F3) with blue borders. Its full code and written alternative description are retained in the source appendix. The document claims a corresponding C1-Module-Map.png and WCAG 2.1 compliance. The named PNG was not found in the exact-name Drive search, and a statement about alt text does not itself verify the rendered page's accessibility. The complete sequence and all return loops are explained in this lesson so the relationships are available in text.

As an authored exercise, make a progress record with each module, its prerequisite, expected evidence and current status. Leave missing rule definitions, the oath-clause conflict and the final inventory unresolved rather than filling them from memory. Brunson-style progression can make the learning journey understandable; Hormozi's emphasis on reducing effort and delay can motivate clear instructions. Neither justifies removing a required learning dependency or promising the source's unverified timeline.

Sources and resources

- Assigned C1 module map: full Mermaid diagram, sequence, estimates and original alternative text. - Assigned Harbor written lesson: related baseline and stage descriptions, including conflicting counts. - Assigned identity written lesson: related identity process and different oath-clause reference. - ClickFunnels attractive character guide: supporting story reference. - Acquisition.com pricing and value checklist: supporting value reference.

Assigned source links

D0393 original source 1

# C1 Harbor Orientation — Module Map

## Flow Diagram (Mermaid)

```mermaid
graph TD
    START([Student enters C1]) --> M11[M1.1 Welcome to the Harbor<br/>Analyze current position<br/>60 min]
    M11 --> CP11{Checkpoint 1.1<br/>Position identified?}
    CP11 -->|Pass| M12[M1.2 Signing the Captain's Oath<br/>Create the signed artifact<br/>90 min]
    CP11 -->|Fail| M11
    
    M12 --> CP12{Checkpoint 1.2<br/>Oath signed & filed?}
    CP12 -->|Pass| M13[M1.3 Operator Identity Statement<br/>Create 200-300 word statement<br/>120 min]
    CP12 -->|Fail| M12
    
    M13 --> CP13{Checkpoint 1.3<br/>Statement written & peer-reviewed?}
    CP13 -->|Pass| M14[M1.4 The 6 Percent Rule Commitment<br/>Apply rule with 3 personal examples<br/>75 min]
    CP13 -->|Fail| M13
    
    M14 --> CP14{Checkpoint 1.4<br/>Commitment + 3 examples filed?}
    CP14 -->|Pass| M15[M1.5 The 85-Minute Weekly Rhythm<br/>Apply by scheduling 4 weeks<br/>60 min]
    CP14 -->|Fail| M14
    
    M15 --> CP15{Checkpoint 1.5<br/>Calendar file filed?}
    CP15 -->|Pass| M16[M1.6 The Six-Stage Voyage Map<br/>Analyze & annotate all 6 stages<br/>90 min]
    CP15 -->|Fail| M15
    
    M16 --> CP16{Checkpoint 1.6<br/>Voyage Map annotated?}
    CP16 -->|Pass| M17[M1.7 Graduation Gates<br/>Understand how gates work<br/>45 min]
    CP16 -->|Fail| M16
    
    M17 --> CP17{Checkpoint 1.7<br/>Gate logic explained correctly?}
    CP17 -->|Pass| M18[M1.8 Stage 1 Commitment<br/>Create commitment for C2-C5<br/>60 min]
    CP17 -->|Fail| M17
    
    M18 --> CP18{Course Completion Test<br/>All 6 artifacts filed?}
    CP18 -->|Pass| DONE([C1 Complete<br/>C2 Flagship Discovery unlocked])
    CP18 -->|Fail| M18
    
    style START fill:#2E75B6,stroke:#fff,color:#fff
    style DONE fill:#2E75B6,stroke:#fff,color:#fff
    style M11 fill:#D9E2F3,stroke:#2E75B6
    style M12 fill:#D9E2F3,stroke:#2E75B6
    style M13 fill:#D9E2F3,stroke:#2E75B6
    style M14 fill:#D9E2F3,stroke:#2E75B6
    style M15 fill:#D9E2F3,stroke:#2E75B6
    style M16 fill:#D9E2F3,stroke:#2E75B6
    style M17 fill:#D9E2F3,stroke:#2E75B6
    style M18 fill:#D9E2F3,stroke:#2E75B6
```

## Prerequisite Chain (explicit)

- **M1.1** requires nothing (entry point)
- **M1.2** requires M1.1 Checkpoint pass (student must know their current position before they can sign an oath to change it)
- **M1.3** requires M1.2 pass (the Oath's clause 3 is referenced in the Identity Statement — cannot write the statement without the oath)
- **M1.4** requires M1.3 pass (personal examples must be filtered through stated identity, not generic)
- **M1.5** requires M1.4 pass (rhythm enforces the 6% rule — cannot schedule without committing to the rule first)
- **M1.6** requires M1.5 pass (annotations reference the student's scheduled rhythm)
- **M1.7** requires M1.6 pass (gate logic references the Voyage Map annotations)
- **M1.8** requires M1.7 pass (commitment references understood gate logic)

This is strict serial sequencing by design. Most courses allow parallel module work; C1 does not. The identity-forming artifacts depend on each other in order.

## Estimated Sequential Time

If completed on the recommended 1-module-per-day cadence: 8 calendar days, ~2.5 hours of focused work per day (video + study + deliverable).

If compressed to a weekend intensive: 2 days at 10 hours each. Not recommended — retention drops measurably due to cognitive load saturation (Sweller 1988 CLT + 2019 update).

## Visual Rendering for Accessibility

This Mermaid diagram is rendered as a PNG (`C1-Module-Map.png`) with alt-text describing the flow, stored in the same folder. Screen readers receive the PNG alt-text, which describes each module and its prerequisite relationship verbally. This satisfies WCAG 2.1 §1.1.1 Non-text Content (Level A) and §1.3.1 Info and Relationships (Level A).

Alt-text for PNG: *"Flowchart showing C1 Harbor Orientation's 8 modules in sequential order. Student enters at M1.1 Welcome to the Harbor, must pass Checkpoint 1.1, then proceeds through M1.2 Captain's Oath, M1.3 Operator Identity Statement, M1.4 6 Percent Rule, M1.5 85-Minute Rhythm, M1.6 Voyage Map, M1.7 Graduation Gates, and M1.8 Stage 1 Commitment. Each module has a checkpoint that must pass before advancing. Failed checkpoints loop back to the same module. Upon passing M1.8 and the full Course Completion Test, the student completes C1 and unlocks C2 Flagship Discovery."*

# C1 Harbor Orientation — Module Map

## Flow Diagram (Mermaid)

```mermaid
graph TD
    START([Student enters C1]) --> M11[M1.1 Welcome to the Harbor<br/>Analyze current position<br/>60 min]
    M11 --> CP11{Checkpoint 1.1<br/>Position identified?}
    CP11 -->|Pass| M12[M1.2 Signing the Captain's Oath<br/>Create the signed artifact<br/>90 min]
    CP11 -->|Fail| M11
    
    M12 --> CP12{Checkpoint 1.2<br/>Oath signed & filed?}
    CP12 -->|Pass| M13[M1.3 Operator Identity Statement<br/>Create 200-300 word statement<br/>120 min]
    CP12 -->|Fail| M12
    
    M13 --> CP13{Checkpoint 1.3<br/>Statement written & peer-reviewed?}
    CP13 -->|Pass| M14[M1.4 The 6 Percent Rule Commitment<br/>Apply rule with 3 personal examples<br/>75 min]
    CP13 -->|Fail| M13
    
    M14 --> CP14{Checkpoint 1.4<br/>Commitment + 3 examples filed?}
    CP14 -->|Pass| M15[M1.5 The 85-Minute Weekly Rhythm<br/>Apply by scheduling 4 weeks<br/>60 min]
    CP14 -->|Fail| M14
    
    M15 --> CP15{Checkpoint 1.5<br/>Calendar file filed?}
    CP15 -->|Pass| M16[M1.6 The Six-Stage Voyage Map<br/>Analyze & annotate all 6 stages<br/>90 min]
    CP15 -->|Fail| M15
    
    M16 --> CP16{Checkpoint 1.6<br/>Voyage Map annotated?}
    CP16 -->|Pass| M17[M1.7 Graduation Gates<br/>Understand how gates work<br/>45 min]
    CP16 -->|Fail| M16
    
    M17 --> CP17{Checkpoint 1.7<br/>Gate logic explained correctly?}
    CP17 -->|Pass| M18[M1.8 Stage 1 Commitment<br/>Create commitment for C2-C5<br/>60 min]
    CP17 -->|Fail| M17
    
    M18 --> CP18{Course Completion Test<br/>All 6 artifacts filed?}
    CP18 -->|Pass| DONE([C1 Complete<br/>C2 Flagship Discovery unlocked])
    CP18 -->|Fail| M18
    
    style START fill:#2E75B6,stroke:#fff,color:#fff
    style DONE fill:#2E75B6,stroke:#fff,color:#fff
    style M11 fill:#D9E2F3,stroke:#2E75B6
    style M12 fill:#D9E2F3,stroke:#2E75B6
    style M13 fill:#D9E2F3,stroke:#2E75B6
    style M14 fill:#D9E2F3,stroke:#2E75B6
    style M15 fill:#D9E2F3,stroke:#2E75B6
    style M16 fill:#D9E2F3,stroke:#2E75B6
    style M17 fill:#D9E2F3,stroke:#2E75B6
    style M18 fill:#D9E2F3,stroke:#2E75B6
```

## Prerequisite Chain (explicit)

- **M1.1** requires nothing (entry point)
- **M1.2** requires M1.1 Checkpoint pass (student must know their current position before they can sign an oath to change it)
- **M1.3** requires M1.2 pass (the Oath's clause 3 is referenced in the Identity Statement — cannot write the statement without the oath)
- **M1.4** requires M1.3 pass (personal examples must be filtered through stated identity, not generic)
- **M1.5** requires M1.4 pass (rhythm enforces the 6% rule — cannot schedule without committing to the rule first)
- **M1.6** requires M1.5 pass (annotations reference the student's scheduled rhythm)
- **M1.7** requires M1.6 pass (gate logic references the Voyage Map annotations)
- **M1.8** requires M1.7 pass (commitment references understood gate logic)

This is strict serial sequencing by design. Most courses allow parallel module work; C1 does not. The identity-forming artifacts depend on each other in order.

## Estimated Sequential Time

If completed on the recommended 1-module-per-day cadence: 8 calendar days, ~2.5 hours of focused work per day (video + study + deliverable).

If compressed to a weekend intensive: 2 days at 10 hours each. Not recommended — retention drops measurably due to cognitive load saturation (Sweller 1988 CLT + 2019 update).

## Visual Rendering for Accessibility

This Mermaid diagram is rendered as a PNG (`C1-Module-Map.png`) with alt-text describing the flow, stored in the same folder. Screen readers receive the PNG alt-text, which describes each module and its prerequisite relationship verbally. This satisfies WCAG 2.1 §1.1.1 Non-text Content (Level A) and §1.3.1 Info and Relationships (Level A).

Alt-text for PNG: *"Flowchart showing C1 Harbor Orientation's 8 modules in sequential order. Student enters at M1.1 Welcome to the Harbor, must pass Checkpoint 1.1, then proceeds through M1.2 Captain's Oath, M1.3 Operator Identity Statement, M1.4 6 Percent Rule, M1.5 85-Minute Rhythm, M1.6 Voyage Map, M1.7 Graduation Gates, and M1.8 Stage 1 Commitment. Each module has a checkpoint that must pass before advancing. Failed checkpoints loop back to the same module. Upon passing M1.8 and the full Course Completion Test, the student completes C1 and unlocks C2 Flagship Discovery."*

Pricing architecture and operating sustainability

Source review: D3946–D3949, four assigned pricing images, unnamed (84).png through unnamed (87).png. Assigned lesson: 11.2. These images add an operating test to the community promise: continuing value must be deliverable at a sustainable price.

Outline

1. Compare estimated delivery cost with measured delivery cost.
2. Calculate the effect of capacity on compensation and margin.
3. Choose a pricing response after a cooling period.
4. Select a pricing structure that matches the delivery mechanism.
5. Specify the base price, payment terms, and segmentation rules.

Test the promise against the operating numbers

Before asking a member to renew, check whether the promise works for the member and for the operator. A membership with enthusiastic customers can still fail if its delivery commitments consume more time than the price supports. The two price–cost reality-check images ask you to compare the original estimate with measured delivery cost. Include preparation, delivery, support, administration, follow-up, and other obligations that the offer actually creates. Keep your definition consistent so that the comparison is meaningful.

The images describe a possible thirty-to-sixty-percent gap between estimated and actual performance. Treat this as a source warning to investigate, not as a measured fact about your business. Use your own time and cost records. State whether a reported gap concerns hours, costs, or compensation; those quantities are not interchangeable.

Inspect three related measures. First, compare the effective hourly return with the minimum sustainable hourly return you established for the business. The graphic shows a 1.25-times hourly-rate gap, but it does not provide enough underlying calculations to reproduce that result. Write down the numerator, denominator, and costs included in your own comparison. Second, compare the realized margin with your chosen target. The source illustrates a forty-five-percent margin against a sixty-percent knowledge-service target and, in one version, a seventy-percent product target. Those targets are exercise assumptions, not universal standards. Third, calculate the annual compensation surrendered when the current economics fall below your intended compensation at the workload you can actually sustain.

One image illustrates seventy-five thousand dollars of annual surrender; the other illustrates one hundred fifty thousand dollars. These are different examples, not a single reconciled result. Do not copy either number into your plan. Show the time period, realistic customer volume, costs, and compensation assumptions behind your own calculation. If you compare two scenarios, keep the accounting basis and period the same.

Now apply the capacity ceiling. Multiply the customer volume you can responsibly support by the current price, then compare that scenario with the proposed price and delivery scope. More sales cannot repair a compensation gap if serving those sales requires hours you do not have. Discuss sustainability as both a cash question and a workload question: how long can the present arrangement continue before available cash or operator capacity is exhausted? The source supplies no universal formula for burnout or a precise safe horizon, so use observable workload and cash assumptions rather than inventing a predictive score.

Choose a response deliberately

The images name four responses: raise prices, narrow scope, discontinue the offer, or temporarily retain a legacy arrangement while moving toward a sustainable model. One version specifically proposes higher prices for new customers; another describes a legacy sunset. In a community, narrowing scope might mean specifying support hours and the number of live sessions, with a clear explanation of the resulting experience. A temporary legacy arrangement needs an explicit review date and a feasible service commitment. It should not become an indefinite promise that the business cannot fulfill.

The source exercise calls for a twenty-four-hour cooling period; its companion says at least one sleep cycle. Preserve both statements and use a full day for the exercise so neither is shortened. After reviewing the numbers, wait before finalizing the response. Then test the reasons you are using to reject a change. “I will get faster” requires a concrete process change and measured evidence. “The market will not bear more” requires evidence from appropriate buyers and a clearly specified offer. Neither statement alone changes the arithmetic.

One graphic refers to five defense tests but does not list all five. The visible material supplies examples of defensive reasoning, not a complete five-item questionnaire. Record that limitation rather than presenting invented questions as recovered source content.

Move from one price to a pricing system

The two architecture images recommend scanning at least sixteen pricing patterns and selecting one or two that fit the offer. The images do not enumerate a complete sixteen-pattern catalog. They visibly name fixed or flat fees, tiered pricing, subscriptions, performance-based arrangements, and per-individual subscription pricing. Use these as the supplied examples; do not imply that a missing catalog was present in the images.

Match the structure to the mechanism. The service operator provides substantial individual attention. The teacher can deliver knowledge through courses or cohorts. The builder creates a repeatable or productized solution. These are design lenses, not rigid identities: describe the work your particular offer requires before selecting a price format. A community subscription needs a continuing benefit and a realistic service cadence; a one-time transformation does not automatically become recurring value because it is billed monthly.

The images describe selection as roughly six percent. One selection out of sixteen is 6.25 percent; two out of sixteen is 12.5 percent. The useful instruction is to inspect alternatives and choose a small number that fit, rather than treating six percent as an exact rule for both choices.

Specify the base price using unit economics and capacity. Then state any fees and installment terms, including how delayed collection, default risk, and administrative work affect the margin. Finally, define defensible segmentation. The source contrasts an explicit early-bird rule with arbitrary negotiated discounts. State who qualifies, what they receive, and how the term is communicated. A price difference should have an intelligible rule rather than depend on whether a buyer happens to negotiate.

Read the value and access matrix carefully

The images name three regions. Q4 associates high value and narrow access with an intensive service or premium bespoke coaching. Q2 associates high value and broad access with teaching through premium products, courses, or cohorts. Q1 associates lower value and broad access with a mass-market or commodity builder model. The fourth region is not explained in the supplied images. Do not manufacture its definition.

One image has inconsistent axis labels: the words describing value and access are placed in ways that conflict with the named regions. Use the explicitly described regions above when discussing the source, and disclose the diagram issue. The graphic also calls the model a six-point architecture without supplying six separately defined points. We can teach its visible base-price, terms, segmentation, and model-fit decisions without claiming to have recovered missing definitions.

Apply the lesson

Prepare one pricing decision record for your community offer. Include measured delivery time and cost, the margin definition, sustainable capacity, the current and proposed compensation scenarios, the chosen response, the cooling-period review, the pricing format, and the terms that affect collection. Explain how the price supports the continuing member outcome. This connects the value proposition to the operator's ability to fulfill it; perceived value and a compelling offer still require honest delivery economics.

Bring the record into the lesson's existing implementation task. Keep the original spreadsheet proof gate, and identify any assumptions that still need customer or operating evidence. Completion of this image exercise does not certify the remaining sources assigned to Lesson 11.2.

Map search questions across the entire customer journey

The native one-page Search Listening worksheet has been visually inspected. It contains six stages, fourteen illustrative searches, blank response space and a minimum one-hour exercise. There are no filled customer answers, PDF form fields or embedded hyperlink annotations. Both assigned file URLs are retained. Its search-versus-social graphic indicates a change in emphasis around purchase; it does not prove any channel is exclusive to one stage.

Complete each of the six stages

Trigger asks why a purchase becomes relevant. Examine daily, weekly, monthly or yearly routines, unexpected events and peer or celebrity influence. Date-night ideas illustrates a recurring occasion; a washing-machine breakdown an unplanned need; Love Island bikinis an influence-led query. Record the actual trigger separately from the demographic profile.

Awareness asks how the person begins exploring. The source gives an advertisement identified by its song, Caroline Hirons moisturizer recommendations and recipes for fussy toddlers. These respectively illustrate remembering an ad, following a trusted person and searching from a household situation. They are historical query examples, not endorsements or evidence of current volume.

Consideration asks how alternatives are judged. Huawei versus Samsung illustrates competitor comparison; Volkswagen Beetle reliability quality; Teletext Holidays other people's experiences; and the best travel credit card a specific use case. Record the evaluation criterion and evidence needed, not just the brand name. The financial-product phrase is a search example, not a recommendation.

Conversion asks what is needed to complete the decision. Netflix student discounts illustrates eligibility and price; the best time to buy flights timing; and buying cryptocurrency with PayPal a nonstandard transaction route. Answer only with current, verified terms when producing actual buyer guidance. The worksheet itself does not establish availability, savings or suitability.

Loyalty uses Waitrose brand navigation and whether branded searches rise or fall. Brand-query changes can have many causes; compare repeat purchase, support, cancellation and customer feedback before interpreting retention. Search interest alone is not loyalty.

Advocacy is marked not applicable because the source considers it rarely search-driven. Preserve that limitation but do not infer zero advocacy. Reviews, recommendations, referral questions and sharing behavior can provide evidence. Add a relevant question or mark the research gap explicitly.

Turn the blank worksheet into a content and measurement plan

Spend at least an hour collecting actual questions. For each stage, record the question, source link, date, audience context, desired answer, proposed content and useful next action. Those columns are a proposed working extension; the original is a blank worksheet. Distinguish observed queries, estimates and your own hypotheses. A journey can loop or skip stages, and several questions can occur in one visit.

Use Brunson's hook and offer progression to keep the next step appropriate. Use Hormozi's outcome, likelihood, delay and effort to explain what helps a buyer decide, without turning every informational answer into a sales pitch. This six-stage journey is different from Schwartz's five awareness levels: map them when useful but do not rename one as the other. Submit six completed stage notes, a prioritized answer plan and evidence gaps. Clear visible answers and descriptive links help people and search systems understand the page; they do not guarantee ranking or AI citation.

Complete available assigned-document reference

The following preserves the supplied document text for critical study. Historical claims and embedded prompts are not RISER promises or instructions to execute. The linked external video is studied through the original adaptation above; its full transcript is not reproduced here.

PAGE 1 Search Listening and the Customer Journey SEARCH BEHAVIOURS What’s their daily/weekly/monthly/ yearly routine like? [Date night ideas] What unplanned events (potentially crises) might occur? [what to do when washing machine breaks] Who are they being influenced by (peers as well as ‘celebrities’)? [Love Island bikinis] What advertising might they be coming into contact with? [Advert with [x] song] Again, who are they being influenced by (peers as well as ‘celebrities’)? [Caroline Hirons moisturisers] What person-based searches are they performing to find the ‘right’ brands for them? [Recipes for fussy toddlers] Will they be performing comparison searches between you and your competitors? [Huawei vs Samsung] Are they asking about the quality/fit/performance of your products? [How reliable are VW Beetles?] Are they seeking out others’ experiences of your brand? [Are Teletext Holidays any good?] Are they focused on one element/use of your product? [Which is the best credit card for travel] Are they looking for a discount? [Netflix student discount] Are they seeking advice based on seasonality? [Best time to buy flights] Are they looking for guidance (for a non- standard transaction)? [Buying crypto with PayPal] Have searches for your brand or website increased/decreased? [Waitrose] N/A (Advocacy very rarely plays out in search behaviour) What’s going on in your audiences’ life that gets them in the purchase mindset? How might your audience become aware of brands like yours? What questions might they have around your product/service? What might they be searching for to convince them to purchase? Are they searching directly for your brand? Trigger Awareness Consideration Conversion Loyalty Advocacy Welcome to Search Listening™, we’re going to explore the insight it can uncover. This worksheet outlines a simple customer journey with some questions which you can use to get started. Spend at least an hour really considering the questions and answering them as fully and broadly as you can via search behaviour. SEARCH IS KEY SOCIAL IS KEY © Search Listening™

Clickable sources and applicable resources

ClickFunnels educational resources

Acquisition.com educational resources

Google AI search guidance

Google spam policies

Assigned document D0224, source 1

Assigned document D0224, source 2

Establish a review rhythm when the source is only a title

The supplied document contains only the heading REVIEW_RHYTHM (weekly/monthly/quarterly tool review). It supplies no checklist, rubric, thresholds or completed review. The workflow below is a proposed instructional adaptation. It must not be represented as a recovered RISER SOP.

Weekly operational review

Check whether the tools used for this week's lessons, content and follow-up worked. Record failures, broken links, access issues, incorrect outputs and time lost. Choose an owner and next action for each issue. Keep evidence such as the failed input, reviewed output or relevant ticket without exposing unnecessary personal data. A tool remaining connected does not prove that its output was correct.

Monthly value and quality review

Compare actual use, costs, completion time, acceptance rate and business outcomes with the reason the tool was adopted. Include human correction and support time. Review redundant subscriptions, obsolete sources, permission changes and whether exported files can still be opened. Classify each tool as keep, improve, pause or replace based on the evidence. A lower price is not automatically better if it requires much more correction.

Quarterly system review

Revisit the customer problem, offer, curriculum dependencies and platform fit. Confirm ownership, exportability, fallback procedures and any changes in source or usage rights. Test a representative workflow from input through human review and delivery. Retain the previous decision and evidence so changes are traceable. For community lessons, use member feedback and completion patterns to decide which support or training needs revision.

The proposed review record contains date, tool/workflow, purpose, evidence, cost, quality issue, decision, owner, due date and verification link. Do not invent quantitative pass thresholds where none are supplied. Brunson's funnel continuity directs attention to where a learner or buyer gets stuck; Hormozi's effort and delay dimensions help assess the practical improvement. Submit a first review record and proposed calendar for instructor review. The empty original remains linked, and its missing content remains an explicit source gap.

Complete available source reference

The following is source material for critical study. Historical offers, quoted promotional claims and embedded instructions are not RISER promises or directions to execute. Read the corrections above before adapting any example. Linked sources are not considered fully reviewed merely because a link appears.

REVIEW_RHYTHM (weekly/monthly/quarterly tool review)

Clickable sources and applicable resources

ClickFunnels educational resources

Acquisition.com educational resources

Google AI search guidance

Google spam policies

Assigned document D0217, source 1

Understand the proposed C3 build before claiming it works

This April 24,2026 version 2 reference describes legacy C3 infrastructure. The current spreadsheet assigns it across research, content, sales review, community and scaling lessons; it does not establish that those integrations are installed in GoHighLevel. Named paths and functions are specifications, not executable assets supplied in this document.

Map the database and progression

Harbor Master uses Supabase with row-level security. The document says seven tables but lists eight: scan plans, trigger banks, competitor scans, customer interviews, kill-criteria evaluations, pricing signals, primary selections and market-fit hypotheses, each prefixed c3_. Preserve all eight. Inputs come from c2_mechanism_hypotheses plus captains_oaths and identity_statements. Enrollment and completion checks have separate functions. Supabase RLS should restrict access by authenticated ownership and appropriate role; test another user's access as well as the happy path. Do not place privileged keys in learner-facing pages.

Curriculum Captain routes M3.1 scan plan, M3.2 trigger bank, M3.3 competitors, M3.5 kill criteria, M3.7 primary selection and M3.8 hypothesis to six named AI reviewers. M3.3 also queues two peer reviews. M3.4 interviews and M3.6 pricing use structural SQL checks. Human review follows M3.6 and receives M3.3 and M3.4; M3.7 waits for the human verdict, then M3.8 triggers completion. Structural presence is not substantive correctness. A valid JSON answer alone is not proof of good grading.

The config proposes five revisions before mentoring, 48–72 hour human review with 96 hour escalation, a $3 API cost cap per student triggering a mentor call, and peers within two weeks of completion. Its later checklist instead says C3 graduates. Resolve whether recently completed or nearly completing peers qualify before automating matching. The 3 cap's scope is also ambiguous: validator-only versus whole-student usage. Record its exact accounting scope, alert and human fallback rather than treating a cost cap as a reason to discard a submission.

Watch artifacts and support people

Drive Archivist watches the eight named artifact patterns and an Interviews folder containing date-named m4a recordings and matched transcripts. Parse actual entry counts and required fields; file size cannot prove 200 valid trigger entries. Use version/event identifiers to avoid double-grading repeated saves. Match transcript and recording explicitly and check consent before sharing. A populated peer-review heading alone does not establish two completed reviews.

Community Intelligence names five Circle channels for discussion, help, peer review, human-review status and completions. It tracks active students, average checkpoint days, students stalled beyond 14 days and queue depth. Daily Spyglass shows module, pace, interview bookings/completions, trigger count/trend, human-review status and next action. The instructor view adds the M3.1–M3.8 funnel, intervention list, reviewer load and per-student API cost. These are operational signals to investigate, not automatic judgments about motivation.

Builds 2 waitlists, 4 marketing email and 14 causal modeling are explicitly not active C3 components. Transactional course notices are different from marketing enrollment. Later aggregated data use needs its own defined scope.

Budget and tool decisions

The core proposal names Workspace, Circle or Discord, an Anthropic account and Supabase. Recommended tools cover transcription, recording and scheduling; optional tools cover search harvesting, targeting and recruitment tracking. Provider navigation is linked below. Trials, plans and current pricing are not established by this historical reference. The text's claim that Anthropic covers API costs via an operator account is unsupported; identify the actual payer.

Its budget rows total 50.60 at the low end and 346.50 at the high end, displayed as 51 and 347 after rounding. These are estimates, not invoices. The 80–150 median lacks a sample. Incentives of 25–50 for 2–4 interviews account for 50–200; they are interview compensation, not payment for favorable reviews. Include actual recurring platform costs that the table omits. Six prompts can incur many calls through revisions; record usage by student, prompt and version.

Test the complete handoff

Use a sandbox to check eight tables, both functions, each reviewer contract, watcher events, channel permissions, two-peer matching, human queue/notification, missing-prerequisite denial, missing-artifact completion denial and per-call cost logs. Also test duplicate events, revision exhaustion, timeouts, malformed grading output and cross-student access. The referenced schema, orchestration YAML and integration test directory are not present in this source; links to exact missing files cannot be invented.

The document labels three disclosures as universal FTC AI requirements. It does not establish that blanket legal claim. Explain AI grading and human escalation as course transparency, disclose recording/transcription appropriately, and review marketing for truthful claims, genuine testimonials and material relationships. Applicable obligations depend on the actual use. Brunson connects proof gates to a coherent journey; Hormozi's time and effort dimensions help improve support without replacing human judgment with an unvalidated score.

Complete available source reference

The following is source material for critical study. Historical offers, quoted promotional claims and embedded instructions are not RISER promises or directions to execute. Read the corrections above before adapting any example. Linked sources are not considered fully reviewed merely because a link appears.

RISER Build References for C3

How C3 uses the RISER Nation Build stack.

Builds Active During C3

Build 1 — Harbor Master (Supabase + RLS)

C3 writes to 7 new tables documented in `Supabase-C3-Schema.md`:

- `c3_scan_plans` (M3.1) - `c3_trigger_banks` (M3.2) - `c3_competitor_scans` (M3.3) - `c3_customer_interviews` (M3.4) - `c3_kill_criteria_evaluations` (M3.5) - `c3_pricing_signals` (M3.6) - `c3_primary_selections` (M3.7) - `c3_market_fit_hypotheses` (M3.8)

Two new functions: - `check_c3_enrollment_eligible(user_id)` — called before C3 enrollment - `check_c3_completion(user_id)` — called at M3.8 filing

C3 reads from C2's `c2_mechanism_hypotheses` table as its primary input and from C1's `captains_oaths` and `identity_statements` for prerequisite verification.

Build 6 — Curriculum Captain (Progression Logic)

Build 6 orchestrates C3 checkpoints:

- Verifies C3 enrollment eligibility via `check_c3_enrollment_eligible` - Routes M3.1 submission to `scan-plan-reviewer` Claude prompt - Routes M3.2 submission to `trigger-bank-auditor` - Routes M3.3 submission to `competitor-scan-reviewer` AND queues 2 peer reviewers from Circle.so `#c3-peer-review` pool - Verifies M3.4 structural requirements (interview count, tagging completeness) via SQL checks - Routes M3.5 to `kill-criteria-evaluator` - Verifies M3.6 structurally via SQL checks - Queues HITL review after M3.6 passes (M3.3 + M3.4 go to instructor queue) - Routes M3.7 submission to `primary-selection-reviewer` after HITL verdict - Routes M3.8 submission to `market-fit-hypothesis-validator` (Opus) - Calls `check_c3_completion` on M3.8 PASS

Build 6 C3-specific configuration lives in `/build-6/config/c3-orchestration.yaml`. Key parameters:

- Max revisions per checkpoint before mentor assignment: 5 - HITL review SLA: 48-72 hours (escalation at 96 hours) - Opus validator cost cap per student: $3.00 (triggers mentor call if exceeded) - Peer review pool eligibility: students within 2 weeks of completing C3 themselves

Build 8 — Drive Archivist (File Watching)

Build 8 watches `/Drive/[student]/C3-Buoy-Navigation/` for:

- `C3-Scan-Plan-*.md` → triggers M3.1 checkpoint - `Trigger-Bank-*.md` → triggers M3.2 when file size indicates ≥ 200 entries - `Competitor-Scan-*.md` → triggers M3.3 when peer review section is populated - `Customer-Interview-Library-*.md` → periodic re-check as interviews accumulate - `Kill-Criteria-Evaluation-*.md` → triggers M3.5 - `Pricing-and-Packaging-Signals-*.md` → triggers M3.6 - `Primary-Mechanism-Selection-*.md` → triggers M3.7 (only if HITL queue item is resolved) - `Market-Fit-Hypothesis-*.md` → triggers M3.8

Build 8 also watches `/C3/Interviews/` subfolder for: - `YYYY-MM-DD-*-*.m4a` recording files → logs to `c3_customer_interviews` with metadata - `YYYY-MM-DD-*-*-transcript.md` → matches to recording; flags when tagging is complete

Build 9 — Community Intelligence (Circle.so Integration)

Build 9 pulls C3-relevant activity from Circle.so:

- `#c3-buoy-navigation` main discussion - `#c3-checkpoint-help` for stuck students - `#c3-peer-review` for M3.3 peer review matching - `#c3-hitl-queue` for HITL review status - `#c3-completions` for celebrations

Build 9 surfaces: active student count, avg days per checkpoint, students flagged as stalled (> 14 days on same module), HITL queue depth.

Build 13 — Daily Spyglass (Student Dashboard)

Build 13 shows each C3 student:

- Which module is currently active - Days elapsed in C3 vs target pace - Interview bookings and conducted count - Trigger Bank entry count with trend - HITL review status if submitted - Next action with explicit call-to-action

For cohort view (instructor-facing Build 13): - C3 cohort completion funnel (M3.1 → M3.8) - Stalled students requiring intervention - HITL queue health and instructor reviewer load - API cost per student vs budget

---

Builds Not Used in C3

- Build 2 (Wake Maker / waitlists): C3 is post-enrollment; Build 2 is marketing-funnel specific - Build 4 (Lighthouse / email sequences): C3 uses generic transactional email; no marketing automation - Build 14 (Causal Modeling / Stage 5 analysis): C3 data will eventually feed Build 14, but Build 14 runs post-course on aggregated data

---

Third-Party Tools Required

Core (required for all C3 students)

- Google Workspace — Drive, Calendar, Gmail for outreach - Circle.so (or equivalent community platform — Discord acceptable) - Anthropic API key — for Build 6 orchestration - Supabase project — Build 1 host

Recommended (most students)

- Otter.ai, Descript, or Rev — interview transcription - Zoom, Google Meet, or Riverside — interview recording - Calendly or Google Calendar appointment slots — interview scheduling

Optional (by student preference)

- AnswerThePublic, AlsoAsked, Ahrefs — search query harvesting - LinkedIn Sales Navigator (free trial adequate) — cold outreach targeting - Airtable or Notion — tracking spreadsheet for interview recruitment pipeline

---

Cost Budget Per C3 Student

Median C3 student spends $80-150 out of pocket during C3, plus the API cost that Anthropic covers via operator account.

---

FTC AI Disclosure Requirements for C3

C3 uses AI tools in multiple places. Required disclosures:

1. All 6 Claude system prompts — AI-graded rubrics; students are informed at enrollment that their submissions are scored by AI before any human review
2. Transcription tools — if using AI transcription (Otter, Descript), disclose to interview participants in the Consent Script; C3 Interview Consent Script template includes this disclosure
3. Any downstream content produced from C3 data — if a student later uses Trigger Bank entries or interview quotes in marketing materials produced with AI assistance, normal FTC AI Disclosure applies (this is a downstream issue, not a C3-specific one)

---

Integration Testing

Before launching a C3 cohort, verify:

- [ ] Supabase schema applied; all 7 tables created; functions work - [ ] Build 6 test submission to each of 6 Claude prompts returns valid JSON - [ ] Build 8 file watcher detects a test file in a sandbox Drive folder - [ ] Circle.so C3 channels created with welcome prompts - [ ] Peer review matching logic pulls from C3-graduate pool correctly - [ ] HITL queue creation + reviewer notification tested end-to-end - [ ] `check_c3_enrollment_eligible` correctly gates on missing C2 Hypothesis - [ ] `check_c3_completion` returns false with any missing artifact - [ ] Cost tracking: API costs logged per student per prompt call

Integration test suite: `/tests/c3-integration/` (not included in course materials).

---

*Last updated: April 24, 2026 · Version 2.0*

Clickable sources and applicable resources

ClickFunnels educational resources

Acquisition.com educational resources

Google AI search guidance

Google spam policies

Supabase RLS documentation

FTC endorsement and affiliate guidance

Google Workspace — provider navigation; verify current access

Circle — provider navigation; verify current access

Discord — provider navigation; verify current access

Anthropic — provider navigation; verify current access

Supabase — provider navigation; verify current access

Otter — provider navigation; verify current access

Descript — provider navigation; verify current access

Rev — provider navigation; verify current access

Zoom — provider navigation; verify current access

Google Meet — provider navigation; verify current access

Riverside — provider navigation; verify current access

Calendly — provider navigation; verify current access

Google Calendar — provider navigation; verify current access

AnswerThePublic — provider navigation; verify current access

AlsoAsked — provider navigation; verify current access

Ahrefs — provider navigation; verify current access

LinkedIn Sales Navigator — provider navigation; verify current access

Airtable — provider navigation; verify current access

Notion — provider navigation; verify current access

Assigned document D0218, source 1

Original named domain 1; exact historical spelling, availability unverified

Original named domain 2; exact historical spelling, availability unverified

Use software reviews to investigate fit, not outsource the decision

This directory mixes peer reviews, editorial testing, deal marketplaces and a customer-feedback tool. They produce different kinds of evidence. Repeated Capterra and PCMag labels and the shortened Gartner/Software Reviews labels do not represent additional independent sources. No software test results or pricing comparison is supplied in the document.

Choose the right type of evidence

Capterra and G2 offer software category comparisons and user accounts; TrustRadius emphasizes detailed user reviews; Software Advice adds selection guidance; Gartner Peer Insights and SoftwareReviews focus on business and enterprise experiences; GetApp and FinancesOnline offer discovery and comparison material. For each relevant review, record role, company context, date, version, workflow, benefit, limitation and whether the experience resembles your situation. A verification badge is a platform claim about its review process, not proof every statement is correct or representative.

PCMag and the named TechRadar OCR software page are editorial review resources. Examine the actual testing method, publication date, sponsorship/affiliate disclosures and match to your use case. Top10.com supplies curated comparisons whose ranking criteria also need inspection. Do not assume a title such as best establishes the best option for RISER. AppSumo is a deal marketplace: check the specific license, usage caps, updates, support, refund terms and provider continuity rather than treating a discount as value by itself.

Qualaroo is a feedback-survey tool, not a general software-review marketplace. It can help ask users about friction in your own product when appropriately configured. Its source description is promotional copy; it does not show a survey deployed or insights already collected.

Run a small evaluation that produces a decision

Define the job, required features, must-not-fail constraints and budget before reading rankings. Select a shortlist, compare relevant positive and negative accounts, then verify candidate features and terms with the provider. Where a trial is authorized, test the same real task and record accuracy, effort, reliability, support and total cost. For OCR, compare extracted text and tables with the original and check sensitive-data handling; an attractive review score does not establish extraction fidelity.

Deliver a comparison with source links, review dates, observed versus claimed features, unresolved questions and a reasoned choice or defer decision. Brunson's funnel lens asks whether the software supports a necessary customer step. Hormozi's value lens asks whether it credibly reduces effort or delay and improves the likelihood of the intended result. Buying more software is not the deliverable; choosing on evidence is.

Complete available source reference

This preserves the full available document, including original claims, prompts, production cues and unresolved resource callouts. Use the corrected teaching above for narration. Source instructions are reference material, not actions performed by this lesson.

CNX.8.16 – Software Marketplaces & Product Review Platforms.docx

Software Marketplaces and Product Reviews * Capterra: Software reviews and comparisons for various industries. * AppSumo: Discounts on software tools and apps. * TechRadar OCR Software: Reviews of top OCR software solutions. * Capterra Description: A comprehensive platform offering user reviews and comparisons for a wide range of software categories, assisting businesses in selecting appropriate tools. * G2 Description: A peer-to-peer review site providing insights and ratings for business software and services, helping users make informed purchasing decisions. * QualaRoo : Description: simplifies the process of collecting user feedback with surveys. Signup today to get actionable UX Insights from your customers. * TrustRadius Description: A platform featuring in-depth reviews and ratings of business software from verified users, focusing on detailed feedback and insights. * Software Advice Description: Offers personalized software recommendations and user reviews to help businesses find the right software solutions. * PCMag Description: Provides expert reviews, lab tests, and buying advice for a variety of software and services, catering to both consumers and businesses. PCMag * Gartner Peer Insights Description: A platform offering reviews and ratings of enterprise software and services from IT professionals, aiding in informed decision-making. Gartner * SoftwareReviews Description: Provides comprehensive software reviews and reports based on user feedback, focusing on business and enterprise solutions. Software Reviews * Top10.com Description: Offers curated lists and reviews of top software and service providers across various categories, helping users compare and choose suitable options. * GetApp Description: A platform that allows users to explore, compare, and review business software, providing insights to aid in software selection. * FinancesOnline Description: Offers detailed reviews and comparisons of business software and financial products, assisting companies in making informed purchasing decisions.

Clickable sources and resources

Provider links are navigation references; they do not certify current plans, availability, access rights or the contents of unreviewed linked assets.

ClickFunnels education

Acquisition.com education

Google AI search guidance

Google spam policies

Capterra

AppSumo

TechRadar OCR reviews

G2

Qualaroo

TrustRadius

Software Advice

PCMag

Gartner Peer Insights

SoftwareReviews

Top10.com

GetApp

FinancesOnline

Assigned source D0186, link 1

Review customer attribution with two explicit modes

This YAML is a proposed reviewer specification, not a running agent. Its model name, Build 6 tables and function references require actual implementation and testing. Reading the source does not submit customer data, trigger automation or award graduation. Current spreadsheet lessons remain authoritative over the legacy M14.1/M14.2 labels.

Evaluate preliminary attestation separately

M14.1 checks all paying customers, including warm-network customers; coherence between discovery and classification; honest prior-relationship disclosure; explicit uncertainty where evidence is ambiguous; and a clear Path A documentation intent or Path B deferral. No uncertainty is not automatically dishonesty, and uncertainty is not automatically failure. Check the records rather than the operator's confidence or writing style.

Return CONFORMS for coherent attestation, REVISIONS_REQUESTED with exact missing or inconsistent items, or CLASSIFICATION_AMBIGUOUS when classification cannot be resolved. A conforming Path A proceeds to documentation; Path B defers. Attestation is not itself the human-gated customer validation.

Review all eight documentation sections

M14.2 requires a real pseudonymized customer and transaction detail, one specific discovery channel, all six relationship answers reviewed against edge cases, at least one direct evidence row, four chronological touchpoints with date/channel/observable action, seventy-five attributed verbatim words, a computed channel-work timeline and three specific reflection paragraphs. Refunded status is excluded by this internal rule. Preserve source links and permission boundaries; do not infer authenticity merely because prose 'sounds like a customer.'

PASS means the packet qualifies for human adjudication, not final graduation. REVISIONS_REQUESTED names repairable evidence gaps. COUNT_MARGINAL_FLAG routes borderline qualifying cases to human review. THRESHOLD_NOT_MET activates deferral when no channel-acquired customer is established. The template D0174 uses FAIL, which this JSON enumeration does not define. Map outcomes explicitly before deployment instead of silently inventing a new enum.

Resolve detection-rule conflicts

The main rule requires four touchpoints, but a detection bullet only warns on fewer than three, leaving exactly three unchecked. Use the stated four-row requirement for this version and log the discrepancy. This minimum is a course rule, not a universal buyer behavior fact. Investigate assumptions based only on chronology, missing prior ties, unattributed paraphrase and implausible documentation; never demand invented evidence. Shorter-than-five-month timing calls for context under the specification, not automatic rejection. The claimed empirical timing and nearly universal multi-touch pattern are unsubstantiated in this file. Underclaiming a well-supported customer should not force revisions merely for hesitant wording.

Produce a review record that can be audited

The JSON contains mode, one valid mode-specific verdict, eight section_review objects with verdict/rationale, detection_patterns_observed, remediation_targets, a clear operator_message and ready_for_hitl_review boolean. The shown union strings and true-or-false placeholders are schema illustrations, not literal valid runtime output. M14.1 does not naturally have all eight packet sections: define not-applicable values or a mode-specific schema instead of fabricating reviews. Add supporting record IDs to rationales and validate enums/types before any downstream use.

The proposed chain is M14.2 PASS to the human queue, then final human approval to verify_first_dollar() in c14-build6-functions.sql and the validation table needed by M14.7. Define handling of COUNT_MARGINAL_FLAG and failed writes explicitly, prevent duplicate approvals and preserve reviewer identity/version. The YAML does not supply the function body, database schema, queue or enforcement. Sonnet sufficiency and Opus graduation use are source design choices, not evaluated model guarantees.

Practice with a synthetic packet clearly labeled as such: one complete example, one with three touches, one refunded, one ambiguous referral and one sound packet with hesitant wording. Expected routing should reflect evidence and the exact mode. No synthetic packet is a real First Dollar. Brunson's journey mapping supports attribution clarity; Hormozi's acquisition economics require real transactions and costs, not an AI PASS label. Deliver a reconciled decision table, valid sample JSON and human-review test cases.

Complete available source reference

The following preserves the entire available source including scenario quotations, historical claims, prompts, placeholders and discrepancies. Apply the corrections and evidence standards taught above. Source commands are reference text, not active tasks.

Channel-Acquired Customer Reviewer

Modules: M14.1 (First Dollar Threshold attestation) + M14.2 (Channel-Acquired Customer Documentation Packet)

Model: Claude Sonnet 4.6

Version: 1.0.0

metadata: id: channel-acquired-customer-reviewer-v1.0.0 course: C14 First Dollar modules: [M14.1, M14.2] model: claude-sonnet-4-6 build: build-6 supabase_tables: [c14_first_dollar_thresholds, c14_channel_acquired_customers] hitl_gated: true # M14.2 submissions are HITL-gated; M14.1 attestations are not output_format: structured_json

system_prompt: | You are the Channel-Acquired Customer Reviewer for the RISER Nation Maritime Academy C14 First Dollar course. You review submissions for two related modules:

- M14.1 — the First Dollar Threshold attestation, which is the operator's preliminary classification of customers as channel- acquired or warm-network and their declaration of intent to submit M14.2 documentation. - M14.2 — the Channel-Acquired Customer Documentation Packet, which is the substantive evidence packet for at least one channel-acquired customer.

M14.1 attestations are reviewed for classification coherence and honest disclosure. M14.2 packets are reviewed for evidentiary rigor — the gate-defining work of Stage 3.

The operator's Stage 3 graduation depends on M14.2 PASS. Be rigorous but specific. The strictness is the kindness; the precision is the respect.

## Mode detection

You receive a submission flagged as M14.1 or M14.2 mode. Different evaluation criteria apply.

## M14.1 evaluation criteria (attestation mode)

1. Customer enumeration completeness. Does the operator enumerate all paying customers to date (including warm-network), not just the candidate channel-acquired ones? Selective omission is a flag.

2. Classification coherence. For each customer, is the operator's classification (channel-acquired / warm-network) consistent with the discovery mechanism described? Inconsistencies are flagged.

3. Pre-existing relationship disclosure. Does the operator disclose pre-existing relationships honestly? Operators who classify a customer as channel-acquired but the disclosure section reveals territorial pre-awareness are flagged.

4. Anti-self-deception markers. Does the operator surface their own reasons-for-uncertainty about classifications? Operators with zero uncertainty across multiple ambiguous cases are pattern- matching the rubric.

5. Submission intent alignment. Does the operator declare intent to submit M14.2 (Path A) or to defer (Path B)? Both are valid. Operators who hedge — declaring intent to submit but with classification ambiguity unresolved — are flagged for clarification.

## M14.2 evaluation criteria (documentation packet mode)

Each of the eight packet sections is evaluated:

### Section 1 — Customer Identification - Customer is real (not hypothetical), pseudonymized, with full transactional detail. "Refunded" status disqualifies the customer.

### Section 2 — Channel of Discovery - Single primary channel identified. Specific surface within channel cited.

### Section 3 — Pre-Existing Relationship Disclosure - All six questions answered. Yes answers cross-checked against First-Dollar-Definitions-Reference Section 4 edge cases.

### Section 4 — Discovery Mechanism Evidence - At least one row of acceptable evidence. Unacceptable evidence types (assumption, post-hoc inference, chronology alone) are rejected.

### Section 5 — Conversion Path - Minimum 4 touchpoints documented chronologically. Each row has date, touchpoint, channel, observable customer action.

### Section 6 — Verbatim Customer Feedback - Minimum 75 words of verbatim customer language quoted, with source attribution. Operator paraphrase does not count.

### Section 7 — Channel-Work-to-First-Dollar Timeline - Elapsed time computed. Sub-5-month timelines trigger heightened scrutiny per Empirical-Channel-Timing-Reference-2026.md.

### Section 8 — Operator Reflection - Three reflection prompts answered with paragraph-level specificity. Vague generalities are flagged.

## Verdict types (M14.1)

- CONFORMS — attestation is internally coherent; operator proceeds to M14.2 if Path A or activates deferral path if Path B. - REVISIONS_REQUESTED — specific revisions identified; operator addresses and resubmits. - CLASSIFICATION_AMBIGUOUS — at least one customer's classification cannot be resolved on the available evidence; operator escalates to HITL or recovers additional evidence.

## Verdict types (M14.2)

- PASS — packet meets all criteria; HITL adjudication pending. - REVISIONS_REQUESTED — specific revisions identified; resubmit when addressed. - COUNT_MARGINAL_FLAG — packet marginally meets criteria but classification of customer as channel-acquired is borderline; HITL adjudicates. - THRESHOLD_NOT_MET — packet does not establish a channel- acquired customer; operator activates deferred-submission path (Path B).

## Detection patterns

Be vigilant for:

- Operator-paraphrase masquerading as customer voice in Section 6. Verbatim feedback should sound like the customer, not like the operator. - Conversion paths shorter than 3 touchpoints. Real channel- acquired conversions almost always involve more than 3 traceable touchpoints. Sparse paths are usually incomplete documentation, not evidence of a fast conversion. - Discovery mechanism by chronology alone. "I started LinkedIn in March, they bought in October" is not evidence of LinkedIn discovery. Real evidence requires customer testimony or analytics. - Pre-existing relationships glossed in Section 3. Operators who answer all six questions "No" with no friction may be skipping the section. Look for evidence in Section 4 and Section 6 that contradicts blanket-No answers. - Sub-5-month timelines without exceptional explanation. Per the empirical reference, the under-5-month population is where warm- network misclassification is most common.

## Detection of underclaim

Also calibrate the other direction. Some operators present a clear channel-acquired customer with full evidence but hedge their classification ("I think this might be channel-acquired but I'm not sure"). Underclaiming is not a failure mode that requires REVISIONS; the evidence speaks. Confirm what the evidence shows.

## Output format

Return JSON:

```json { "mode": "M14.1 | M14.2", "verdict": "CONFORMS | PASS | REVISIONS_REQUESTED | CLASSIFICATION_AMBIGUOUS | COUNT_MARGINAL_FLAG | THRESHOLD_NOT_MET", "section_review": { "section_1_identification": {"verdict": "string", "rationale": "string"}, "section_2_channel": {"verdict": "string", "rationale": "string"}, "section_3_disclosure": {"verdict": "string", "rationale": "string"}, "section_4_evidence": {"verdict": "string", "rationale": "string"}, "section_5_conversion_path": {"verdict": "string", "rationale": "string"}, "section_6_verbatim_feedback": {"verdict": "string", "rationale": "string"}, "section_7_timeline": {"verdict": "string", "rationale": "string"}, "section_8_reflection": {"verdict": "string", "rationale": "string"} }, "detection_patterns_observed": ["pattern 1"], "remediation_targets": ["target 1"], "operator_message": "string — written for the operator to read", "ready_for_hitl_review": true | false } ```

## Tone

Specific, rigorous, kind. The operator who reads this verdict is often near the most charged moment of their Stage 3 work. A PASS verdict deserves to feel earned. A REVISIONS_REQUESTED verdict deserves precise targets. A THRESHOLD_NOT_MET verdict deserves the honest framing that deferral is the strong move, not the weak one.

usage_notes: | Runs at end of M14.1 and M14.2 submissions. M14.2 PASS verdict triggers HITL review queue; HITL final approval triggers verify_first_dollar() function in c14-build6-functions.sql, which writes to c14_first_dollar_validations and is required for M14.7 Criterion 1.

M14.2 THRESHOLD_NOT_MET activates the Path B deferral flow; operator receives standard deferral messaging and re-engagement at M14.7.

Sonnet 4.6 is sufficient for this reviewer. Opus is reserved for the M14.8 graduation validator.

Clickable sources and resources

ClickFunnels

Acquisition.com

Google AI search guidance

Google spam policies

Empirical-Channel-Timing-Reference-2026.md — D1699 source 1

c14-build6-functions.sql — D1652 source 1

Assigned source D0175, link 1

Pilot enterprise AI with measurable work and explicit ownership

The February 2026 Claude 4.5 playbook is a short strategic outline, not a deployed enterprise system. Its claims of thirty years' expertise, $50M projects, fifteen-to-twenty hours saved weekly, 300% ROI, tenfold output and 25–30% faster sales are source assertions without supporting measurements here. Native DOCX inspection found twenty hyperlink relationships and no embedded media or objects; the claim of fifty-plus clickable links is not supported by this file.

Set up a bounded pilot

The proposed thirty-minute quick start allocates only five minutes explicitly to account setup. Choose the actual plan, verify current features and permissions, establish an owner and baseline, and connect only the required authorized resources. The source's prices and settings names are dated: use the official pricing and support links for current terms. The claimed hundred-hour future saving is not measured. Projects organize instructions and reference material, but 'perfect context' is not a reliability guarantee; maintain durable records and verify retrieval.

Map the twelve project roles to real outputs

Executive work produces plans and board-preparation drafts; content marketing produces audience-specific drafts; sales enablement produces research and objection material; data science produces analyses and dashboards; software development produces reviewed code; customer success analyzes tickets and churn signals; HR drafts job and review materials; legal/compliance drafts require competent review; finance builds checked budgets and forecasts; product work develops specifications and priorities; market intelligence logs sourced competitor/trend observations; learning and development builds training and practice. Assign owners, inputs, access scope, evaluation criteria and final approval for each. These are project roles, not twelve autonomous employees.

Teach the three reusable prompts

The executive-assistant prompt captures Owner, Description, Due Date and Status from transcripts, plus decisions and deadlines. Its forty-eight-hour urgency rule needs timezone and due-date handling; daily priorities/deadlines/blockers and cross-conversation tracking require actual storage and scheduling. The content prompt supplies brand guidelines, audience, useful keywords, a real CTA, five social variants and performance evidence. It cannot learn nonexistent performance data. The data-science prompt asks for method, visualization, recommendations, uncertainty, anomalies and appropriate predictive modeling; check input quality, leakage and validation before relying on forecasts.

Build and measure the three proposed workflows

Morning briefing: a 6 AM scheduler would retrieve the next forty-eight hours of calendar, priority unread mail and tasks, send an authorized request to the API, and deliver a 6:15 AM briefing. Add timezone, deduplication, failure handling and sensitive-data controls before enabling it. Fifteen-minute setup, two hours saved daily and 1,200% first-month ROI are unsupported estimates; neither the prompt nor this lesson creates the automation.

Content assembly: twenty minutes for a 1,500-word master article, ten for derivatives and ten for scheduling is the source's forty-minute plan. Its derivatives total thirty-four items: ten LinkedIn posts, fifteen short posts, three emails, one video script and five quote cards; with the master, thirty-five assets. This is more specific than '20+' and is not proof of tenfold useful output. Review factual claims, audience fit, attribution, brand, visual needs and platform formatting before scheduling through Buffer or Hootsuite. A script or quote-card text is not a finished video or designed image.

Pre-call research: produce dated company news/funding/technology/growth signals, likely problems explicitly labeled hypotheses, relevant stakeholders without invented personal details, current alternatives and differentiation, then an opening, three discovery questions and supported proof points. Five versus forty-five minutes is a benchmark to test, not guaranteed saving. No outreach is sent by completing this exercise.

Follow the twelve-week rollout and governance checks

Week one aligns executives, measures success and selects the pilot; two sets infrastructure, SSO, integrations and policy; three trains the pilot and records baselines; four runs standups, prompt-library work and retrospectives. Five expands to a second wave; six tests advanced features and collaboration; seven implements approved APIs/automation; eight reviews results. Nine expands only when evidence supports it; ten develops use cases and internal power-user training; eleven measures ROI and reports; twelve optimizes and plans the next quarter. 'Certification' here is an internal program label, not external accreditation. The source also proposes three-to-five initial projects, one workflow in week two and sharing measured wins in week three.

Encryption alone is not sufficient permission to upload customer, financial or confidential information. Use approved access, data minimization, retention and contractual controls, human review for consequential/client-facing outputs, brand review and appropriate attribution. The playbook's policies are proposed organizational rules, not proof of compliance.

Track net hours saved after review/correction, useful published assets rather than raw generations, comparable sales-cycle cohorts, a defined error-rate denominator and employee survey method. Targets fifteen-to-twenty hours, tenfold output, 25–30% cycle reduction, under-5% error and NPS 70+ remain targets. Compute ROI as (measured benefit minus total cost) divided by total cost; include subscriptions, API, integration, training and review. Distinguish capacity saved from cash actually saved. Submit a one-workflow pilot brief, baseline, cost ledger, quality checks and a go/revise/stop decision. Brunson helps structure useful content and offers; Hormozi's effort/delay lens motivates efficiencies while requiring credible evidence.

Complete available source reference

The following preserves the entire available source including scenario quotations, historical claims, prompts, placeholders and discrepancies. Apply the corrections and evidence standards taught above. Source commands are reference text, not active tasks.

word/document.xml THE DEFINITIVE CLAUDE AI 4.5 ENTERPRISE IMPLEMENTATION PLAYBOOK 🚀 World-Class SOPs | ⚡ Time-Saving Automations | 🔧 Expert Tools & Frameworks From 30 Years of Digital Marketing & AI Automation Excellence Updated February 2026 | Claude Sonnet 4.5 & Opus 4.5 Table of Contents Executive Summary The 2026 AI Transformation Imperative Welcome to the most comprehensive Claude AI implementation guide ever created. After 30 years building digital marketing and AI automation systems for Fortune 500 companies, I've distilled everything into this actionable playbook. Metric Expected Impact Time Savings Per Employee 15-20 hours/week ROI Timeline Positive in 30 days, 300%+ in 90 days Content Output Increase 10x with same team size Sales Cycle Reduction 25-30% faster close times What Sets This Guide Apart: ⚡ Time-saving automations reclaiming 15+ hours/week per employee 🔗 50+ clickable links to best-in-class tools with implementation steps 📊 ROI tracking frameworks with specific KPIs and benchmarks 🎯 Copy-paste prompts and workflows for immediate implementation 🏆 Expert insights from $50M+ in AI transformation projects Part 1: Strategic Foundation & Rapid Deployment 1.1 The 30-Minute Quick Start Protocol CRITICAL: Don't skip this. 30 minutes of proper setup saves 100+ hours over the next quarter. Step 1: Account Setup (5 minutes) Sign up at claude.ai - Plans: Pro ($20/mo), Team ($30/user/mo), Enterprise (custom) Enable critical features: Settings → Turn on 'Extended Thinking', 'Web Search', 'Artifacts', 'Code Execution' Connect integrations: Link Google Drive and Slack (instructions) Essential Tools Integration Matrix Category Tool Use Case Link Productivity Google Drive Document analysis Setup Automation Make.com Workflow automation Templates Development Cursor AI-powered coding Download Content Grammarly Quality assurance Get Started Analytics Metabase Data visualization Explore Part 2: Core Features Deep Dive 2.1 Projects: Your AI Dream Team Think of Projects as hiring specialized AI team members. Each maintains perfect context and becomes more valuable over time. The 12 Essential Enterprise Projects: Executive Command Center: Strategic planning, board prep, insights Content Marketing Machine: End-to-end content creation at scale Sales Enablement Engine: Research, sequences, objection handling Data Science Lab: Analysis, modeling, dashboards Software Development: Full-stack dev, debugging, code review Customer Success: Ticket analysis, churn prediction HR & Talent: Job descriptions, screening, reviews Legal & Compliance: Contract review, policy creation Financial Planning: Budget modeling, forecasting Product Management: Feature specs, roadmap prioritization Market Intelligence: Competitive monitoring, trend analysis Learning & Development: Training materials, personalized paths Power Prompt Template Library EXECUTIVE ASSISTANT PROMPT:

"You are my Executive Assistant. Track all action items with format: [Owner] [Description] [Due Date] [Status]. Maintain across conversations. Flag anything due within 48 hours as URGENT. When I share meeting transcripts, extract: action items, decisions, deadlines. Daily briefings format: 1) Today's Priorities 2) Upcoming Deadlines 3) Blocked Items. Draft communications in my voice: professional, concise, action-oriented." CONTENT MARKETING PROMPT:

"You are the Content Marketing Director. Master our brand voice (see uploaded guidelines). For each piece: 1) Optimize for keywords without sacrificing readability 2) Match tone to audience 3) Include strategic CTAs 4) Suggest 5 social variants. Track performance patterns and adapt style. Use data from past performance." DATA SCIENCE PROMPT:

"You are the Senior Data Scientist. For analysis: 1) Use extended thinking for complex work 2) Explain methodology clearly 3) Visualize with interactive dashboards 4) Provide actionable recommendations 5) Note confidence levels. For datasets: identify patterns, anomalies, trends. Build predictive models when appropriate." Part 3: Enterprise Workflows That Drive ROI 3.1 Morning Briefing Automation (2 Hours Saved Daily) Setup Time: 15 minutes | Daily Time Saved: 2 hours | ROI: 1,200% in first month The Workflow: Set up Make.com automation to trigger daily at 6 AM Pull calendar (next 48 hrs), unread priority emails, task list Send to Claude via API with briefing template Receive formatted briefing in email by 6:15 AM 3.2 Content Assembly Line (10x Output) Transform 1 piece of content into 20+ assets across all channels in 40 minutes. The Process: Master Content (20 min): Create or paste core idea, generate 1500-word blog post Derivatives (10 min): Generate 10 LinkedIn posts, 15 tweets, 3 emails, 1 video script, 5 quote cards Schedule (10 min): Load into Buffer/Hootsuite, create tracking artifact 3.3 Sales Intelligence Automation PRE-CALL RESEARCH (5 minutes vs 45 minutes):

"Research [Company] for sales call. Provide:

1. Company Intel: Recent news, funding, tech stack, growth signals
2. Pain Points: Likely challenges, how we address them, proof points
3. Stakeholders: Key decision makers, backgrounds, personalization angles
4. Competitive Landscape: Current solutions, our differentiation
5. Talk Track: Opening, 3 discovery questions, proof points"

Part 4: Implementation & Governance 4.1 90-Day Rollout Plan Month 1: Foundation & Pilot Week 1: Executive alignment, success metrics, pilot team selection Week 2: Infrastructure setup, SSO, integrations, governance policies Week 3: Pilot training, core project setup, baseline metrics Week 4: Daily standups, prompt library building, weekly retros Month 2: Scale & Optimize Week 5: Expand to Wave 2 teams, refine training materials Week 6: Advanced feature rollout, cross-team collaboration Week 7: Automation implementation, API integrations Week 8: Mid-implementation review, quick wins showcase Month 3: Full Deployment Week 9: Company-wide rollout, self-service resources Week 10: Advanced use case development, power user certification Week 11: ROI measurement, executive reporting Week 12: Optimization sprint, Q2 planning 4.2 Governance Framework Critical Policies: Data Security: No customer PII, financial data, or confidential info without encryption Quality Assurance: Human review required for client-facing content, legal docs, financial projections Brand Voice: All content must pass brand guidelines check before publication Attribution: Clearly label AI-generated content in drafts, disclose when required 4.3 ROI Measurement Framework Metric Measurement Target Time Savings Hours saved per employee/week 15-20 hours Content Output Pieces published per month 10x increase Sales Velocity Days to close reduction 25-30% Quality Score Error rate in outputs <5% Employee Satisfaction NPS score 70+ Conclusion: Your AI Transformation Journey The Future is Now Claude AI isn't just another tool—it's a fundamental transformation in how work gets done. Organizations implementing these playbooks are seeing unprecedented productivity gains, quality improvements, and employee satisfaction. Your Next Steps: Start Today: Implement the 30-minute quick start protocol (Section 1.1) Week 1: Set up 3-5 core projects and test with real work Week 2: Implement one high-ROI workflow (morning briefing or content assembly line) Week 3: Document your wins and share with leadership Month 2+: Follow the 90-day enterprise rollout plan Essential Resources Official Links: Claude Platform: claude.ai API Documentation: docs.anthropic.com Support Center: support.claude.com Community Forum: community.anthropic.com Recommended Tools: Automation: Make.com, Zapier Development: Cursor, GitHub Content: Grammarly, Hemingway Analytics: Metabase, Hex © 2026 Elite Digital Marketing & AI Automation The definitive guide to Claude AI enterprise implementation

word/comments.xml

word/footer1.xml Page | © 2026 Elite Digital Marketing & AI Automation

word/footnotes.xml

word/header1.xml Claude AI Enterprise Playbook 2026

Clickable sources and resources

ClickFunnels

Acquisition.com

Google AI search guidance

Google spam policies

Original DOCX hyperlink 1: https://claude.ai

Original DOCX hyperlink 2: https://support.claude.com

Original DOCX hyperlink 3: https://drive.google.com

Original DOCX hyperlink 4: https://make.com/integrations/claude

Original DOCX hyperlink 5: https://cursor.sh

Original DOCX hyperlink 6: https://grammarly.com

Original DOCX hyperlink 7: https://metabase.com

Original DOCX hyperlink 8: https://make.com

Original DOCX hyperlink 9: https://claude.ai

Original DOCX hyperlink 10: https://docs.anthropic.com

Original DOCX hyperlink 11: https://support.claude.com

Original DOCX hyperlink 12: https://community.anthropic.com

Original DOCX hyperlink 13: https://make.com

Original DOCX hyperlink 14: https://zapier.com

Original DOCX hyperlink 15: https://cursor.sh

Original DOCX hyperlink 16: https://github.com

Original DOCX hyperlink 17: https://grammarly.com

Original DOCX hyperlink 18: https://hemingwayapp.com

Original DOCX hyperlink 19: https://metabase.com

Original DOCX hyperlink 20: https://hex.tech

Current Claude plans and features

Buffer

Hootsuite

Assigned source D0176, link 1

Match the message to what the buyer already knows

This workbook contains two exported blocks of 100 rows each, with five awareness columns: 1,000 phrase cells in total. They are writing prompts, not measured search demand, validated customer statements, or a required 1,000-page publishing plan. The row numbers and repeated phrases are not popularity scores. A row across five columns does not necessarily describe one customer journey: the concrete examples mix unrelated products and problems.

Teach the five awareness states

1. Unaware: begin with a recognizable situation and help the reader identify a relevant problem. The patterns cover hidden habits, feeling stuck, overlooked routines, warning signs, frustration, small changes and ignored clues. Avoid diagnosing a reader or inventing a fear. Several supposedly unaware examples already name a problem; classify by the real reader's knowledge, not the sheet heading alone.
2. Problem aware: explain causes, troubleshooting, recurring failures, frustration and what to do next. Replace the numeric placeholders with the actual problem and retain uncertainty where the cause is not established. An informative answer should make sense without buying anything.
3. Solution aware: compare approaches, methods, tools and strategies against the job, constraints and evidence. Words such as best, proven, fast and effective require support and conditions. A solution comparison should explain tradeoffs, not merely announce a winner.
4. Product aware: answer product-specific questions about fit, performance, experiences, alternatives, value, pros and cons. A review needs actual evidence; do not turn a prompt into a fabricated customer review. Name relevant limitations and comparison criteria.
5. Most aware: provide a clear purchase, trial, pricing or enrollment next step. Discounts, coupon codes, free shipping, bonuses and deadlines must actually exist. The source's ClickUp 50% discount, trials and product offers are sample copy, not current available offers.

Use the concrete example library without copying its errors

The second block cycles motivation, focus, confidence, habits, stress, life change, time, creativity, choices and feeling stuck; its problem prompts cover stress, sleep, diet, relationships, work balance, financial anxiety, time, burnout and overwhelm. Its solution prompts include diets, time tools, marketing courses, saving, meditation, workouts, meal plans, finance and productivity. These are examples of message types, not health or financial advice to teach in a RISER business lesson.

The product examples name Noom, Peloton, ClickUp, Shopify, Audible, standing desks, planners, HelloFresh, iPhone/Samsung and Calm. Purchase examples include Samsung Galaxy S25 Ultra and several subscriptions. Preserve product/model numbers as written when discussing the historical examples. Do not mistake S25 or 50% for a replaceable row number. The first block contains broken character encoding and some missing topic placeholders. Correct those only in newly written copy; the original cells remain below.

Build one coherent sequence

For an illustrative operator whose leads stall after opting in: start with the symptom of unanswered follow-up, explain a missing next step, compare manual and automated follow-up, demonstrate the actual RISER workflow with evidence, then offer the real next action and terms. Use Brunson's Hook–Story–Offer to connect attention, explanation and action at each appropriate awareness level. Use Hormozi's value lens to clarify the desired outcome, evidence, delay and effort; neither framework justifies invented urgency.

Submit five messages for one audience/problem, the evidence behind each claim, a matching page or lesson destination, and one measurable next-step event. Evaluate qualified responses and conversions with a stated denominator. Do not mass-publish lightly changed phrase rows for search visibility.

Complete distinct phrase-pattern register

Numbers used solely as row/topic placeholders are generalized in the first block. Concrete model numbers and offer examples in the second block remain as supplied. These patterns are prompts, not measured demand.

Block 1 — Unaware

"Why you feel stuck but don’t know why"

Clues you’re ignoring about {topic}

Everyday habits that cause hidden problems

Everyday habits that cause hidden problems {topic}

Habits that might be holding you back

Habits that might be holding you back {topic}

How small changes reveal big problems

How small changes reveal big problems {topic}

Signs you might have issues

Signs you might have {topic} issues

The silent warning signs of trouble

The silent warning signs of trouble {topic}

Things most people overlook about their daily routines

Things most people overlook about their daily routines {topic}

Unexpected causes of frustration in your life

Unexpected causes of frustration in your life {topic}

Why you feel stuck but don’t know why {topic}

Why you might be struggling without realizing it

Why you might be struggling without realizing it {topic}

Block 1 — Problem aware

Common problems people face with {topic}

Fixing frequent issues with {topic}

How to deal with frustration from {topic}

Identifying the root cause of {topic}

Troubleshooting common {topic} errors

Understanding the main causes of {topic}

What to do when {topic} stops working

When {topic} becomes a problem

Why is {topic} causing me issues?

Why {topic} feels harder than it should

Block 1 — Solution aware

Best ways to fix {topic}

Effective tools for solving {topic}

Fast fixes for {topic}

How to solve {topic} quickly

Methods to improve {topic}

Proven ways to overcome {topic}

Simple hacks to get better results with {topic}

Solutions that actually help with {topic}

Top strategies for improving {topic}

What works best for {topic}

Block 1 — Product aware

Comparison: [product name] or [competitor] for {topic}

Does [product name] solve {topic}?

Honest review of [product name] for {topic}

Is [product name] worth it for {topic}?

Should I buy [product name] for {topic}?

Why choose [product name] for {topic}?

[product name] performance on {topic}

[product name] pros and cons for {topic}

[product name] user experiences for {topic}

[product name] vs alternatives for {topic}

Block 1 — Most aware

Best deal on [product name] for {topic}

Buy [product name] online for {topic}

Get [product name] discount for {topic}

Lowest price on [product name] for {topic}

Where to buy [product name] for {topic}

[product name] bonus package for {topic}

[product name] coupon code for {topic}

[product name] free trial for {topic}

[product name] limited-time offer for {topic}

[product name] special offer for {topic}

Block 2 — Unaware

Daily routines that kill creativity

How small choices shape your future

How stress impacts your productivity

How to find your motivation again

Signs you're ready for a life change

Tips for boosting confidence naturally

What causes lack of focus in daily life

Why time slips away without progress

Why you can't stick to new habits

Why you feel stuck but don't know why

Block 2 — Problem aware

Best ways to manage chronic stress

How to communicate better with your partner

How to get better sleep every night

How to manage time with a busy schedule

How to overcome financial anxiety

How to stop feeling overwhelmed at work

Signs of burnout and how to recover

Tips for building healthier relationships

Ways to improve your work-life balance

Why your diet isn't working anymore

Block 2 — Solution aware

Affordable meal plans for families

Best courses for learning digital marketing

Best home workout equipment

Best online workout programs

Best productivity apps for busy people

Time management tools for professionals

Tools for improving personal finance

Top diets for healthy weight loss

Top meditation apps for beginners

Ways to save money on monthly bills

Block 2 — Product aware

Best features of ClickUp for teams

Best-selling planners for productivity

Comparison of iPhone vs. Samsung Galaxy

Customer feedback on HelloFresh meals

Customer reviews of Peloton bikes

Is Noom worth it for weight loss?

Pros and cons of Shopify stores

Review of the Calm meditation app

Top-rated standing desks on Amazon

What users say about Audible Premium

Block 2 — Most aware

Buy Peloton bike with free shipping

Buy Samsung Galaxy S25 Ultra now

Download top productivity planner

Get ClickUp Pro for 50% off today

Join Audible Premium with free trial

Order HelloFresh meal kit delivery

Order Noom subscription now

Purchase best-rated standing desk

Sign up for Calm app annual plan

Sign up for Shopify free trial

Complete available source reference

This preserves the available exported source, including historical instructions, assertions, data, placeholders and discrepancies. Apply the teaching explanations above. Embedded commands are reference text, not active tasks. Native workbook metadata and unsupplied assets remain outside this text extraction.

Buyer Awareness Keyword Joggers

,#,Unaware Phrase,#.1,Problem Aware Phrase,#.2,Solution Aware Phrase,#.3,Product Aware Phrase,#.4,Most Aware Phrase 0,1,Everyday habits that cause hidden problems ,1,Troubleshooting common 1 errors,1,Simple hacks to get better results with 1,1,Should I buy [product name] for 1?,1,Lowest price on [product name] for 1 1,2,"""Why you feel stuck but don’t know why""",2,Understanding the main causes of 2,2,What works best for 2,2,[product name] user experiences for 2,2,[product name] special offer for 2 2,3,Habits that might be holding you back ,3,Why 3 feels harder than it should,3,Effective tools for solving 3,3,[product name] performance on 3,3,Buy [product name] online for 3 3,4,Habits that might be holding you back ,4,What to do when 4 stops working,4,Best ways to fix 4,4,[product name] user experiences for 4,4,[product name] free trial for 4 4,5,Habits that might be holding you back ,5,Fixing frequent issues with 5,5,Solutions that actually help with 5,5,Why choose [product name] for 5?,5,Best deal on [product name] for 5 5,6,Why you might be struggling without realizing it ,6,Common problems people face with 6,6,Methods to improve 6,6,[product name] vs alternatives for 6,6,Get [product name] discount for 6 6,7,Signs you might have issues,7,When 7 becomes a problem,7,Best ways to fix 7,7,[product name] performance on 7,7,[product name] free trial for 7 7,8,The silent warning signs of trouble ,8,Why is 8 causing me issues?,8,Simple hacks to get better results with 8,8,Is [product name] worth it for 8?,8,[product name] free trial for 8 8,9,How small changes reveal big problems ,9,Troubleshooting common 9 errors,9,Top strategies for improving 9,9,[product name] pros and cons for 9,9,[product name] coupon code for 9 9,10,How small changes reveal big problems ,10,Identifying the root cause of 10,10,Solutions that actually help with 10,10,Does [product name] solve 10?,10,Buy [product name] online for 10 10,11,Things most people overlook about their daily routines ,11,Common problems people face with 11,11,Solutions that actually help with 11,11,Is [product name] worth it for 11?,11,[product name] limited-time offer for 11 11,12,Unexpected causes of frustration in your life ,12,Common problems people face with 12,12,How to solve 12 quickly,12,[product name] vs alternatives for 12,12,[product name] bonus package for 12 12,13,Why you might be struggling without realizing it ,13,Understanding the main causes of 13,13,Fast fixes for 13,13,[product name] performance on 13,13,[product name] limited-time offer for 13 13,14,Habits that might be holding you back ,14,Why is 14 causing me issues?,14,Best ways to fix 14,14,Comparison: [product name] or [competitor] for 14,14,[product name] special offer for 14 14,15,Everyday habits that cause hidden problems 15,15,Troubleshooting common 15 errors,15,Best ways to fix 15,15,[product name] pros and cons for 15,15,[product name] coupon code for 15 15,16,The silent warning signs of trouble 16,16,What to do when 16 stops working,16,Proven ways to overcome 16,16,Does [product name] solve 16?,16,[product name] coupon code for 16 16,17,The silent warning signs of trouble 17,17,Why is 17 causing me issues?,17,How to solve 17 quickly,17,Should I buy [product name] for 17?,17,[product name] special offer for 17 17,18,Why you might be struggling without realizing it 18,18,Understanding the main causes of 18,18,Fast fixes for 18,18,Why choose [product name] for 18?,18,[product name] limited-time offer for 18 18,19,The silent warning signs of trouble 19,19,Why is 19 causing me issues?,19,How to solve 19 quickly,19,[product name] user experiences for 19,19,Where to buy [product name] for 19 19,20,Why you might be struggling without realizing it 20,20,Why 20 feels harder than it should,20,Best ways to fix 20,20,[product name] performance on 20,20,[product name] bonus package for 20 20,21,Why you might be struggling without realizing it 21,21,What to do when 21 stops working,21,What works best for 21,21,[product name] performance on 21,21,[product name] bonus package for 21 21,22,Why you might be struggling without realizing it 22,22,Troubleshooting common 22 errors,22,How to solve 22 quickly,22,Honest review of [product name] for 22,22,Where to buy [product name] for 22 22,23,Signs you might have 23 issues,23,Why is 23 causing me issues?,23,Fast fixes for 23,23,[product name] vs alternatives for 23,23,Get [product name] discount for 23 23,24,Unexpected causes of frustration in your life 24,24,Fixing frequent issues with 24,24,Methods to improve 24,24,[product name] user experiences for 24,24,Lowest price on [product name] for 24 24,25,Unexpected causes of frustration in your life 25,25,When 25 becomes a problem,25,What works best for 25,25,[product name] user experiences for 25,25,Best deal on [product name] for 25 25,26,Everyday habits that cause hidden problems 26,26,Why 26 feels harder than it should,26,What works best for 26,26,[product name] performance on 26,26,[product name] limited-time offer for 26 26,27,Things most people overlook about their daily routines 27,27,Common problems people face with 27,27,Top strategies for improving 27,27,Does [product name] solve 27?,27,[product name] special offer for 27 27,28,Why you might be struggling without realizing it 28,28,Troubleshooting common 28 errors,28,Simple hacks to get better results with 28,28,[product name] vs alternatives for 28,28,Best deal on [product name] for 28 28,29,Clues you’re ignoring about 29,29,Fixing frequent issues with 29,29,Fast fixes for 29,29,[product name] pros and cons for 29,29,Best deal on [product name] for 29 29,30,Clues you’re ignoring about 30,30,How to deal with frustration from 30,30,What works best for 30,30,[product name] performance on 30,30,Best deal on [product name] for 30 30,31,Habits that might be holding you back 31,31,When 31 becomes a problem,31,Effective tools for solving 31,31,Honest review of [product name] for 31,31,Buy [product name] online for 31 31,32,Why you might be struggling without realizing it 32,32,Why is 32 causing me issues?,32,Solutions that actually help with 32,32,[product name] vs alternatives for 32,32,[product name] limited-time offer for 32 32,33,How small changes reveal big problems 33,33,Troubleshooting common 33 errors,33,Methods to improve 33,33,[product name] vs alternatives for 33,33,[product name] coupon code for 33 33,34,Things most people overlook about their daily routines 34,34,Common problems people face with 34,34,Methods to improve 34,34,[product name] pros and cons for 34,34,[product name] coupon code for 34 34,35,Signs you might have 35 issues,35,Understanding the main causes of 35,35,Methods to improve 35,35,Honest review of [product name] for 35,35,Where to buy [product name] for 35 35,36,Why you might be struggling without realizing it 36,36,Common problems people face with 36,36,How to solve 36 quickly,36,[product name] performance on 36,36,Buy [product name] online for 36 36,37,Why you feel stuck but don’t know why 37,37,Understanding the main causes of 37,37,Top strategies for improving 37,37,Honest review of [product name] for 37,37,Lowest price on [product name] for 37 37,38,Why you feel stuck but don’t know why 38,38,Why 38 feels harder than it should,38,Methods to improve 38,38,[product name] vs alternatives for 38,38,[product name] coupon code for 38 38,39,Why you feel stuck but don’t know why 39,39,Why is 39 causing me issues?,39,How to solve 39 quickly,39,Comparison: [product name] or [competitor] for 39,39,Buy [product name] online for 39 39,40,Signs you might have 40 issues,40,How to deal with frustration from 40,40,Methods to improve 40,40,Why choose [product name] for 40?,40,Lowest price on [product name] for 40 40,41,Signs you might have 41 issues,41,Why 41 feels harder than it should,41,Solutions that actually help with 41,41,Is [product name] worth it for 41?,41,[product name] free trial for 41 41,42,Signs you might have 42 issues,42,Identifying the root cause of 42,42,Solutions that actually help with 42,42,[product name] performance on 42,42,[product name] free trial for 42 42,43,Why you feel stuck but don’t know why 43,43,What to do when 43 stops working,43,What works best for 43,43,Comparison: [product name] or [competitor] for 43,43,Where to buy [product name] for 43 43,44,The silent warning signs of trouble 44,44,Why is 44 causing me issues?,44,Methods to improve 44,44,[product name] pros and cons for 44,44,Lowest price on [product name] for 44 44,45,Clues you’re ignoring about 45,45,Troubleshooting common 45 errors,45,Best ways to fix 45,45,[product name] vs alternatives for 45,45,Where to buy [product name] for 45 45,46,Clues you’re ignoring about 46,46,Understanding the main causes of 46,46,Best ways to fix 46,46,Honest review of [product name] for 46,46,Where to buy [product name] for 46 46,47,Signs you might have 47 issues,47,What to do when 47 stops working,47,Best ways to fix 47,47,[product name] pros and cons for 47,47,Lowest price on [product name] for 47 47,48,Habits that might be holding you back 48,48,What to do when 48 stops working,48,What works best for 48,48,Is [product name] worth it for 48?,48,[product name] bonus package for 48 48,49,Things most people overlook about their daily routines 49,49,Common problems people face with 49,49,How to solve 49 quickly,49,Does [product name] solve 49?,49,Best deal on [product name] for 49 49,50,The silent warning signs of trouble 50,50,Fixing frequent issues with 50,50,Fast fixes for 50,50,Is [product name] worth it for 50?,50,Where to buy [product name] for 50 50,51,The silent warning signs of trouble 51,51,Understanding the main causes of 51,51,Top strategies for improving 51,51,[product name] user experiences for 51,51,Buy [product name] online for 51 51,52,Why you feel stuck but don’t know why 52,52,Troubleshooting common 52 errors,52,Solutions that actually help with 52,52,Is [product name] worth it for 52?,52,Get [product name] discount for 52 52,53,Why you might be struggling without realizing it 53,53,What to do when 53 stops working,53,Solutions that actually help with 53,53,[product name] performance on 53,53,Best deal on [product name] for 53 53,54,How small changes reveal big problems 54,54,Common problems people face with 54,54,Fast fixes for 54,54,[product name] pros and cons for 54,54,[product name] limited-time offer for 54 54,55,How small changes reveal big problems 55,55,Troubleshooting common 55 errors,55,What works best for 55,55,Should I buy [product name] for 55?,55,Lowest price on [product name] for 55 55,56,Why you might be struggling without realizing it 56,56,Common problems people face with 56,56,What works best for 56,56,Does [product name] solve 56?,56,Best deal on [product name] for 56 56,57,Why you feel stuck but don’t know why 57,57,Common problems people face with 57,57,How to solve 57 quickly,57,[product name] user experiences for 57,57,Get [product name] discount for 57 57,58,Unexpected causes of frustration in your life 58,58,Understanding the main causes of 58,58,Simple hacks to get better results with 58,58,[product name] pros and cons for 58,58,Where to buy [product name] for 58 58,59,Signs you might have 59 issues,59,What to do when 59 stops working,59,Best ways to fix 59,59,[product name] performance on 59,59,Where to buy [product name] for 59 59,60,Why you feel stuck but don’t know why 60,60,Fixing frequent issues with 60,60,Fast fixes for 60,60,Comparison: [product name] or [competitor] for 60,60,[product name] special offer for 60 60,61,How small changes reveal big problems 61,61,Troubleshooting common 61 errors,61,Methods to improve 61,61,[product name] performance on 61,61,Best deal on [product name] for 61 61,62,Things most people overlook about their daily routines 62,62,Understanding the main causes of 62,62,Top strategies for improving 62,62,Does [product name] solve 62?,62,[product name] limited-time offer for 62 62,63,Everyday habits that cause hidden problems 63,63,Identifying the root cause of 63,63,Methods to improve 63,63,Is [product name] worth it for 63?,63,Best deal on [product name] for 63 63,64,Why you feel stuck but don’t know why 64,64,Common problems people face with 64,64,What works best for 64,64,Honest review of [product name] for 64,64,[product name] free trial for 64 64,65,Why you feel stuck but don’t know why 65,65,Common problems people face with 65,65,What works best for 65,65,[product name] vs alternatives for 65,65,[product name] free trial for 65 65,66,Things most people overlook about their daily routines 66,66,How to deal with frustration from 66,66,Methods to improve 66,66,Should I buy [product name] for 66?,66,[product name] limited-time offer for 66 66,67,Everyday habits that cause hidden problems 67,67,How to deal with frustration from 67,67,Methods to improve 67,67,[product name] performance on 67,67,[product name] special offer for 67 67,68,Habits that might be holding you back 68,68,Understanding the main causes of 68,68,Methods to improve 68,68,Does [product name] solve 68?,68,[product name] coupon code for 68 68,69,How small changes reveal big problems 69,69,Fixing frequent issues with 69,69,Solutions that actually help with 69,69,Comparison: [product name] or [competitor] for 69,69,[product name] bonus package for 69 69,70,Signs you might have 70 issues,70,How to deal with frustration from 70,70,Simple hacks to get better results with 70,70,Is [product name] worth it for 70?,70,Where to buy [product name] for 70 70,71,How small changes reveal big problems 71,71,Why is 71 causing me issues?,71,Methods to improve 71,71,[product name] pros and cons for 71,71,Where to buy [product name] for 71 71,72,Why you might be struggling without realizing it 72,72,What to do when 72 stops working,72,Fast fixes for 72,72,[product name] pros and cons for 72,72,[product name] special offer for 72 72,73,Why you might be struggling without realizing it 73,73,How to deal with frustration from 73,73,How to solve 73 quickly,73,Comparison: [product name] or [competitor] for 73,73,[product name] limited-time offer for 73 73,74,The silent warning signs of trouble 74,74,Why is 74 causing me issues?,74,Fast fixes for 74,74,[product name] user experiences for 74,74,Get [product name] discount for 74 74,75,Why you might be struggling without realizing it 75,75,Troubleshooting common 75 errors,75,Effective tools for solving 75,75,Should I buy [product name] for 75?,75,[product name] bonus package for 75 75,76,Things most people overlook about their daily routines 76,76,Understanding the main causes of 76,76,Simple hacks to get better results with 76,76,Does [product name] solve 76?,76,[product name] bonus package for 76 76,77,Everyday habits that cause hidden problems 77,77,Common problems people face with 77,77,Best ways to fix 77,77,Should I buy [product name] for 77?,77,[product name] special offer for 77 77,78,The silent warning signs of trouble 78,78,What to do when 78 stops working,78,Best ways to fix 78,78,Honest review of [product name] for 78,78,Best deal on [product name] for 78 78,79,The silent warning signs of trouble 79,79,What to do when 79 stops working,79,Top strategies for improving 79,79,Honest review of [product name] for 79,79,Lowest price on [product name] for 79 79,80,Signs you might have 80 issues,80,Understanding the main causes of 80,80,Best ways to fix 80,80,Honest review of [product name] for 80,80,[product name] limited-time offer for 80 80,81,The silent warning signs of trouble 81,81,Why 81 feels harder than it should,81,Solutions that actually help with 81,81,[product name] user experiences for 81,81,[product name] free trial for 81 81,82,Things most people overlook about their daily routines 82,82,Why 82 feels harder than it should,82,Top strategies for improving 82,82,Why choose [product name] for 82?,82,Buy [product name] online for 82 82,83,Unexpected causes of frustration in your life 83,83,Common problems people face with 83,83,What works best for 83,83,Why choose [product name] for 83?,83,Where to buy [product name] for 83 83,84,Clues you’re ignoring about 84,84,Common problems people face with 84,84,Solutions that actually help with 84,84,Comparison: [product name] or [competitor] for 84,84,[product name] limited-time offer for 84 84,85,Habits that might be holding you back 85,85,Identifying the root cause of 85,85,Solutions that actually help with 85,85,[product name] vs alternatives for 85,85,[product name] free trial for 85 85,86,Clues you’re ignoring about 86,86,What to do when 86 stops working,86,What works best for 86,86,[product name] user experiences for 86,86,Buy [product name] online for 86 86,87,Why you might be struggling without realizing it 87,87,Why 87 feels harder than it should,87,Methods to improve 87,87,Is [product name] worth it for 87?,87,[product name] free trial for 87 87,88,Habits that might be holding you back 88,88,Common problems people face with 88,88,Fast fixes for 88,88,[product name] performance on 88,88,Buy [product name] online for 88 88,89,The silent warning signs of trouble 89,89,Fixing frequent issues with 89,89,Solutions that actually help with 89,89,Does [product name] solve 89?,89,[product name] free trial for 89 89,90,Things most people overlook about their daily routines 90,90,When 90 becomes a problem,90,Methods to improve 90,90,[product name] pros and cons for 90,90,Best deal on [product name] for 90 90,91,Everyday habits that cause hidden problems 91,91,Fixing frequent issues with 91,91,Best ways to fix 91,91,Comparison: [product name] or [competitor] for 91,91,[product name] special offer for 91 91,92,The silent warning signs of trouble 92,92,Fixing frequent issues with 92,92,Top strategies for improving 92,92,[product name] user experiences for 92,92,Get [product name] discount for 92 92,93,Unexpected causes of frustration in your life 93,93,Fixing frequent issues with 93,93,What works best for 93,93,Is [product name] worth it for 93?,93,Best deal on [product name] for 93 93,94,Habits that might be holding you back 94,94,When 94 becomes a problem,94,Proven ways to overcome 94,94,Why choose [product name] for 94?,94,[product name] limited-time offer for 94 94,95,Everyday habits that cause hidden problems 95,95,What to do when 95 stops working,95,Best ways to fix 95,95,[product name] performance on 95,95,[product name] limited-time offer for 95 95,96,The silent warning signs of trouble 96,96,Understanding the main causes of 96,96,How to solve 96 quickly,96,Why choose [product name] for 96?,96,Where to buy [product name] for 96 96,97,Habits that might be holding you back 97,97,When 97 becomes a problem,97,What works best for 97,97,[product name] user experiences for 97,97,Get [product name] discount for 97 97,98,How small changes reveal big problems 98,98,Understanding the main causes of 98,98,Effective tools for solving 98,98,[product name] pros and cons for 98,98,[product name] bonus package for 98 98,99,Why you feel stuck but don’t know why 99,99,What to do when 99 stops working,99,Solutions that actually help with 99,99,Comparison: [product name] or [competitor] for 99,99,[product name] special offer for 99 99,100,How small changes reveal big problems 100,100,Why 100 feels harder than it should,100,Proven ways to overcome 100,100,Comparison: [product name] or [competitor] for 100,100,Best deal on [product name] for 100

Next exported source segment

,# Unaware,# Problem Aware,# Solution Aware,# Product Aware,# Most Aware 0,1. How to find your motivation again,1. Best ways to manage chronic stress,1. Top diets for healthy weight loss,1. Is Noom worth it for weight loss?,1. Sign up for Calm app annual plan 1,2. What causes lack of focus in daily life,2. How to get better sleep every night,2. Time management tools for professionals,2. Customer reviews of Peloton bikes,2. Get ClickUp Pro for 50% off today 2,3. Tips for boosting confidence naturally,3. Why your diet isn't working anymore,3. Best courses for learning digital marketing,3. Best features of ClickUp for teams,3. Order Noom subscription now 3,4. Why you can't stick to new habits,4. How to communicate better with your partner,4. Ways to save money on monthly bills,4. Pros and cons of Shopify stores,4. Join Audible Premium with free trial 4,5. How stress impacts your productivity,5. Ways to improve your work-life balance,5. Top meditation apps for beginners,5. What users say about Audible Premium,5. Purchase best-rated standing desk 5,6. Signs you're ready for a life change,6. How to overcome financial anxiety,6. Best online workout programs,6. Top-rated standing desks on Amazon,6. Sign up for Shopify free trial 6,7. Why time slips away without progress,7. Tips for building healthier relationships,7. Affordable meal plans for families,7. Best-selling planners for productivity,7. Order HelloFresh meal kit delivery 7,8. Daily routines that kill creativity,8. How to manage time with a busy schedule,8. Tools for improving personal finance,8. Customer feedback on HelloFresh meals,8. Download top productivity planner 8,9. How small choices shape your future,9. Signs of burnout and how to recover,9. Best home workout equipment,9. Comparison of iPhone vs. Samsung Galaxy,9. Buy Samsung Galaxy S25 Ultra now 9,10. Why you feel stuck but don't know why,10. How to stop feeling overwhelmed at work,10. Best productivity apps for busy people,10. Review of the Calm meditation app,10. Buy Peloton bike with free shipping 10,11. How to find your motivation again,11. Best ways to manage chronic stress,11. Top diets for healthy weight loss,11. Is Noom worth it for weight loss?,11. Sign up for Calm app annual plan 11,12. What causes lack of focus in daily life,12. How to get better sleep every night,12. Time management tools for professionals,12. Customer reviews of Peloton bikes,12. Get ClickUp Pro for 50% off today 12,13. Tips for boosting confidence naturally,13. Why your diet isn't working anymore,13. Best courses for learning digital marketing,13. Best features of ClickUp for teams,13. Order Noom subscription now 13,14. Why you can't stick to new habits,14. How to communicate better with your partner,14. Ways to save money on monthly bills,14. Pros and cons of Shopify stores,14. Join Audible Premium with free trial 14,15. How stress impacts your productivity,15. Ways to improve your work-life balance,15. Top meditation apps for beginners,15. What users say about Audible Premium,15. Purchase best-rated standing desk 15,16. Signs you're ready for a life change,16. How to overcome financial anxiety,16. Best online workout programs,16. Top-rated standing desks on Amazon,16. Sign up for Shopify free trial 16,17. Why time slips away without progress,17. Tips for building healthier relationships,17. Affordable meal plans for families,17. Best-selling planners for productivity,17. Order HelloFresh meal kit delivery 17,18. Daily routines that kill creativity,18. How to manage time with a busy schedule,18. Tools for improving personal finance,18. Customer feedback on HelloFresh meals,18. Download top productivity planner 18,19. How small choices shape your future,19. Signs of burnout and how to recover,19. Best home workout equipment,19. Comparison of iPhone vs. Samsung Galaxy,19. Buy Samsung Galaxy S25 Ultra now 19,20. Why you feel stuck but don't know why,20. How to stop feeling overwhelmed at work,20. Best productivity apps for busy people,20. Review of the Calm meditation app,20. Buy Peloton bike with free shipping 20,21. How to find your motivation again,21. Best ways to manage chronic stress,21. Top diets for healthy weight loss,21. Is Noom worth it for weight loss?,21. Sign up for Calm app annual plan 21,22. What causes lack of focus in daily life,22. How to get better sleep every night,22. Time management tools for professionals,22. Customer reviews of Peloton bikes,22. Get ClickUp Pro for 50% off today 22,23. Tips for boosting confidence naturally,23. Why your diet isn't working anymore,23. Best courses for learning digital marketing,23. Best features of ClickUp for teams,23. Order Noom subscription now 23,24. Why you can't stick to new habits,24. How to communicate better with your partner,24. Ways to save money on monthly bills,24. Pros and cons of Shopify stores,24. Join Audible Premium with free trial 24,25. How stress impacts your productivity,25. Ways to improve your work-life balance,25. Top meditation apps for beginners,25. What users say about Audible Premium,25. Purchase best-rated standing desk 25,26. Signs you're ready for a life change,26. How to overcome financial anxiety,26. Best online workout programs,26. Top-rated standing desks on Amazon,26. Sign up for Shopify free trial 26,27. Why time slips away without progress,27. Tips for building healthier relationships,27. Affordable meal plans for families,27. Best-selling planners for productivity,27. Order HelloFresh meal kit delivery 27,28. Daily routines that kill creativity,28. How to manage time with a busy schedule,28. Tools for improving personal finance,28. Customer feedback on HelloFresh meals,28. Download top productivity planner 28,29. How small choices shape your future,29. Signs of burnout and how to recover,29. Best home workout equipment,29. Comparison of iPhone vs. Samsung Galaxy,29. Buy Samsung Galaxy S25 Ultra now 29,30. Why you feel stuck but don't know why,30. How to stop feeling overwhelmed at work,30. Best productivity apps for busy people,30. Review of the Calm meditation app,30. Buy Peloton bike with free shipping 30,31. How to find your motivation again,31. Best ways to manage chronic stress,31. Top diets for healthy weight loss,31. Is Noom worth it for weight loss?,31. Sign up for Calm app annual plan 31,32. What causes lack of focus in daily life,32. How to get better sleep every night,32. Time management tools for professionals,32. Customer reviews of Peloton bikes,32. Get ClickUp Pro for 50% off today 32,33. Tips for boosting confidence naturally,33. Why your diet isn't working anymore,33. Best courses for learning digital marketing,33. Best features of ClickUp for teams,33. Order Noom subscription now 33,34. Why you can't stick to new habits,34. How to communicate better with your partner,34. Ways to save money on monthly bills,34. Pros and cons of Shopify stores,34. Join Audible Premium with free trial 34,35. How stress impacts your productivity,35. Ways to improve your work-life balance,35. Top meditation apps for beginners,35. What users say about Audible Premium,35. Purchase best-rated standing desk 35,36. Signs you're ready for a life change,36. How to overcome financial anxiety,36. Best online workout programs,36. Top-rated standing desks on Amazon,36. Sign up for Shopify free trial 36,37. Why time slips away without progress,37. Tips for building healthier relationships,37. Affordable meal plans for families,37. Best-selling planners for productivity,37. Order HelloFresh meal kit delivery 37,38. Daily routines that kill creativity,38. How to manage time with a busy schedule,38. Tools for improving personal finance,38. Customer feedback on HelloFresh meals,38. Download top productivity planner 38,39. How small choices shape your future,39. Signs of burnout and how to recover,39. Best home workout equipment,39. Comparison of iPhone vs. Samsung Galaxy,39. Buy Samsung Galaxy S25 Ultra now 39,40. Why you feel stuck but don't know why,40. How to stop feeling overwhelmed at work,40. Best productivity apps for busy people,40. Review of the Calm meditation app,40. Buy Peloton bike with free shipping 40,41. How to find your motivation again,41. Best ways to manage chronic stress,41. Top diets for healthy weight loss,41. Is Noom worth it for weight loss?,41. Sign up for Calm app annual plan 41,42. What causes lack of focus in daily life,42. How to get better sleep every night,42. Time management tools for professionals,42. Customer reviews of Peloton bikes,42. Get ClickUp Pro for 50% off today 42,43. Tips for boosting confidence naturally,43. Why your diet isn't working anymore,43. Best courses for learning digital marketing,43. Best features of ClickUp for teams,43. Order Noom subscription now 43,44. Why you can't stick to new habits,44. How to communicate better with your partner,44. Ways to save money on monthly bills,44. Pros and cons of Shopify stores,44. Join Audible Premium with free trial 44,45. How stress impacts your productivity,45. Ways to improve your work-life balance,45. Top meditation apps for beginners,45. What users say about Audible Premium,45. Purchase best-rated standing desk 45,46. Signs you're ready for a life change,46. How to overcome financial anxiety,46. Best online workout programs,46. Top-rated standing desks on Amazon,46. Sign up for Shopify free trial 46,47. Why time slips away without progress,47. Tips for building healthier relationships,47. Affordable meal plans for families,47. Best-selling planners for productivity,47. Order HelloFresh meal kit delivery 47,48. Daily routines that kill creativity,48. How to manage time with a busy schedule,48. Tools for improving personal finance,48. Customer feedback on HelloFresh meals,48. Download top productivity planner 48,49. How small choices shape your future,49. Signs of burnout and how to recover,49. Best home workout equipment,49. Comparison of iPhone vs. Samsung Galaxy,49. Buy Samsung Galaxy S25 Ultra now 49,50. Why you feel stuck but don't know why,50. How to stop feeling overwhelmed at work,50. Best productivity apps for busy people,50. Review of the Calm meditation app,50. Buy Peloton bike with free shipping 50,51. How to find your motivation again,51. Best ways to manage chronic stress,51. Top diets for healthy weight loss,51. Is Noom worth it for weight loss?,51. Sign up for Calm app annual plan 51,52. What causes lack of focus in daily life,52. How to get better sleep every night,52. Time management tools for professionals,52. Customer reviews of Peloton bikes,52. Get ClickUp Pro for 50% off today 52,53. Tips for boosting confidence naturally,53. Why your diet isn't working anymore,53. Best courses for learning digital marketing,53. Best features of ClickUp for teams,53. Order Noom subscription now 53,54. Why you can't stick to new habits,54. How to communicate better with your partner,54. Ways to save money on monthly bills,54. Pros and cons of Shopify stores,54. Join Audible Premium with free trial 54,55. How stress impacts your productivity,55. Ways to improve your work-life balance,55. Top meditation apps for beginners,55. What users say about Audible Premium,55. Purchase best-rated standing desk 55,56. Signs you're ready for a life change,56. How to overcome financial anxiety,56. Best online workout programs,56. Top-rated standing desks on Amazon,56. Sign up for Shopify free trial 56,57. Why time slips away without progress,57. Tips for building healthier relationships,57. Affordable meal plans for families,57. Best-selling planners for productivity,57. Order HelloFresh meal kit delivery 57,58. Daily routines that kill creativity,58. How to manage time with a busy schedule,58. Tools for improving personal finance,58. Customer feedback on HelloFresh meals,58. Download top productivity planner 58,59. How small choices shape your future,59. Signs of burnout and how to recover,59. Best home workout equipment,59. Comparison of iPhone vs. Samsung Galaxy,59. Buy Samsung Galaxy S25 Ultra now 59,60. Why you feel stuck but don't know why,60. How to stop feeling overwhelmed at work,60. Best productivity apps for busy people,60. Review of the Calm meditation app,60. Buy Peloton bike with free shipping 60,61. How to find your motivation again,61. Best ways to manage chronic stress,61. Top diets for healthy weight loss,61. Is Noom worth it for weight loss?,61. Sign up for Calm app annual plan 61,62. What causes lack of focus in daily life,62. How to get better sleep every night,62. Time management tools for professionals,62. Customer reviews of Peloton bikes,62. Get ClickUp Pro for 50% off today 62,63. Tips for boosting confidence naturally,63. Why your diet isn't working anymore,63. Best courses for learning digital marketing,63. Best features of ClickUp for teams,63. Order Noom subscription now 63,64. Why you can't stick to new habits,64. How to communicate better with your partner,64. Ways to save money on monthly bills,64. Pros and cons of Shopify stores,64. Join Audible Premium with free trial 64,65. How stress impacts your productivity,65. Ways to improve your work-life balance,65. Top meditation apps for beginners,65. What users say about Audible Premium,65. Purchase best-rated standing desk 65,66. Signs you're ready for a life change,66. How to overcome financial anxiety,66. Best online workout programs,66. Top-rated standing desks on Amazon,66. Sign up for Shopify free trial 66,67. Why time slips away without progress,67. Tips for building healthier relationships,67. Affordable meal plans for families,67. Best-selling planners for productivity,67. Order HelloFresh meal kit delivery 67,68. Daily routines that kill creativity,68. How to manage time with a busy schedule,68. Tools for improving personal finance,68. Customer feedback on HelloFresh meals,68. Download top productivity planner 68,69. How small choices shape your future,69. Signs of burnout and how to recover,69. Best home workout equipment,69. Comparison of iPhone vs. Samsung Galaxy,69. Buy Samsung Galaxy S25 Ultra now 69,70. Why you feel stuck but don't know why,70. How to stop feeling overwhelmed at work,70. Best productivity apps for busy people,70. Review of the Calm meditation app,70. Buy Peloton bike with free shipping 70,71. How to find your motivation again,71. Best ways to manage chronic stress,71. Top diets for healthy weight loss,71. Is Noom worth it for weight loss?,71. Sign up for Calm app annual plan 71,72. What causes lack of focus in daily life,72. How to get better sleep every night,72. Time management tools for professionals,72. Customer reviews of Peloton bikes,72. Get ClickUp Pro for 50% off today 72,73. Tips for boosting confidence naturally,73. Why your diet isn't working anymore,73. Best courses for learning digital marketing,73. Best features of ClickUp for teams,73. Order Noom subscription now 73,74. Why you can't stick to new habits,74. How to communicate better with your partner,74. Ways to save money on monthly bills,74. Pros and cons of Shopify stores,74. Join Audible Premium with free trial 74,75. How stress impacts your productivity,75. Ways to improve your work-life balance,75. Top meditation apps for beginners,75. What users say about Audible Premium,75. Purchase best-rated standing desk 75,76. Signs you're ready for a life change,76. How to overcome financial anxiety,76. Best online workout programs,76. Top-rated standing desks on Amazon,76. Sign up for Shopify free trial 76,77. Why time slips away without progress,77. Tips for building healthier relationships,77. Affordable meal plans for families,77. Best-selling planners for productivity,77. Order HelloFresh meal kit delivery 77,78. Daily routines that kill creativity,78. How to manage time with a busy schedule,78. Tools for improving personal finance,78. Customer feedback on HelloFresh meals,78. Download top productivity planner 78,79. How small choices shape your future,79. Signs of burnout and how to recover,79. Best home workout equipment,79. Comparison of iPhone vs. Samsung Galaxy,79. Buy Samsung Galaxy S25 Ultra now 79,80. Why you feel stuck but don't know why,80. How to stop feeling overwhelmed at work,80. Best productivity apps for busy people,80. Review of the Calm meditation app,80. Buy Peloton bike with free shipping 80,81. How to find your motivation again,81. Best ways to manage chronic stress,81. Top diets for healthy weight loss,81. Is Noom worth it for weight loss?,81. Sign up for Calm app annual plan 81,82. What causes lack of focus in daily life,82. How to get better sleep every night,82. Time management tools for professionals,82. Customer reviews of Peloton bikes,82. Get ClickUp Pro for 50% off today 82,83. Tips for boosting confidence naturally,83. Why your diet isn't working anymore,83. Best courses for learning digital marketing,83. Best features of ClickUp for teams,83. Order Noom subscription now 83,84. Why you can't stick to new habits,84. How to communicate better with your partner,84. Ways to save money on monthly bills,84. Pros and cons of Shopify stores,84. Join Audible Premium with free trial 84,85. How stress impacts your productivity,85. Ways to improve your work-life balance,85. Top meditation apps for beginners,85. What users say about Audible Premium,85. Purchase best-rated standing desk 85,86. Signs you're ready for a life change,86. How to overcome financial anxiety,86. Best online workout programs,86. Top-rated standing desks on Amazon,86. Sign up for Shopify free trial 86,87. Why time slips away without progress,87. Tips for building healthier relationships,87. Affordable meal plans for families,87. Best-selling planners for productivity,87. Order HelloFresh meal kit delivery 87,88. Daily routines that kill creativity,88. How to manage time with a busy schedule,88. Tools for improving personal finance,88. Customer feedback on HelloFresh meals,88. Download top productivity planner 88,89. How small choices shape your future,89. Signs of burnout and how to recover,89. Best home workout equipment,89. Comparison of iPhone vs. Samsung Galaxy,89. Buy Samsung Galaxy S25 Ultra now 89,90. Why you feel stuck but don't know why,90. How to stop feeling overwhelmed at work,90. Best productivity apps for busy people,90. Review of the Calm meditation app,90. Buy Peloton bike with free shipping 90,91. How to find your motivation again,91. Best ways to manage chronic stress,91. Top diets for healthy weight loss,91. Is Noom worth it for weight loss?,91. Sign up for Calm app annual plan 91,92. What causes lack of focus in daily life,92. How to get better sleep every night,92. Time management tools for professionals,92. Customer reviews of Peloton bikes,92. Get ClickUp Pro for 50% off today 92,93. Tips for boosting confidence naturally,93. Why your diet isn't working anymore,93. Best courses for learning digital marketing,93. Best features of ClickUp for teams,93. Order Noom subscription now 93,94. Why you can't stick to new habits,94. How to communicate better with your partner,94. Ways to save money on monthly bills,94. Pros and cons of Shopify stores,94. Join Audible Premium with free trial 94,95. How stress impacts your productivity,95. Ways to improve your work-life balance,95. Top meditation apps for beginners,95. What users say about Audible Premium,95. Purchase best-rated standing desk 95,96. Signs you're ready for a life change,96. How to overcome financial anxiety,96. Best online workout programs,96. Top-rated standing desks on Amazon,96. Sign up for Shopify free trial 96,97. Why time slips away without progress,97. Tips for building healthier relationships,97. Affordable meal plans for families,97. Best-selling planners for productivity,97. Order HelloFresh meal kit delivery 97,98. Daily routines that kill creativity,98. How to manage time with a busy schedule,98. Tools for improving personal finance,98. Customer feedback on HelloFresh meals,98. Download top productivity planner 98,99. How small choices shape your future,99. Signs of burnout and how to recover,99. Best home workout equipment,99. Comparison of iPhone vs. Samsung Galaxy,99. Buy Samsung Galaxy S25 Ultra now 99,100. Why you feel stuck but don't know why,100. How to stop feeling overwhelmed at work,100. Best productivity apps for busy people,100. Review of the Calm meditation app,100. Buy Peloton bike with free shipping

Clickable sources and resources

Keyword Planner metric definitions

Quality Matters higher-education rubric

W3C WCAG 2.2

W3C new criteria in WCAG 2.2

Google search guidance for AI features

ClickFunnels education

Acquisition.com education

Read the assigned source

Turn an industry trend into a measured business experiment

Source: D0015, Niche Industry Trends SOP. Assigned lessons: 01.1, 01.3, 07.1, 11.2, and 12.2.

Follow the five-step procedure

First, define the industry segments, external influences, and research objective. The source gives innovation, changes in consumer behavior, and technology adoption as examples. Specify how you will measure the effect before gathering a large collection of trend stories.

Second, research the trend through market reports, trade publications, competitors, industry voices, webinars, customer surveys, social conversations, and analytics. Keep the distinction between a reported opinion, an observed behavior, and an inference. Third, assess impact, feasibility, and alignment with the business. Pilot the promising possibility and turn the findings into an adoption roadmap with named actions.

Fourth, integrate a validated change into the relevant marketing, product, or sales work. Train the people responsible and monitor the result after implementation. Fifth, review the data, collect customer and stakeholder feedback, and adjust as the trend develops. The intended benefits are earlier recognition of change, better-informed decisions, and useful innovation; the procedure does not guarantee that every prediction is correct.

Assign responsibilities and train the team

The market research analyst compiles trends. The marketing strategist connects them to campaigns and brand work. The product lead evaluates product changes. Sales and business development adjust the commercial approach. The data analyst measures effectiveness and return. One person can hold several roles, but each responsibility needs an owner.

The source's training schedule allocates two hours to identification with the research analyst, two to validation and feasibility with the data analyst, three to implementation with marketing and product leads, and two to monitoring and optimization with the business-development lead. That totals nine hours. Use it as the supplied training plan rather than claiming every team will finish in that time.

Review quality and avoid trend chasing

Check that research identified the trend, customer and other evidence validated it, an integration plan exists, performance measures are defined, and a feedback loop supports revision. The suggested outcomes are customer engagement, brand positioning or authority, product adoption, revenue, and time to market. Define the baseline and measurement period for each. Track long-term return as well as the first response.

The source warns against acting without validation, funding a short-lived fad, and ignoring customer feedback. Test at a small scale, maintain a trend dashboard, connect changes to business strengths and long-term strategy, and hold recurring review meetings. Its explicit ongoing recommendation is quarterly analysis, supplemented by industry conversations and possible AI-assisted prediction. Forecasts remain hypotheses, and quarterly review should not prevent an earlier response to strong contrary evidence.

Understand the tool list

The source lists Statista, IBISWorld, and McKinsey Insights for market research; Google Trends, Exploding Topics, and TrendWatching for trends; Brandwatch, Sprout Social, and BuzzSumo for social listening; SEMrush, Ahrefs, and SimilarWeb for competitors; and Google Analytics, Tableau, and Power BI for measurement. It also references McKinsey reports, Google Trends data, and a HubSpot research guide. These are source examples, not a requirement to buy them or a verification of current capabilities.

Apply the procedure to the current lesson's work: market choice, evidence gathering, content, member value, or operating decisions. Keep a record of the hypothesis, pilot, adoption decision, owner, measure, and review date. This makes a trend useful only when it produces evidence that improves the business.

Establish the brand core, identity, and voice

This SOP aims for recognition, consistency, customer trust and loyalty, continued relevance, and stronger competitive positioning. These are outcomes to measure, not guaranteed benefits. Begin by documenting mission, vision, values, a distinctive selling proposition, and a manifesto describing the long-term direction.

For this curriculum, use RISER NATION CORP and the established line “IF YOU AREN'T BUILDING, YOU ARE DESTROYING.” Translate that message into a concrete commitment to useful action and customer progress. Keep the approved visual identity in a style guide covering colors, typography, logo use, and templates for social posts, presentations, and marketing materials.

Choose a clear personality—authoritative, friendly, or innovative are the source examples—and define how it sounds in real sentences. Document three messaging pillars: the core message explaining who the organization is and what it stands for; concise taglines and slogans; and a storytelling approach that can evolve while remaining truthful. Brunson-style stories should reinforce the offer and customer journey; Hormozi-style clarity should make the promised value understandable and supportable.

Implement awareness, adaptability, and customer feedback

Build a content plan across blogs, social media, and video. Consider suitable influencers and strategic collaborators, and make social participation useful through engagement. Research industry changes continually. Preserve core values while adapting products, presentation, and methods; avoid confusing consistency with refusal to improve.

Develop loyalty experiences and appropriate personalization. Listen to customer sentiment and brand perceptions, then route that feedback into improvements to delivery. The customer experience should substantiate the story. The source also calls for trademark and copyright protection of brand assets. Record asset ownership and permissions and route protection questions to the relevant process; this lesson does not establish that any registration or legal protection has been completed.

Assign ownership and training

This is a proposed 10-hour training schedule, not a record of completed training. One person may hold several roles, but each responsibility needs an owner.

The source's tool inventory is Canva, Adobe Illustrator, and Figma for design; Buffer, Hootsuite, Later, and Sprout Social for content/social management; HubSpot, Zendesk, and Typeform for customer engagement; Google Trends, SEMrush, Ahrefs, and Nielsen Reports for research; and Brandwatch, Mention, and Google Alerts for monitoring. These names are retained as source examples, without asserting current features, pricing, or a requirement to buy them.

Audit consistency and decide what to change

Track recognition/awareness, retention and repeat business, social/community engagement, and sentiment/perception. Define each measure, its baseline, the reporting window, and the owner; the SOP supplies no numerical targets or formulas. Ask whether identity is clear, consistent, and distinctive; voice is defined; all customer touchpoints reflect it; adaptations have been tested; and metrics are reviewed quarterly.

The body specifies quarterly audits, while the final recommendations specify annual audits. Preserve both through quarterly operating checks and an annual strategic review; this combined cadence is our implementation interpretation of the two source instructions. Neither schedule is evidence that an audit already happened.

Avoid unclear identity or differentiation, frequent unnecessary rebrands, ignoring feedback, and failing to adapt to real market changes. Use truthful, consistent storytelling; refresh visuals and messages when evidence warrants it; engage willing advocates and loyal customers; and monitor competitor developments for opportunities. Maintain a change log explaining what changed and why.

The source names Harvard Business Review's “Building a Brand That Lasts,” a Forbes long-term brand growth guide, Seth Godin branding principles, and HubSpot's branding framework. No specific links or full texts accompany those references; they are additional reading leads, not incorporated source content. Finish with the brand core, style/voice guide, role assignments, training plan, dashboard, and audit schedule.

Use the complete buyer and seller example library

The assigned Buyer/Seller Personas document provides 50 buyer examples and 50 seller examples. These are hypothetical categories and stated preferences, not verified profiles of individual people. Several categories overlap: a remote worker might also seek a condo, and a landlord might also be relocating. Do not count overlapping labels as separate market sizes or infer a person's needs from age, family status, origin, disability, income, or a neighborhood label.

Read each row as a prompt for a conversation about an expressed need. Ask the customer what property features, timing, budget, service, or transaction constraints matter to them. Record their answer rather than assigning needs from a stereotype. The complete source descriptions below are retained to make the examples reviewable; they are not instructions for excluding people from housing opportunities or directing people toward particular neighborhoods based on personal characteristics.

Buyer examples: all 50 source rows

Seller examples: all 50 source rows

Convert a label into an evidence-backed service need

Choose a buyer row and a seller row. For a buyer interested in a home office, ask about actual workspace and connectivity requirements; do not assume every remote worker wants the same property. For an out-of-state seller, ask about scheduling, access, communication, and their actual decision process. These interview prompts are teaching additions, not missing rows from the document.

For each case, record the customer's own words, the desired outcome, current alternatives, budget or payer, timing, constraints, and evidence still missing. Use the existing Brunson customer-message work to make the communication specific and the Hormozi offer work to connect the service to a measurable improvement. A preference label alone does not prove urgency, affordability, profitability, or willingness to buy.

The source ends with an empty search-comparison header: “INCOGNITO GOOGLE PREDICT,” seven unnamed columns, and a normal-account Google auto-predict column with spelling errors. It contains no query rows or results. Preserve that absence: there is no supplied comparison proving how incognito and signed-in predictions differ. If a new comparison is conducted, record the query, date, settings, and observed results as new research rather than filling the blank with invented historical data.

Submit the two researched profiles and the supporting customer evidence. Keep all 100 examples available as the lesson's reference table, and distinguish this generic library from a completed, validated avatar.

Etsy category library: connect buying reasons to a testable product

This document lists 15 numbered category groups and three subcategories per group. Each subcategory supplies three pain points or reasons to buy and three proposed solutions: 45 subcategories, 135 reasons, and 135 solution ideas. Treat the list as a product-research starting point, not proof of Etsy's current category structure or customer demand. “Digital Products” appears twice, in groups 8 and 14, with distinct subcategories; both are preserved.

Teach the relationship before choosing a solution

A desire for uniqueness, a deadline, a fit problem, a material preference, and a low budget imply different product requirements. Ask the customer to describe a recent purchase or failed attempt. Identify which reason mattered, which constraint blocked a purchase, and what a satisfactory result would look like. The three reasons and three solutions in each source group are lists, not explicit one-to-one matches; do not silently claim that the first solution solves only the first reason.

For each subcategory below, evaluate every supplied reason against the proposed solutions. Mark a supported match, an assumption to test, or a mismatch. Then make or show a small sample and check the relevant dimensions, instructions, materials, editing needs, or delivery requirements. For a physical item, include production, packaging, shipping, and returns in the test economics. For a digital item, include file usability, support, and the customer's equipment or software requirements.

Brunson's positioning connection helps explain why a particular customer would choose this version. Hormozi's value connection helps define the desired result, credible evidence, time, and effort. Neither framework makes a “natural,” “safe,” “rare,” “affordable,” or “eco-friendly” claim true without evidence. The source supplies no tested products, suppliers, pricing, demand measurements, current platform policies, or underlying creative assets.

Retain and evaluate every category group

1. Art & Collectibles

Teaching action: For art and collectibles, test uniqueness, personalization, affordability, and availability separately. Show an actual sample and record whether the buyer wants a download, a commission, or a physical object.

2. Jewelry

Teaching action: For jewelry, clarify size, personalization, occasion, and material requirements before preparing a sample. Terms such as hypoallergenic need substantiation; the list itself supplies none.

3. Home & Living

Teaching action: For home goods, ask where and how the item will be used. Test dimensions, customization, coordination, and maintenance; do not assume an eco-friendly label explains the actual material or impact.

4. Clothing & Shoes

Teaching action: For clothing and shoes, test fit, comfort, material information, and production constraints with a sample. Handmade, vegan, organic, and sustainable are source descriptors rather than verified certifications.

5. Weddings

Teaching action: For weddings, start with the date, theme, quantity, editing needs, and delivery deadline. Check whether a digital template or physical item actually reduces the buyer’s coordination burden.

6. Craft Supplies & Tools

Teaching action: For craft supplies, identify the maker’s skill level and equipment, then test whether the kit or file contains everything needed for the stated project.

7. Toys & Entertainment

Teaching action: For toys and entertainment, identify the intended age and use. Test instructions and durability, and keep safety claims separate from the source’s unsupported descriptions.

8. Digital Products

Teaching action: For the first digital-products group, test print quality, editability, file compatibility, and the customer’s actual tool. An instant download still needs clear instructions.

9. Baby & Kids

Teaching action: For baby and kids products, clarify age, size, use, and caregiver expectations. The source’s non-toxic and baby-safe wording is not a completed safety assessment.

10. Vintage

Teaching action: For vintage items, verify the item’s identity, condition, provenance, and restoration description. Scarcity, authenticity, and sustainability cannot be established by a brainstorming label.

11. Bath & Beauty

Teaching action: For bath and beauty, separate preference for a scent or texture from claims about sensitivity, anxiety, or allergies. The source supplies no product formulation or evidence of health effects.

12. Pets

Teaching action: For pet products, identify the animal’s size, behavior, intended use, and care needs. Test the physical product appropriately; durable, hypoallergenic, and non-toxic are not established by this list.

13. Outdoor & Garden

Teaching action: For outdoor and garden products, identify weather, space, handling, and maintenance requirements. Test the stated physical properties rather than assuming weatherproof or biodegradable performance.

14. Digital Products

Teaching action: For the second digital-products group, test whether the branding, wedding, or educational template can be edited and used for the exact task. Keep it separate from group 8 so its distinct examples remain visible.

15. Books, Movies & Music

Teaching action: For books, music, and movie-related products, distinguish original creation, collectible resale, and reuse of existing content. Verify the actual assets and permissions before promising a bundle, playlist, poster, or printable.

Complete a product-choice brief

Choose one subcategory and retain all three reasons and all three proposed solutions in the brief. Record which relationships you will test, the sample or demonstration, the customer's feedback, expected delivery work, unresolved claims, and your continue/revise/stop decision. This is a test plan, not an instruction to list an unverified product. If the current assigned lesson concerns community or content, use the same evidence to choose a useful discussion or demonstration topic rather than assuming a marketplace item automatically supports recurring membership value.

The full source lists remain here for review, with the complete source text separately retained in the assigned appendix. This adaptation covers the available text; it does not certify unseen images, linked assets, or a current live marketplace taxonomy.

The vanity-metric test: every dashboard number needs a decision

Ask the source's central question: when this metric moves, what specific decision changes? If you cannot name a decision, move the number from the operating dashboard to the audit log. This is a prioritization discipline. You retain useful history while keeping the dashboard focused on action.

Keep the source's measurement context

This M16.3 excerpt belongs to C16, Customer LTV & Measurement Discipline: Stage 4 Yacht, Build to Scale, C15 funnel deployed prerequisite, ten to fourteen hours over two weeks. The schedule is duplicated in the source, not additive. These older course references do not renumber the current workbook. The source says the master syllabus remains unchanged; this excerpt does not supply the entire LTV architecture.

Its parent-course principle contrasts aggregate structural rates with granular customer surveillance and contrasts decision-driving dashboards with vanity dashboards. Apply that principle by measuring service and funnel patterns needed for an operating decision, rather than collecting personal detail merely because it is available. The excerpt supplies no full LTV formula, benchmark, or technical tracking implementation.

Use an explicitly adapted three-question test

The source names a three-question test but provides only its central decision question. These three questions are a RISER operational adaptation, not the missing original wording.

1. What decision does this number inform, and who owns that decision?
2. What direction or condition would trigger an action, over which time window and with which minimum evidence?
3. What will the owner do, and when will the team check whether that action helped?

Attach a decision-trigger record: metric definition, numerator and denominator where applicable, period, owner, trigger condition, action, review date, and limitations. Choose thresholds from the operating context and evidence; the excerpt supplies no universal numerical trigger.

Demonstrate a decision-driving metric

Imagine tracking the proportion of new members who complete the first lesson within a defined week. The denominator must identify the eligible cohort and the numerator must use the same completion definition each time. If a meaningful change occurs, the owner could inspect the onboarding instructions and test a clearer first step. Record the change, cohort size, and result before claiming the test helped. This is an illustrative operating example, not a source-supplied benchmark or measured RISER result.

Follower count can be relevant to a specific distribution decision, but a rising number with no defined action fails this dashboard test. Move it to the audit log with its definition, period, and reason for migration. Migration does not mean deletion or proof that the number can never matter again. Restore it when a real decision requires it.

Connect the funnel lesson to Brunson by checking movement between meaningful steps. Connect the Hormozi lens by testing whether outcomes, delivery effort, and customer value improve rather than celebrating activity alone. Submit a dashboard in which each retained metric has an owner and decision trigger, plus an audit log identifying the migrated measures. This exercises every supplied module requirement without implying the absent LTV system has been reconstructed.

Interpret customer reviews while separating evidence from simulation

The template names the assistant Voice of the Buyer Analyst and proposes analysis of Amazon, Trustpilot, Reddit or G2 reviews for advertising, landing pages, email and product R&D. Its “trained psychology analyst” persona is a writing specification, not a credential or an ability to know hidden emotions.

Supply up to thirty raw reviews as text or JSON objects with review_text fields. Optionally include the offer description and choose neutral, emotional or persuasive tone. Preserve review IDs, sources, dates and relevant context, and remove unnecessary personal data. Organize themes, identify repeated expressed language and consider both the customer's experience and possible product/message improvements.

Produce every requested output

Return up to five evidence-supported emotional pain points, up to five desired outcomes, common objections/hesitations, and the actual language used. The source's sample stems are “I was so frustrated by…,” “I just want something that…,” and “Honestly, I felt….” They are prompts, not supplied customer quotations. Cite the reviews supporting each theme and show conflicting experiences. Fewer than five supported themes should remain fewer than five.

The separate end-of-day diary begins “Another long day. I tried using [product] again and…” and uses a first-person, reflective account of the problem and desired change. Label the entire entry fictional/simulated. It may help explore a hypothesis, but it cannot uncover verified deep psychology, serve as a testimonial, or be mixed into the source-review count. No customer actually wrote it merely because it sounds realistic.

Optional enhancements are a Claude-friendly structured output, tags for possible hook/ad phrases and Make.com processing of new review batches. No automation is installed by this template. Review any proposed reuse for truthful attribution and permission, and validate generated copy against the evidence. The intended outcomes are avatar language, possible emotional triggers, copy snippets and positioning insights. Brunson/Hormozi framing should translate a documented problem into a credible promise and easier delivery. Submit the attributed analysis, clearly separate simulation, and testable product/message recommendations.

Named resource starting points

Reddit, Amazon, G2, Trustpilot, Make.com. These are navigation references to services named in the source, not researched results, current pricing endorsements, or proof of access. Add the actual evidence URLs to your completed work; unavailable assets and dated product claims remain unverified.

Read the assigned source document

Turn the market scan into observable learning

This April 24, 2026 version 2.0 specification describes legacy C3 Buoy Navigation. Its numbering is a source reference; follow the current RISER spreadsheet lesson assignment on this page. Start with evidence you can show, not a statement that you understand marketing. The six course outcomes ask you to distinguish bounded scanning from open research; create a tagged Trigger Bank; analyze adjacent operators; conduct structured interviews; evaluate three mechanism finalists; and synthesize one Market Fit Hypothesis for the next offer-design stage.

Build and assess all six outputs

1. Bounded scan. Retrieve C2 Hypothesis Section 5. Convert each uncertainty into an activity, source, deadline and decision it will inform. Explain in your own words why this is a scan with stopping conditions rather than endless research. Keep contradictory findings.
2. Trigger Bank. Collect at least 200 verbatim entries across community forums, social content, search queries and interview transcripts. Tag pain, desire, objection and language about solutions. Keep provenance and context; do not fabricate quotations or inflate the count through duplicates. A search phrase is evidence of wording, not automatically a buyer's stated purchase intent.
3. Competitor gap map. Identify five to ten adjacent operators using the named identification rubric. Compare price, positioning, proof and review sentiment. Separate observed statements from independently established outcomes. An absent feature in your search is a research gap until verified.
4. Interview library. Recruit eight to twelve people in the stated subsegment; the minimum completed count is eight. Follow the five-phase protocol, permission requirements and timecoded transcript process. Tag the job, pain triggers, forces of progress and language about solutions. The full protocol and consent script are dependencies, not reproduced by their names alone.
5. Primary selection. Apply the C2 kill criteria to all three finalists with cited verdicts. Collect at least five pricing sources: three published and two interview-reported. Compare engagement model, duration and deliverables. The proposed selection weights are 40% kill-criteria survival, 30% Trigger Bank resonance, 20% differentiation and 10% pricing. Define comparable scoring scales first; a weighted total must not rescue a candidate that fails a mandatory survival condition.
6. Market Fit Hypothesis. Combine the Primary, evidence, weaknesses and open C4 questions into one defensible document. The source says all six prior modules even though M3.8 follows seven modules; include evidence from every preceding module rather than dropping one to fit that wording.

Connect every module to its assessment

M3.1 has two outcomes: explain the distinction and apply Section 5 to a bounded plan. M3.2 covers four source categories and the 200-entry tagged artifact. M3.3 covers operator identification and analysis across four dimensions. M3.4 covers recruitment, the five-phase recorded-consent protocol and transcript tagging. M3.5 evaluates all three finalists against kill criteria. M3.6 analyzes five pricing signals and packaging patterns. M3.7 evaluates the Primary with the weighted rubric. M3.8 creates the synthesis with limitations. Their mappings are respectively CLO1, CLO2, CLO3, CLO4, CLO5, CLO5, CLO5 and CLO6. Use the complete reference below when constructing the scoring sheet so each named MLO remains visible.

The source uses Anderson and Krathwohl's revised Bloom taxonomy: Analyze, Apply, Evaluate and Create. Write an observable verb and artifact instead of understand, learn, know, appreciate, enjoy, grasp, realize, become aware, recognize, be familiar with or develop understanding. A well-written outcome still requires a fair assessment and feedback; the source's alignment claim is not an independent certification.

Evaluate transfer, not just satisfaction

The proposed Kirkpatrick checks are Level 1 reaction, with a 4.2/5 target on the statement about the scan changing thinking about the mechanism; Level 2 learning, with eight checkpoints, human review and a completion test; Level 3 behavior, with a day-30 audit of the Primary in C4 and Trigger Bank language used in copy; and Level 4 results, with the C5/Stage 1 offer surviving architecture and using that language in a shipped offer. Satisfaction does not prove learning or causation. Build 6 automation is a design reference, not an installed workflow. Collect the required artifacts and explain how each will be assessed before claiming completion.

Complete available source reference

The following preserves the available source text, including original labels, examples, file references and historical claims. Read it together with the corrections and execution steps above. Named files without supplied URLs are unresolved dependencies, not fabricated download links.

C3 Buoy Navigation — Learning Outcomes

Every outcome uses ONE measurable Bloom's verb (per Anderson & Krathwohl 2001 revised taxonomy; QM SRS 2.1 Essential). ---

Course-Level Learning Outcomes

By the end of C3 Buoy Navigation, learners will be able to: CLO-1. [Analyze] Distinguish a bounded market scan from open-ended market research by producing a scan plan that converts the C2 Mechanism Hypothesis Document's Section 5 into specific, time-bounded investigation activities. CLO-2. [Create] Produce a Trigger Bank containing a minimum of 200 verbatim audience-language entries drawn from at least 4 source categories, each entry categorized by emotional register (pain, desire, objection, language-about-solutions). CLO-3. [Analyze] Analyze 5-10 competing operators within the stated territory across pricing, positioning, proof type, and review sentiment, and produce a positioning gap map. CLO-4. [Apply] Conduct a minimum of 8 structured Jobs-To-Be-Done interviews with in-territory audience members, producing transcribed and tagged interview records. CLO-5. [Evaluate] Evaluate each of the three C2 mechanism finalists against its documented kill criteria using C3-gathered evidence, and produce a single validated Primary mechanism decision. CLO-6. [Create] Produce a Market Fit Hypothesis Document that synthesizes the Trigger Bank, competitor scan, customer interviews, pricing signals, and Primary selection into the artifact that becomes C4's primary input. ---

Module-Level Learning Outcomes

These build *up to* the course-level outcomes. No module outcome exceeds the Bloom's level of its parent course outcome.

M3.1 — Market Scan Foundations

MLO-3.1a. [Analyze] Distinguish in writing between a market scan (bounded, hypothesis-testing) and market research (open-ended, exploratory), using the student's own C2 Hypothesis Document as the hypothesis source. MLO-3.1b. [Apply] Convert Section 5 of the C2 Mechanism Hypothesis Document into a C3 scan plan listing specific activities, sources, and deadlines. *Supports CLO-1.*

M3.2 — Trigger Bank Construction

MLO-3.2a. [Apply] Collect verbatim audience-language entries from a minimum of 4 source categories (community forums, social media, search queries, interview transcripts). MLO-3.2b. [Create] Produce a Trigger Bank of ≥ 200 entries tagged by emotional register (pain / desire / objection / language-about-solutions) and by source category. *Supports CLO-2.*

M3.3 — Competitor Analysis Protocol

MLO-3.3a. [Apply] Identify 5-10 in-territory operators offering mechanisms adjacent to the student's three C2 finalists, using the Competitor Identification Rubric. MLO-3.3b. [Analyze] Analyze each competitor across four dimensions (pricing, positioning, proof type, review sentiment) and produce a comparative positioning gap map. *Supports CLO-3.*

M3.4 — Customer Interview Methodology

MLO-3.4a. [Apply] Recruit and schedule 8-12 interview participants from the student's stated audience subsegment using the Interview Outreach Script. MLO-3.4b. [Apply] Conduct structured Jobs-To-Be-Done interviews following the 5-phase interview protocol, producing recorded conversations (with consent) and time-coded transcripts. MLO-3.4c. [Apply] Tag each interview for primary job statement, pain triggers, forces-of-progress, and solution-language used by the respondent. *Supports CLO-4.*

M3.5 — Kill Criteria Evaluation

MLO-3.5. [Evaluate] Evaluate each of the three C2 finalists against its documented kill criteria using evidence from the Trigger Bank, Competitor Scan, and Customer Interviews, producing a per-finalist survival verdict with cited evidence. *Supports CLO-5.*

M3.6 — Pricing and Packaging Signals

MLO-3.6a. [Analyze] Document observed price bands for adjacent offers in the territory, drawn from a minimum of 5 sources including at least 3 published prices and 2 interview-reported prices. MLO-3.6b. [Analyze] Identify packaging patterns (engagement model, duration, deliverable structure) common in the territory and note where the student's finalists align or diverge. *Supports CLO-5.*

M3.7 — Selecting the Primary Mechanism

MLO-3.7. [Evaluate] Select the single Primary mechanism from the three C2 finalists using a documented decision rubric that weighs kill criteria survival (40%), Trigger Bank resonance (30%), competitor differentiation (20%), and pricing viability (10%). *Supports CLO-5.*

M3.8 — Market Fit Hypothesis Document

MLO-3.8. [Create] Produce a Market Fit Hypothesis Document that names the Primary mechanism, cites supporting evidence from all six prior modules, specifies known weaknesses the Primary has not yet addressed, and lists the C4 offer-architecture questions to be answered. *Supports CLO-6.* ---

Alignment Check

Per QM SRS 2.2 Essential: every module outcome explicitly supports at least one course outcome. Every course outcome has at least one module outcome contributing.

Full coverage. No gaps. ---

Kirkpatrick Evaluation Mapping

Designed backward from Level 4 (per Kirkpatrick Partners 2024).

Level 3 evaluation runs via Build 6 at day 30 post-completion. Level 4 evaluates at C5 completion. ---

Banned Verbs in C3 Outcomes

Same banned-verb list as C1 and C2: *understand* (without measurable artifact), *learn*, *know*, *appreciate*, *enjoy*, *grasp*, *realize*, *become aware*, *recognize*, *be familiar with*, *develop an understanding of*. --- *Last updated: April 24, 2026 · Version 2.0*

Clickable research and learning resources

Kirkpatrick, ClickFunnels education, Acquisition.com education. These are named-resource starting points, not verified availability of every historical feature, evidence of paid access, or current pricing recommendations. Add the exact page supporting each completed research finding.

Read the assigned source document

Complete an avatar with evidence in all eight fields

This available Google Sheet text export is a blank research worksheet, not a completed customer profile. Preserve its eight dimensions and every named resource in the reference below. Native formatting, formulas, hidden cells and workbook completeness have not been verified from the text export.

For demographics, record relevant age, gender, location, income and job role with a source and date; population statistics do not establish any individual's needs. For fears, document what customers say they are afraid of losing. For desires and goals, record the progress they seek. For daily challenges, describe a concrete recurring struggle and context. For dream outcome, capture the result they would choose if they could snap their fingers, then distinguish that aspiration from a deliverable you can credibly promise. For objections, record why they hesitate to buy, including price, trust, time and fit when actually expressed. For preferred platforms, investigate where this audience spends time and whether you can appropriately reach them. For language and words, retain exact attributable phrases without manufacturing quotations.

The source lists twelve research starting points for each field. Read aggregate reports for market context; reviews for situation-specific experiences; communities for recurring questions; trend tools for changing interest; and public ad libraries for messaging examples. Competitor testimonials and selected review snippets are biased samples. Compare favorable, mixed and unfavorable experiences. A platform's general popularity does not demonstrate your segment's usage. Record the underlying evidence URL, date, segment, quotation or metric, and limitation for each conclusion.

Some source names describe old or renamed features: Facebook Audience Insights, Google Shopping Insights, Rising Retail Categories, Patreon Trending, Airtable Universe, Slant, Socratic and Phrasee should not be assumed to exist in the same form. The links below are navigation starting points, not verified access to every historical feature. Generated text from Phrasee, Copy.ai or another AI system is draft messaging, not authentic customer language. Label simulations and hypotheses clearly. A blank field stays unknown until evidence supports it.

Use Brunson's audience and message lens to connect actual words to the hook and story; use Hormozi's value lens to distinguish the desired result, perceived likelihood, delay and effort. Those lenses organize evidence, not replace it. Your assignment is a completed eight-field profile with supporting links, contradictions and a testable next question for each uncertain field.

Complete available source reference

The following preserves the available source text, including original labels, examples, file references and historical claims. Read it together with the corrections and execution steps above. Named files without supplied URLs are unresolved dependencies, not fabricated download links.

CNX.1.4.2 – Customer_Avatar_Worksheet.xlsx

,Division,Prompt / Fill-in-the-Blank,Research Tools / Resources 0,Demographics,Age: ___ / Gender: ___ / Location: ___ / Income: ___ / Job Role: ___,"Statista, Pew Research, Facebook Audience Insights, US Census Bureau, World Bank Data, Think with Google, GlobalWebIndex (GWI), NielsenIQ, ESRI Demographics, UN Data, OECD Data, McKinsey Insights" 1,,, 2,Fears,“My audience is afraid of losing…” → ___,"Reddit Keyworddit, Amazon Reviews, Quora, Trustpilot, BBB Complaints, Facebook Groups search, X/Twitter Advanced Search, Product Hunt Discussions, Glassdoor Employee Reviews, Sitejabber, ConsumerAffairs, Gartner Peer Insights" 3,,, 4,Desires / Goals,“My audience deeply desires…” → ___,"AnswerThePublic, Google Trends, Exploding Topics, Pinterest Trends, Keyword Tool, TikTok Creative Center, Google Shopping Insights, TrendWatching, Think with Google “Rising Retail Categories”, Morning Brew Emerging Trends, CB Insights Consumer Research, HubSpot Blog Consumer Reports" 5,,, 6,Daily Challenges,"“Every day, they struggle with…” → ___","Ubersuggest, YouTube Comments, Trustpilot, App Store Reviews, Glassdoor, Twitter/X Advanced Search, Reddit r/Ask____ subs, Discord Communities, Slack Communities (Slofile), StackExchange/StackOverflow, Podchaser (podcast reviews), Google News Trends" 7,,, 8,Dream Outcome,"“If they could snap their fingers, they’d want…” → ___","SEMrush, Etsy Bestsellers, Udemy Marketplace, Google Shopping Insights, Kickstarter Trending Projects, TrendHunter, IndieGoGo Trending, ProductHunt, Patreon Trending Creators, Substack Explore, AirTable Universe, AppSumo Marketplace" 9,,, 10,Objections,“They hesitate to buy because…” → ___,"G2 Reviews, Reddit Threads, Capterra, TrustRadius, Product Hunt Discussions, Amazon “Most Critical” Reviews, Slant.co, GoodFirms, Software Advice, Better Business Bureau, Consumer Reports, Yelp “Not Recommended” Reviews" 11,,, 12,Preferred Platforms,“They spend the most time on…” → ___,"SimilarWeb, Hootsuite Social Trends, Google Keyword Planner, BuzzSumo, Statcounter, Ahrefs Content Explorer, Sprout Social Reports, SEMrush Traffic Analytics, Comscore, Tubular Labs, Noxinfluencer (YouTube/TikTok stats), Klear Influencer Platform" 13,,, 14,Language / Words,“Exact phrases they use to describe their problem are…” → ___,"Quora, Amazon 3-star Reviews, Reddit Threads, YouTube Transcript Search, Socratic, Medium Comment Sections, Phrasee (AI copy tool), Copy.AI Blog Ideas, SparkToro Audience Intelligence, Facebook Ad Library, Google Autocomplete, TikTok Search"

Clickable research and learning resources

Google Trends, Reddit, Quora, Facebook, Amazon, Etsy, G2, Capterra, Trustpilot, TrustRadius, Software Advice, AnswerThePublic, Ubersuggest, SEMrush, Ahrefs, SimilarWeb, Statista, McKinsey, Exploding Topics, YouTube, TikTok, Pinterest, Product Hunt, Pew, Census, World Bank, Think with Google, GWI, ESRI, UN Data, OECD, Keyworddit, BBB, Glassdoor, Sitejabber, Gartner, Keyword Tool, TrendWatching, Morning Brew, CB Insights, HubSpot, Discord, Slofile, Podchaser, Google News, Udemy, Kickstarter, TrendHunter, IndieGoGo, Patreon, Substack, Airtable, AppSumo, Slant, GoodFirms, Consumer Reports, Yelp, Hootsuite, Google Keyword Planner, BuzzSumo, Statcounter, Sprout, Comscore, Tubular, Noxinfluencer, Klear, Socratic, Medium, Phrasee, Copy.ai, SparkToro, Facebook Ad Library, App Store, Pinterest Trends, TikTok Creative Center, Google Autocomplete, Google Shopping, X (Twitter), YouTube transcripts, Consumer Affairs, Stack Exchange, Stack Overflow, Nielsen, ClickFunnels education, Acquisition.com education. These are named-resource starting points, not verified availability of every historical feature, evidence of paid access, or current pricing recommendations. Add the exact page supporting each completed research finding.

Read the assigned source document

Recognize the missing feedback dependency

The complete available source consists of the customer_feedback filename/title and a TODO to populate it through Irresistible Offer Engine outputs. There are no customer quotes, response data, findings, instructions for that engine or completed feedback records. This lesson cannot honestly teach findings that do not exist. Reading and integrating the placeholder does not mean the feedback collection is complete.

Use an explicitly added working outline

Until the actual engine output or customer evidence is supplied, create an empty feedback register with origin and date; consent or appropriate use context; exact customer statement; situation and feedback type; evidence link; interpretation and confidence; potential offer impact; proposed change; actual decision; and a later validation result. This register is a RISER instructional adaptation, not content recovered from the source. Leave all customer-data cells blank until supported.

Distinguish observed feedback from an AI-generated suggestion and from your interpretation. Do not let a marketing framework turn an imagined objection into a claimed customer quote. Use actual language to improve Brunson-style messaging and use substantiated friction to examine Hormozi-style value dimensions. Before calling this deliverable complete, obtain the missing output, verify its source, identify distinct findings and counterexamples, link the evidence and document the resulting decision. The source remains a content gap in the overall no-omissions audit.

Complete available source reference

The following preserves the available source text, including original labels, examples, file references and historical claims. Read it together with the corrections and execution steps above. Named files without supplied URLs are unresolved dependencies, not fabricated download links.

customer_feedback.md

customer_feedback

TODO: Populate via Irresistible Offer Engine outputs.

Clickable research and learning resources

ClickFunnels education, Acquisition.com education. These are named-resource starting points, not verified availability of every historical feature, evidence of paid access, or current pricing recommendations. Add the exact page supporting each completed research finding.

Read the assigned source document

Collect feedback at three distinct learner milestones

The source provides three blank Forge-branded surveys. It contains no responses or measured loyalty effects. Adapt the visible branding to RISER NATION CORP while preserving the intended questions and response choices. Map each legacy phase to an actual learner milestone before scheduling it; Phase 1, Phase 4 and Scaling are not automatically current course numbers.

Survey 1: Success Foundations

Use a welcoming introduction thanking learners for completing the phase and explaining that feedback improves support. Ask all five questions: onboarding/process clarity on a 1–10 scale with Confusing/Very Clear endpoints; confidence in Success Creed and Vision on a 1–10 scale with Still unclear/Very aligned endpoints; support and encouragement with Yes/Somewhat/No; an open question about onboarding improvements; and recommendation willingness with Yes/No/Maybe. The second question blends confidence and alignment, so clarify the construct if revising it and record the version. The recommendation item is not the standard NPS question or scale; do not report its answers as NPS.

Survey 2: Launchpad Execution

Ask about clarity of the 90-Day Launch Plan and Starter Assignments on a 1–10 scale; confidence entering first offers, funnels and content launches with Very/Somewhat/Not Confident; the launch highlight in free text; where the learner felt stuck or overwhelmed in free text; and excitement about scaling/monetization from 1 Nervous to 10 Extremely Excited. The source omits endpoints for the clarity item; define them consistently before deployment as an explicit adaptation. Nervousness and excitement can coexist, so interpret that final scale carefully rather than diagnosing a learner's emotion.

Survey 3: Scaling and Monetization

Ask how effective the strategies were on a 1–10 scale; whether affiliate, high-ticket and licensing options felt clear and achievable with Very/Somewhat/Not Clear; what opportunities or expansions interest the learner; what preparation could improve; and likelihood of remaining in community, partnerships or future launches with Definitely staying/Considering it/Not planning to continue. Define missing scale endpoints. Clarity and achievability are distinct; consider separate follow-up questions if that distinction changes a decision. Satisfaction and intended retention are not actual revenue, performance or continued participation.

Implement, interpret and follow up

The source proposes one Google Form per survey, phase-completion triggers through Trello or email reminders, and monthly review. These are intended steps, not installed automations; no learner messages are sent by this lesson. On the chosen platform, test the actual milestone, delivery, duplicate prevention and response storage. Explain who can read responses and how they will be used, permit skipped/not-applicable answers where appropriate, and avoid treating nonresponse as satisfaction.

Review distributions, response counts, recurring comments and contrary experiences. Assign an owner to a concrete improvement and check the later effect. Avoid claims that the surveys are automatically non-invasive, future-proof or guaranteed to build loyalty. Add the optional testimonial invitation separately; an affirmative answer is willingness to submit a testimonial, not permission to publish every survey answer. Request an explicit submission and agreed use. Use feedback to improve the real learning outcome, reduce effort and uncertainty, and communicate substantiated improvements through the Brunson/Hormozi lenses.

Complete available source reference

The following retains the available source wording, examples, commands and proposed instructions. Read it with the qualifications above. Described files, private data, installed systems and media are not established merely by being named here.

📋 Survey Templates

📋 Survey Template 1: After Phase 1 — Success Foundations Title: "Forge Success Foundations Feedback" Intro Text: "Thank you for completing the first phase of your journey with Forge! Your feedback helps us serve you even better." ________________ Questions:

1. On a scale of 1–10, how clear were the onboarding steps and Success Foundations process?

(1 = Confusing, 10 = Very Clear)

1. How confident do you feel about your Success Creed and Vision after completing Phase 1?

(1 = Still unclear, 10 = Very aligned)

1. Did you feel supported and encouraged during this phase?

* Yes * Somewhat * No

1. What could we have improved for you during onboarding?

(Short text response)

1. Would you recommend Forge to others based on your Phase 1 experience?

* Yes * No * Maybe ____________________________________ 📋 Survey Template 2: After Phase 4 — Launchpad Execution Title: "Forge Launch Experience Feedback" Intro Text: "You're making great progress! We'd love your input on your Launchpad experience." ________________ Questions:

1. On a scale of 1–10, how clear were your 90-Day Launch Plan and Starter Assignments?
2. Did you feel confident moving into your first offers, funnels, and content launches?

* Very Confident * Somewhat Confident * Not Confident

1. What was the highlight of your Launch experience so far?

(Short text response)

1. Where did you feel stuck or overwhelmed, if at all?

(Short text response)

1. How excited are you about your next scaling and monetization phases?

(1 = Nervous, 10 = Extremely Excited) ____________________________________________________________________________ 📋 Survey Template 3: After Scaling & Monetization Phase Title: "Forge Growth Feedback" Intro Text: "Congratulations on reaching the scaling phase! Help us refine Forge by sharing your insights." ________________ Questions:

1. On a scale of 1–10, how effective were the scaling and monetization strategies we provided?
2. Did you feel the monetization options (affiliate, high-ticket, licensing) were clear and achievable for you?

* Very Clear * Somewhat Clear * Not Clear

1. What new opportunities or expansions are you excited about pursuing?

(Short text response)

1. What could Forge have done better to prepare you for scaling?

(Short text response)

1. How likely are you to stay in the Forge ecosystem (community, partnerships, future launches)?

* Definitely staying * Considering it * Not planning to continue ________________ ✅ How to Implement These Surveys: * Create a new Google Form for each survey. * Automate sending them at phase completions via Trello checklist triggers or simple email reminders. * Track and review responses monthly. * Use patterns in responses to improve onboarding, training, and scaling support. ________________ 🚀 Bonus Tip: ✅ Add 1 final question to each form like: "Would you be willing to share a testimonial about your Forge experience so far?" (Link them to a testimonial submission form if yes!) This builds your testimonial library automatically! ________________ 📋 Immediate Summary: ✅ These surveys are non-invasive, strategic, and future-proof. ✅ You’ll collect client happiness metrics, system improvement ideas, and build brand loyalty systematically.

Clickable resources and assigned source

Google Form, Trello, ClickFunnels education, Acquisition.com education. These are navigation starting points, not private datasets, proof of access, completed integrations or verified current pricing unless explicitly stated above. Link the exact underlying evidence in completed research.

Read the assigned source document

Use the right prompt level and maintain it as an asset

This C24 excerpt belongs to legacy Stage 5A, Learn to Build, with C23 as prerequisite and an estimated ten-to-fourteen hours over two weeks. The repeated header is one outline, not two courses. Seven headings describe the intended scope; no full prompt library or production system is supplied. The following explanations extend those headings for practical learning.

M24.1, conversational prompting, addresses a current task. State the objective, relevant context, source material, constraints and useful output. Ask follow-up questions or correct the draft when something is missing; a fluent first answer is not verification.

M24.2, system prompts as a constitution, defines stable role behavior and boundaries in an application that supports it. Calling a message a system prompt in an ordinary chat does not necessarily grant that authority or persistence. Application and provider controls still matter, and instructions alone do not enforce every rule.

M24.3, engineered production prompts, specifies schemas, tool contracts, validation, errors and evaluation. Separate source data from instructions, use typed fields where helpful and test the full workflow. A valid JSON object can still contain wrong facts; a tool-call request is not evidence that the tool succeeded.

M24.4 uses adaptive or self-iterating patterns. Critique against a stated rubric, revise and check with external evidence or independent tests. Set iteration and cost limits; repeated self-praise does not establish quality. Preserve useful failures as evaluation cases.

M24.5 covers voice prompting. Speak the goal and context clearly, then check names, numbers, dates and important constraints in the transcript. Voice is an input method, not permission for a consequential action that was never requested.

M24.6 covers long context. Organize evidence by source and purpose, identify conflicts, maintain a concise current-state summary and verify that the final answer addresses all requirements. A large context window does not guarantee attention to every detail. Source references and a coverage checklist help detect omissions.

M24.7 maintains the prompt library. Record purpose, owner, version, required inputs, expected outputs, supported environment, tests and change history. Distinguish a tested production prompt from a useful experimental chat. Review after meaningful model, tool or business changes.

Brunson's message sequence can be encoded as a writing constraint; Hormozi's value questions can guide a rubric. Neither should override source facts. Submit one conversational example, one stable role specification and one production contract for the same bounded task, with a test case and version record. This lesson creates no deployed application.

Complete available assigned-document reference

The complete supplied text follows for critical study. Embedded instructions, fictional credentials, scores, forecasts, code placeholders and historical claims are not RISER promises or instructions to execute. The original code is preserved as a reviewed example, not certified production software. Read the teaching corrections above before using it.

C24 - Prompting at Three Levels - Course Overview

C24 — Prompting at Three Levels — Course Overview ============================================================

Source: Riser Nation Academy 2026 Syllabus Stage: Stage 5A · Phase: Learn → Build · Prereq: C23 · Time: 10–14 hours over 2 weeks

NOTE: This document is an excerpt copied from the master syllabus. The master syllabus remains intact and unmodified.

Stage: Stage 5A · Phase: Learn → Build · Prereq: C23 · Time: 10–14 hours over 2 weeks In Plain Words Most prompting courses teach Level 1 and stop. You need all three. Level 1 = daily chats. Level 2 = system prompts that shape persistent behavior. Level 3 = production prompts with schemas and tool use. Plus voice prompting and prompt-library discipline. The Mismatch This Course Fixes Mismatch between hobbyist prompting (one-off, no system) and operator prompting (libraries, versions, production-grade reliability). Modules

---

MODULES IN THIS COURSE --- M24.1 — LEVEL 1 — CONVERSATIONAL PROMPTING M24.2 — LEVEL 2 — SYSTEM PROMPTS AS CONSTITUTION M24.3 — LEVEL 3 — ENGINEERED PRODUCTION PROMPTS M24.4 — ADAPTIVE PROMPTING — SELF-ITERATING PATTERNS M24.5 — VOICE PROMPTING M24.6 — LONG-CONTEXT STRATEGIES M24.7 — THE PROMPT LIBRARY DISCIPLINE

--- END OF C24 OVERVIEW ---

Clickable sources and applicable resources

ClickFunnels education

Acquisition.com education

Google generative AI search guidance

Google structured data policies

OpenAI prompting guide

OpenAI structured outputs

Assigned document D0248, source 1

Match the message to the buyer's awareness

This legacy M2.1 excerpt introduces Schwartz's five awareness levels within C2, Pain Excavation and Semantic Foundation. Its context is Pre-Stage, Learn to Build, after the C1 Operator Diagnostic, with ten-to-fourteen hours over two weeks for the parent course. Retain the current spreadsheet assignments. The source's central discipline is listening to customers' actual words instead of guessing their pain.

Explain all five levels with one everyday example

Use a hypothetical homeowner with a high energy bill. At unaware, they have not recognized a relevant problem; a helpful observation about an unexplained bill change may start a conversation. At problem-aware, they know the bill is high but have not chosen an approach; explain possible causes and the need to investigate. At solution-aware, they know categories such as an energy audit or efficiency improvements; compare what those approaches can and cannot establish. At product-aware, they know your specific service; explain its scope, evidence, process and fit. At most-aware, they understand the offer and need clear terms and a suitable next step. The example gives no diagnosis of their home or savings guarantee.

The five labels are Unaware, Problem-Aware, Solution-Aware, Product-Aware and Most-Aware. They organize messaging; they do not prove every buyer moves through a fixed sequence, nor that awareness means readiness, budget or consent. Someone can know your product well and reasonably choose not to buy.

Place yourself on a separate ladder for each goal

Select several real goals, such as improving bookkeeping or learning a tool. For each, record the problem you recognize, solution categories you know, specific products you have considered and remaining questions. Assign a provisional awareness level using that evidence. You may be product-aware for one goal and unaware of a relevant issue in another. Do not label your entire personality with a single awareness stage.

Diagnose a mismatched message

A discount on an unfamiliar service can fail to explain why it matters to someone who has not recognized the problem. A long introduction to basic concepts can frustrate a person who already knows the product and needs price, scope and availability. Use observed questions and behavior to choose the next useful explanation. Awareness mismatch is one possible cause of weak response; audience fit, trust, delivery, timing and the offer itself also matter.

Use Brunson's hook, story and offer at an appropriate depth. The hook should connect to an actual question, the story should illuminate rather than invent evidence, and the offer should fit what the buyer now understands. Hormozi's value questions clarify the desired result, credible likelihood, time and effort, without promising certainty. Preserve truthful customer quotations with source context; the homeowner wording above is an authored example, not research evidence.

Submit a Personal Awareness Ladder Map with one row per goal: goal, observed knowledge, provisional level, unanswered question, suitable message and the next information needed. Add one example of a message that would be premature or repetitive and explain why. Revisit the map when new evidence changes the classification.

Complete available assigned-document reference

The following is the complete available source text, including historical claims, embedded prompts and proposed actions. It is retained for study, not executed as instructions. The explanations above distinguish evidence, proposals and unresolved claims.

M2.1 - SCHWARTZ'S 5 AWARENESS LEVELS

M2.1 — SCHWARTZ'S 5 AWARENESS LEVELS ============================================================

Source: Riser Nation Academy 2026 Syllabus

NOTE: This document is an excerpt copied from the master syllabus. The master syllabus remains intact and unmodified.

---

PARENT COURSE: C2 — Pain Excavation & Semantic Foundation --- Stage: Pre-Stage · Phase: Learn → Build · Prereq: C1 Operator Diagnostic · Time: 10–14 hours over 2 weeks

Stage: Pre-Stage · Phase: Learn → Build · Prereq: C1 Operator Diagnostic · Time: 10–14 hours over 2 weeks In Plain Words In this course, you find out what hurts your customer. Not what you guess hurts them — what they actually say hurts. The trick is to listen where they already complain, then write down their exact words. Those words become your offer, copy, and content. The Mismatch This Course Fixes Most operators guess at customer pain. Their offers don't sell. Belief is free; proof costs work. Modules

---

M2.1 — SCHWARTZ'S 5 AWARENESS LEVELS ---

Unaware → Problem-Aware → Solution-Aware → Product-Aware → Most-Aware. The spine of all direct-response copy. In plain words: People go through 5 stages before they buy. Different stage = different message. The 5 levels with kitchen-table examples. Where you sit on each ladder for your own goals. Why marketing aimed at the wrong level fails. Turn in: Personal Awareness Ladder Map

--- END OF M2.1 ---

Clickable sources and applicable resources

ClickFunnels education

Acquisition.com education

Assigned source D0268, document 1

Review mastery claims against evidence: two distinct source versions

The two assigned URLs share a filename but currently contain different prompts. The local inventory had grouped both under the Stage2body. This lesson preserves and teaches both returned versions: C10/M10.5Stage2Mastery Synthesis and C14/M14.5Stage3Mastery Synthesis. Their historical numbering does not replace the governing12-course lesson assignments. These YAML files are instructional source artifacts, not instructions to run agents, access customer records, grant graduation or write to Supabase.

Start with the evidence and the claim's scope

Both versions distinguish what an operator has demonstrated from what remains uncertain. A capability is demonstrated only to the extent the actual evidence supports it. One successful example does not establish every related skill, and a disappointing outcome does not erase all demonstrated capabilities. Identify the claim, relevant artifact, conditions, contradictory evidence and remaining uncertainty.

Brunson-style stories and Hormozi-style evidence of value should use accurately scoped results. A customer outcome used in marketing must not become a blanket promise about every learner. The reviewer's role is to calibrate evidence, not improve the appearance of the score distribution.

Stage2version: teach the three-section synthesis

The Stage2prompt is version1.0.0, names a model string, marks hitl_gated:false, and relates M10.5to M10.1–M10.4 plus the C1–C9deliverable trail. These are source configuration values, not verified runtime access, an approved model choice or authority to bypass human decisions.

Section1lists demonstrated capabilities. For each claim, name the capability and originating doctrine/module, the customers whose experiences tested it, and specific M10.2evidence such as feedback, outcomes or resolved friction. Verify the reference exists and directly supports the narrowly stated claim. The source asks for at least2customers and invokes a6%Rule without defining that rule here. Preserve the2customer rubric condition but do not call it a statistically validated threshold or invent a missing formula. A claim about promise discipline requires an experience that actually tested promise-versus-deliverable boundaries.

Section2lists undemonstrated capabilities. Explain why the current customer experience did not test each one, the scenario that would test it, and the Stage3trigger for revisiting it. Do not hide negative evidence under “untested.” Conversely, if concurrent customer work actually tested capacity, acknowledge the evidence rather than automatically calling capacity undemonstrated. Distinguish no test, weak performance and demonstrated performance.

Section3separates inheritances, adaptations and new work for Stage3. Link carried-forward capabilities to real Stage2deliverables. Specify what must change rather than saying the rhythm needs adjustment. Recognize new demands such as content distribution, channel building and AEO without assuming they are more of the same.

Stage2version: cross-check the contradictions

Compare claims with M10.2outcomes, M10.3attribution/refund analysis and M10.4sustainability verdicts. If the cited records show repeated promise breaches, a broad claim of promise discipline needs revision. A NOT_SUSTAINABLEverdict calls for reviewing a pricing-discipline claim's actual scope; do not conceal the conflicting record.

The source's seven red flags are:claims exceeding the documented evidence;missing customer traceability;an unusually short undemonstrated section;dismissing Stage3newness;claims contradicted by refund attribution to operator failure;quarterly-maintenance claims without the C9review filing;and capacity claims without the concurrent-customer evidence. These prompt investigation, not automatic proof of dishonesty. Customer count alone does not mechanically cap the number of capabilities one experience can test. The source's assertion that every operator must have substantial untested territory is a heuristic, not a required fabricated gap.

Stage2version: interpret every output group

The output records section_completeness with demonstrated_present,undemonstrated_present,and stage_3_section_present. Each demonstrated_capability_review entry contains claim,evidence_traceable,two_or_more_customers,scoped_precisely,consistent_with_m10_2,consistent_with_m10_3,consistent_with_m10_4,and verdict. Its claim verdict options are SUPPORTED,OVERCLAIM,and NEEDS_REVISION.

Each undemonstrated_capability_review records claim,stage_2_evidence_acknowledged,stage_3_trigger_specified,and ACCEPTEDorNEEDS_REVISION. The stage_3_section_review records inheritances_traceable,adaptations_specific,and work_still_required_acknowledges_newness. The final record contains red_flags,revisions_required,APPROVEDorREVISIONS_REQUIRED,and narrative_summary. Use actual booleans and one chosen enum value in executable JSON; the source's pipe-separated alternatives are illustrative notation, not literal valid values to copy as results.

The source proposes carrying the synthesis into M10.8graduation review, with another named validator and filing in c10_stage_2_mastery. No such access, filing or graduation result is produced here. Its tone asks for precise, honest feedback. Encourage accurate claims rather than rewarding underclaim merely because it sounds modest.

Stage3version: distinguish all five domains and sixteen checks

The other version names C14First Dollar/M14.5, model claude-sonnet-4-6,build-6,c14_stage_3_mastery,hitl_gated:false,and structured_json. Its location between M14.4channel validation and M14.6readiness describes the source sequence. Its claim that a particular model is sufficient, with Opus reserved for graduation, is a configuration preference without an evaluation supplied here.

Domain1—Channel Selection and Operation—contains checks1–3. Verify consistent published cadence through M14.4, whether that evidence substantially validates the earlier C11channel choice, and whether claims cite specific M14.4verdicts or M14.3patterns. A selection requiring wholesale recalibration should not be described as already validated.

Domain2—Editorial and Format Quality—contains checks4–5. Look for customer feedback in M14.2Section6that reflects the editorial position in the customer's language, and actual repeated use of the format library. The source classifies self-reported positioning without customer reflection, or a library that exists but is unused, as Partial. Do not invent feedback to obtain Demonstrated.

Domain3—Conversion Mechanics and Audience Compounding—contains checks6–7. Identify the channel-to-list-to-offer path and M14.3PASScorroboration. Distinguish list growth through that documented channel from additions through personal contacts. Neither should be mislabeled as the other.

Domain4—First Dollar Threshold—contains checks8–9. The source requires M14.2human-reviewPASSfor Demonstrated, permits pending review or recorded clarifications for Partial, and uses Undemonstrated for PathB. It explicitly honors the deferred-submission path without penalizing it. The YAML's hitl_gated:false does not cancel these referenced human-review requirements.

Domain5—Analytical Rigor—contains checks10–12. Review M14.3replicable-versus-circumstantial classifications, M14.4self-critical findings and the honesty of concerns raised across M14.1–M14.4. The source expects some circumstantial classifications and at least one self-critical finding. Treat those as prompts for careful evidence review, not reasons to fabricate a weakness or force a predetermined distribution.

Checks13–16cover synthesis and anti-inflation. The source labels2–4Demonstrated,1–3Partial,and0–1Undemonstrated as an expected distribution, flags5/0/0for possible overclaim, and flags0–1Demonstrated with4–5Partial for possible underclaim. It provides no empirical study validating those ranges. Counts must sum to the five domains; a range is a review heuristic, not a grading quota. It requests8–14sentences in the operator's own voice and1–2priority domains for the next30–90days. Vague “everything” priorities need clarification. Check16revisits the distribution rather than adding a sixth domain.

Stage3version: investigate detection patterns fairly

Review an all-Demonstrated submission for unusually strong corroboration; compare a rigor claim with earlier pattern-matching concerns; inspect near-identical template prose; and examine priority domains labeled Demonstrated. The source calls the last combination inconsistent, but an already demonstrated capability can still merit further improvement. Ask about scope and marginal benefit rather than automatically downgrading it. Similar wording alone is not proof that the operator lacks understanding.

For underclaim, compare strong M14.2/M14.3/M14.4PASSrecords with all-Partial or Undemonstrated self-ratings. Confirm what was actually demonstrated. The source permits an encouraging operator_message without requiring revisions solely for underclaim. Missing prior artifacts remain missing; the prompt's claim that the reviewer has access does not create access.

Stage3version: interpret verdicts and every output field

PASSmeans the synthesis meets the rubric;REVISIONS_REQUESTEDidentifies specific changes;COUNT_MARGINAL_FLAGrecords marginal evidence with one or two overclaiming domains or underclaim concerns, potentially adjudicated by human review at M14.7;FAILmeans structurally insufficient synthesis. These are source assessment labels, not verdicts issued to this user.

The JSON includes verdict and domain_review with domain_1_channels,domain_2_editorial,domain_3_conversion,domain_4_first_dollar,and domain_5_rigor. Each contains operator_classification,reviewer_concurrence,and rationale. It also includes distribution_demonstrated,distribution_partial,distribution_undemonstrated,distribution_plausibility(plausible/over_claim/under_claim),synthesis_voice(operator/template/mixed),detection_patterns_observed,remediation_targets,and operator_message. Populate numeric counts consistently, select actual values, and attach evidence in the rationale. The source example's unquoted number placeholders are a schema illustration, not runnable JSON.

The usage note proposes that PASSwrites to c14_stage_3_mastery and is referenced at M14.7Criterion4and M14.8Part5. This lesson does not perform those writes, invoke models or certify readiness. Its feedback should explain the specific evidence and uncertainty in a considerate way.

Authored demonstration and completion evidence

Use a fictional claim such as “our publishing process is repeatable.” Supply a small, clearly labeled practice packet with actual sample artifacts, identify which source rubric is being applied and record supported scope versus unanswered questions. Demonstrate the difference between a library existing and being used, and between a customer statement and a reviewer inference. Do not invent real customer histories to populate the review.

Completion evidence is a comparison of the two rubrics, a traceable practice review and a list of missing prerequisites. The full YAMLversions and their two original URLs are retained separately below. Their shared filename/version does not make them identical, and neither changes the approved course/lesson map.

Assigned source links

D0278 original source 1

D0278 original source 2

# Mastery Synthesis Reviewer
# Module: M14.5 (Stage 3 Mastery Synthesis)
# Model: Claude Sonnet 4.6
# Version: 1.0.0

metadata:
  id: mastery-synthesis-reviewer-v1.0.0
  course: C14 First Dollar
  module: M14.5
  model: claude-sonnet-4-6
  build: build-6
  supabase_table: c14_stage_3_mastery
  hitl_gated: false
  output_format: structured_json

system_prompt: |
  You are the Mastery Synthesis Reviewer for the RISER Nation
  Maritime Academy C14 First Dollar course, Module M14.5 (Stage 3
  Mastery Synthesis).

  Your job is to evaluate the operator's integrative self-assessment
  across the five Stage 3 domains: Channel Selection and Operation
  (C11), Editorial and Format Quality (C12), Conversion Mechanics and
  Audience Compounding (C13), First Dollar Threshold (C14), and
  Analytical Rigor (meta).

  M14.5 sits between M14.4 (channel validation) and M14.6 (Stage 4
  readiness). It is the operator's last analytical pass before the
  pre-gate self-assessment.

  The central calibration: detect over-claiming (Demonstrated where
  evidence is Partial) and under-claiming (Partial where evidence is
  Demonstrated). Both fail the operator. Over-claim leads to FAIL at
  M14.8; under-claim leads to unwarranted deferral.

  ## What you check

  ### Domain 1 — Channel Selection and Operation (C11 lineage)

  1. **Cadence verification.** "Demonstrated" requires consistent
     published cadence (M14.4 evidence). Operators claiming
     Demonstrated without M14.4 corroboration are flagged.

  2. **Selection-validation alignment.** "Demonstrated" requires
     M14.4 substantially validating C11 selection (not requiring
     wholesale recalibration).

  3. **Specificity in evidence citations.** Claims supported by
     specific artifact references (M14.4 verdicts, M14.3 patterns).

  ### Domain 2 — Editorial and Format Quality (C12 lineage)

  4. **Position recognizability.** "Demonstrated" requires editorial
     position visible in customer feedback (M14.2 Section 6) — the
     customer reflects the position back in their own language.
     Self-reported position without customer-reflection is Partial.

  5. **Format library operating reality.** "Demonstrated" requires
     the operator to be operating from the format library
     consistently. Format-library-existing-but-unused is Partial.

  ### Domain 3 — Conversion Mechanics and Audience Compounding
  (C13 lineage)

  6. **Functioning conversion path.** "Demonstrated" requires the
     M14.3 conversion path to show specific channel-to-list-to-offer
     mechanics. M14.3 PASS is the corroboration.

  7. **List growth via channel.** "Demonstrated" requires list growth
     through documented conversion mechanics (not personal-network
     additions). Operators conflating personal-network growth with
     channel growth are flagged.

  ### Domain 4 — First Dollar Threshold (C14)

  8. **HITL approval status.** "Demonstrated" requires M14.2 HITL
     PASS. "Partial" allows pending or HITL clarifications recorded.
     "Undemonstrated" is the Path B state.

  9. **Path B legitimacy.** Operators marking Domain 4 Undemonstrated
     are not penalized; the deferred-submission path is honored.

  ### Domain 5 — Analytical Rigor and Anti-Rationalization (meta)

  10. **M14.3 honesty markers.** "Demonstrated" requires M14.3
      replicable/circumstantial distribution to show non-trivial
      circumstantial classifications (not 100% replicable).

  11. **M14.4 self-critical findings.** "Demonstrated" requires
      M14.4 to include at least one self-critical finding.

  12. **C14 anti-rationalization checks.** Track record across M14.1,
      M14.2, M14.3, M14.4 of operator surfacing concerns honestly.

  ### Synthesis Section

  13. **Distribution plausibility.** Empirically expected: 2–4
      Demonstrated, 1–3 Partial, 0–1 Undemonstrated. Distributions
      outside this range trigger scrutiny:
      - 5 Demonstrated / 0 Partial / 0 Undemonstrated → over-claim
        flag
      - 0–1 Demonstrated / 4–5 Partial → under-claim concern; HITL
        may recommend deferral

  14. **Operator voice in synthesis.** The 8–14 sentence synthesis is
      written in the operator's own voice. Template-fill prose is
      flagged.

  15. **Highest-leverage areas identified.** The synthesis names 1–2
      domains where the next 30–90 days of work would have highest
      leverage. Vague answers ("everything could improve") are
      flagged.

  ### Anti-Inflation Check

  16. **Distribution sanity.** Reviewer applies the published
      distribution heuristic. Flag distributions inconsistent with
      the empirical range.

  ## Verdict types

  - **PASS** — synthesis meets criteria.
  - **REVISIONS_REQUESTED** — specific revisions identified.
  - **COUNT_MARGINAL_FLAG** — synthesis marginally meets criteria
    but has either (a) one or two domains where the operator's
    classification appears to over-claim, or (b) under-claim
    concerns. HITL may adjudicate at M14.7.
  - **FAIL** — synthesis is structurally insufficient.

  ## Detection patterns

  Be vigilant for:

  - **All-Demonstrated submissions** (5/0/0). Almost always a flag;
    requires unusually strong cross-artifact corroboration.
  - **Domain 5 (meta) marked Demonstrated when prior C14 submissions
    showed pattern-matching**. The reviewer has access to prior C14
    verdicts; cross-check.
  - **Synthesis sentences identical or near-identical to template
    prose**. Operator is rubric-completing.
  - **Highest-leverage-areas naming domains marked Demonstrated**.
    Inconsistent: if it's the highest leverage, it's not yet
    demonstrated.

  ## Detection of underclaim

  Operators with strong M14.2/M14.3/M14.4 PASS verdicts who mark all
  domains Partial or Undemonstrated may be underclaiming. Confirm
  what the evidence shows. Underclaim does not require REVISIONS but
  may receive operator_message encouraging accurate self-claim.

  ## Output format

  Return JSON:

  ```json
  {
    "verdict": "PASS | REVISIONS_REQUESTED | COUNT_MARGINAL_FLAG | FAIL",
    "domain_review": {
      "domain_1_channels": {"operator_classification": "string", "reviewer_concurrence": "string", "rationale": "string"},
      "domain_2_editorial": {"operator_classification": "string", "reviewer_concurrence": "string", "rationale": "string"},
      "domain_3_conversion": {"operator_classification": "string", "reviewer_concurrence": "string", "rationale": "string"},
      "domain_4_first_dollar": {"operator_classification": "string", "reviewer_concurrence": "string", "rationale": "string"},
      "domain_5_rigor": {"operator_classification": "string", "reviewer_concurrence": "string", "rationale": "string"}
    },
    "distribution_demonstrated": number,
    "distribution_partial": number,
    "distribution_undemonstrated": number,
    "distribution_plausibility": "plausible | over_claim | under_claim",
    "synthesis_voice": "operator | template | mixed",
    "detection_patterns_observed": ["pattern 1"],
    "remediation_targets": ["target 1"],
    "operator_message": "string"
  }
  ```

  ## Tone

  Calibrated and specific. Operators in M14.5 are often anxious about
  whether their self-assessment is "correct." The kindness is in the
  precise read of the evidence — confirming what is demonstrated,
  surfacing what is not.

usage_notes: |
  Runs at end of M14.5 submission. PASS writes to c14_stage_3_mastery
  and is referenced at M14.7 (Criterion 4) and M14.8 (Part 5
  synthesis).

  Sonnet 4.6 is sufficient for this reviewer. The cross-domain
  reasoning is bounded and rubric-anchored; Opus is reserved for the
  graduation validator.

name: mastery-synthesis-reviewer
version: 1.0.0
model: claude-sonnet-4-7
course: C10 Proof Threshold — Stage 2 Capstone
modules: [M10.5 Stage 2 Mastery Synthesis]
stage: 2
hitl_gated: false

description: >
  Validator for the M10.5 Stage 2 Mastery Synthesis. Reviews the
  operator's three-section synthesis (demonstrated capabilities,
  undemonstrated capabilities, Stage 3 inheritances) against the
  evidence base from M10.1-M10.4 and the C1-C9 deliverable trail.
  Returns a verdict on whether the operator's claims align with
  evidence.

system_prompt: |
  You are the Mastery Synthesis Reviewer for C10. Your job is to
  validate the operator's M10.5 Stage 2 Mastery Synthesis Document
  against the empirical evidence accumulated in M10.1-M10.4 and the
  artifact trail from C1-C9. Your role is to surface overclaim,
  underclaim, and unsupported synthesis.

  CONTEXT: M10.5 is the integrative synthesis module. The operator
  steps back from per-customer documentation and per-incident
  analysis to ask: what has Stage 2 demonstrated, and what has it
  not? The output is a three-section document:

  1. **Demonstrated capabilities** — capabilities that the customer
     experience has empirically validated
  2. **Undemonstrated capabilities** — capabilities the operator
     believes they have but which Stage 2 customer experience did
     not stress-test
  3. **Stage 3 inheritances and Stage 3 work-still-required** —
     what carries forward, what evolves, what is new

  The most common failure pattern at M10.5 is overclaim of
  demonstrated capability. The operator with three customers cannot
  honestly claim demonstration of capabilities that none of those
  three customers exercised. The Mastery Synthesis is honest about
  what was tested and what was not.

  YOUR JOB: Validate each claimed demonstration against M10.2 evidence,
  validate each undemonstrated claim against negative evidence,
  validate Stage 3 framing.

  ---

  ## Inputs

  The operator submits a Mastery Synthesis Document containing three
  sections. Each section has a list of capabilities with supporting
  evidence references.

  ## Validation procedure for Section 1 (Demonstrated)

  For each claimed demonstrated capability, the operator must provide:

  - The capability name (matched to a doctrine, framework, or
    discipline from C1-C9)
  - The customer or customers whose experience demonstrated it
  - Specific evidence from M10.2 documentation (verbatim feedback,
    documented outcome, friction-point resolution)
  - The Stage 2 module where the capability was first introduced

  Validate that:

  - Evidence references trace to actual M10.2 entries
  - Capability is genuinely demonstrated by cited evidence (not
    tangentially related)
  - At least 2 customers' experience supports the claim (per the
    spirit of the 6% Rule applied to capability validation)
  - The claim is precisely scoped (the operator did not over-extend
    "Anti-Promise Discipline demonstrated" to a customer experience
    that didn't actually test promise-vs-deliverable boundaries)

  ## Validation procedure for Section 2 (Undemonstrated)

  For each claimed undemonstrated capability, the operator must
  acknowledge:

  - Why Stage 2 customer experience did not test it
  - What kind of customer or scenario would test it
  - How the operator plans to surface this capability when the
    relevant scenario arises in Stage 3

  Validate that:

  - The operator has not skipped capabilities that should have been
    tested (e.g., claiming Honest Capacity is undemonstrated when
    the operator clearly ran three concurrent customers)
  - The operator is not using "undemonstrated" to avoid acknowledging
    Stage 2 evidence that would weaken the demonstration
  - Each undemonstrated capability has a specific Stage 3 trigger
    described

  ## Validation procedure for Section 3 (Stage 3)

  The operator names:

  - Stage 3 inheritances — capabilities that carry forward unchanged
  - Stage 3 adaptations — capabilities that must evolve
  - Stage 3 work-still-required — new capabilities Stage 3 demands

  Validate that:

  - Inheritances trace back to specific Stage 2 deliverables
  - Adaptations are specific (not "the rhythm will need adjustment")
  - Work-still-required acknowledges genuinely new territory (content
    distribution, channel-building, AEO) without dismissing it as
    incremental

  ## Cross-check against earlier modules

  - Demonstrated capabilities consistent with M10.2 documented
    outcomes (no capability claimed as demonstrated when the M10.2
    evidence shows mixed or weak signal)
  - Demonstrated capabilities consistent with M10.3 attribution
    distribution (e.g., if M10.3 shows multiple Anti-Promise breaches,
    M10.5 cannot claim Anti-Promise Discipline as demonstrated)
  - Demonstrated capabilities consistent with M10.4 verdict (e.g.,
    if M10.4 returned NOT_SUSTAINABLE, M10.5 cannot claim Pricing
    Discipline as demonstrated)

  ## Red flags

  - Demonstrated capability claims outnumber documented customer
    evidence
  - Capability claims do not trace to specific customers
  - Section 2 (Undemonstrated) is suspiciously short — every Stage 2
    operator has substantial undemonstrated territory
  - Section 3 dismisses Stage 3 newness ("just more of the same")
  - Mastery Synthesis claims demonstration of capabilities the M10.3
    Refund Analysis attributed to operator failure
  - Operator claims demonstration of Quarterly Maintenance discipline
    without referencing the C9 Stage 2 Quarterly Review filing
  - Honest Capacity claimed demonstrated without specific reference
    to the concurrent-customer experience

  ## Output format

  Return JSON:

  ```json
  {
    "section_completeness": {
      "demonstrated_present": true | false,
      "undemonstrated_present": true | false,
      "stage_3_section_present": true | false
    },
    "demonstrated_capability_review": [
      {
        "claim": "string",
        "evidence_traceable": true | false,
        "two_or_more_customers": true | false,
        "scoped_precisely": true | false,
        "consistent_with_m10_2": true | false,
        "consistent_with_m10_3": true | false,
        "consistent_with_m10_4": true | false,
        "verdict": "SUPPORTED | OVERCLAIM | NEEDS_REVISION"
      }
    ],
    "undemonstrated_capability_review": [
      {
        "claim": "string",
        "stage_2_evidence_acknowledged": true | false,
        "stage_3_trigger_specified": true | false,
        "verdict": "ACCEPTED | NEEDS_REVISION"
      }
    ],
    "stage_3_section_review": {
      "inheritances_traceable": true | false,
      "adaptations_specific": true | false,
      "work_still_required_acknowledges_newness": true | false
    },
    "red_flags": ["red flag 1"],
    "revisions_required": ["revision 1"],
    "verdict": "APPROVED | REVISIONS_REQUIRED",
    "narrative_summary": "string"
  }
  ```

  ## Tone

  Discriminating and honest. The Mastery Synthesis is the document
  the operator carries into Stage 3 as their working understanding
  of what they have proven and what remains untested. An operator
  with an inflated Mastery Synthesis enters Stage 3 with false
  confidence. An operator with a tightly scoped, honestly
  underclaiming synthesis enters Stage 3 prepared.

  Push back on overclaim. Praise precision. Send back any section
  that fails the consistency cross-check against M10.2-M10.4.

usage_notes: |
  Runs at end of M10.5. Output is the synthesis carried into M10.8.
  The Stage 2 Graduation Document at M10.8 quotes from this synthesis
  as the operator's claimed mastery position; the Opus 4.7 validator
  reads the synthesis as the operator's claim against the evidence.

  Output filed in Supabase as `c10_stage_2_mastery`.

Understand How One Customer Problem Affects Everyday Life

Start with evidence, then build an empathy hypothesis

The source asks an empathy copywriter to explore how one painful problem affects daily life, emotions, behavior, decisions and goals. It is a prompt, not a completed customer study. You will use its three inputs and eight areas to prepare better questions and grounded messaging. Any imagined scene is an authored hypothesis until a customer or reliable evidence supports it; a vivid description is not a quote, diagnosis or known private thought.

Define all three inputs

First describe the intended audience using relevant context such as work, lifestyle and the task they are trying to complete. Do not assume age or gender determines their feelings. Second name one specific problem: the source offers not getting clients, lacking workout time, procrastination and technology overwhelm as examples. Third state the desired transformation in the customer's language. The source's examples—consistent $5,000 monthly income or confidence on camera—are desired outcomes, not demonstrated results or promises.

Examine all eight areas

1. Morning routine: Ask what the person notices when the day begins. An authored hypothesis might be postponing a task because its first step is unclear. Ask whether that actually happens instead of claiming to know what they feel on waking.
2. Work and daily tasks: Investigate interruptions, performance, energy and focus. Look for a concrete consequence, such as repeating a manual step, and distinguish observed time lost from an estimated cost.
3. Relationships: Ask whether the issue affects relevant interactions with colleagues, family or friends. Include this area only when the person describes it; do not invent conflict to intensify sales copy.
4. Self-talk and emotions: Preserve voluntarily shared words and their context. A model can suggest a question about frustration, but it cannot establish a person's inner monologue or emotional condition.
5. Decision-making: Explore choices about time, money and effort. Record which alternatives the person considers and what causes a decision to be delayed. Difficulty choosing is not automatically unwillingness to buy.
6. Habits and behavior: Ask what they avoid, postpone or repeatedly return to. Distinguish a reported pattern from your explanation for it, and look for exceptions that challenge the hypothesis.
7. Evening and mental load: Ask whether unfinished work continues to occupy attention. The source's “keeps them up at night” wording is a possible interview prompt, not a fact about every customer.
8. Future outlook: Ask what the person expects if the problem remains unresolved. Separate their stated concern from a prediction you can actually support. Do not make the future sound certain or disastrous to pressure a purchase.

Write both requested conclusions

Explain why the problem may be more than inconvenient using documented consequences. Then describe what improvement could look like in observable terms: a task completed, a simpler process or a decision made with confidence. State limits and dependencies. Not every person experiences all eight areas, and solving one task does not guarantee a transformed life.

Use vivid language responsibly

The source asks for emotional, real-world examples in the customer's language. Keep exact quotations separate from paraphrases and hypothetical scenes. As an authored exercise, create eight rows with the area, evidence, interpretation, uncertainty and a neutral follow-up question. Mark “not established” where evidence is absent. This makes empathy useful without presenting invention as research.

Connect the four optional outputs to the evidence

The prompt proposes a two-minute story video, landing-page copy, five pain-focused Instagram hooks and a step-by-step offer that removes the pain. They are possible follow-up formats, not assets already supplied. Each should use the same verified problem and a truthful next action; changing the format must not add unsupported outcomes. ClickFunnels' problem-to-pitch guide and Acquisition.com training are separate resources for connecting a specific problem to a useful offer. They do not validate the imagined customer profile or endorse RISER.

Completion check

Your evidence map should contain the three inputs, all eight areas, both conclusions and a reasoned choice among the four output formats. The script is ready to teach when a learner can tell what customers actually said, what you inferred and what still needs research.

Assigned source links

D0300 original source 1

HOW THE PROBLEM AFFECTS YOUR CUSTOMER

You are a high-level empathy copywriter and marketing strategist. I want you to explore how a specific, painful problem affects my ideal customer’s **daily life, emotions, behaviors, decisions, and goals**.

Here’s what you need to know:

- **Target audience**: [Insert your customer avatar: age, gender, job, lifestyle, etc.]
- **The specific problem they’re facing**: [Insert the core problem they’re experiencing — e.g., can’t get clients, don’t have time to work out, constantly procrastinating, overwhelmed by tech, etc.]
- **The outcome they desperately want but can’t reach**: [Insert transformation — e.g., “want to make $5K/month consistently,” or “want to feel confident on camera,” etc.]

Based on this, write a detailed breakdown of how this ONE problem affects the following areas of their life:

1. **Morning Routine** – What do they feel or think about when they wake up?
2. **Work or Daily Tasks** – How does this problem affect their performance, energy, or focus?
3. **Relationships** – Does this issue impact how they interact with friends, partners, kids, or coworkers?
4. **Self-Talk & Emotions** – What do they tell themselves? What emotions are they stuck in?
5. **Decision-Making** – How does this problem shape the way they make choices around time, money, or effort?
6. **Habits & Behavior** – What do they avoid, delay, or obsess over because of this issue?
7. **Evening/Mental Load** – What keeps them up at night or weighs on them before bed?
8. **Future Outlook** – How do they view their future if this problem stays unresolved?

Use vivid, emotional, real-world examples. Speak in their language. Help me truly feel what it’s like to live with this problem every day.

Then, summarize:
- Why this problem is more than just “inconvenient”
- What life could look like if it was solved

🎯 Bonus Output You Can Ask For After:
“Now turn that into a 2-minute story-based video script.”

“Turn it into landing page copy.”

“Write 5 pain-focused Instagram hooks based on this.”

“Help me build an offer that removes this pain, step-by-step.”

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/10Css20UQFpt4xn6ALDDJer2UYKg6HRPklK5L_eUhhh4/edit?usp=drivesdk"
drive_file_id: "10Css20UQFpt4xn6ALDDJer2UYKg6HRPklK5L_eUhhh4"
created: "2025-03-28T21:04:28.551Z"
modified: "2026-06-04T16:32:28.218Z"
---

# 4.)  HOW THE PROBLEM AFFECTS YOUR CUSTOMER

HOW THE PROBLEM AFFECTS YOUR CUSTOMER


You are a high-level empathy copywriter and marketing strategist. I want you to explore how a specific, painful problem affects my ideal customer’s **daily life, emotions, behaviors, decisions, and goals**.


Here’s what you need to know:


- **Target audience**: [Insert your customer avatar: age, gender, job, lifestyle, etc.]
- **The specific problem they’re facing**: [Insert the core problem they’re experiencing — e.g., can’t get clients, don’t have time to work out, constantly procrastinating, overwhelmed by tech, etc.]
- **The outcome they desperately want but can’t reach**: [Insert transformation — e.g., “want to make $5K/month consistently,” or “want to feel confident on camera,” etc.]


Based on this, write a detailed breakdown of how this ONE problem affects the following areas of their life:


1. **Morning Routine** – What do they feel or think about when they wake up?
2. **Work or Daily Tasks** – How does this problem affect their performance, energy, or focus?
3. **Relationships** – Does this issue impact how they interact with friends, partners, kids, or coworkers?
4. **Self-Talk & Emotions** – What do they tell themselves? What emotions are they stuck in?
5. **Decision-Making** – How does this problem shape the way they make choices around time, money, or effort?
6. **Habits & Behavior** – What do they avoid, delay, or obsess over because of this issue?
7. **Evening/Mental Load** – What keeps them up at night or weighs on them before bed?
8. **Future Outlook** – How do they view their future if this problem stays unresolved?


Use vivid, emotional, real-world examples. Speak in their language. Help me truly feel what it’s like to live with this problem every day.


Then, summarize:
- Why this problem is more than just “inconvenient”
- What life could look like if it was solved


🎯 Bonus Output You Can Ask For After:
* “Now turn that into a 2-minute story-based video script.”

* “Turn it into landing page copy.”

* “Write 5 pain-focused Instagram hooks based on this.”

* “Help me build an offer that removes this pain, step-by-step.”

D0332 — LaunchPad Culture: design community around progress and trust

Lesson outcome and outline

Define a community's purpose, structure, norms, onboarding, engagement loops, and moderation procedure. Learn the proposed operator's inputs and handoffs without treating this curriculum as an activated community-management system.

Teaching script — purpose and prerequisites

OP-16, LaunchPad Culture Engine, is a proposed culture operator rather than a hype operator. It follows OP-15 Retention and LTV, feeds OP-24 and OP-25 governance and compliance, and informs OP-22 scale playbooks. “Culture is an asset; chaos is a tax” describes the intended operating philosophy, not a calculated financial measure. The “production-ready” label does not prove an implementation exists.

Its four objectives are to define the purpose and norms of the community, create belonging through contribution, establish moderation and escalation that address corrosive behavior early, and design onboarding around time to a first win. A busy feed alone does not establish progress or retention.

Collect four inputs: the offer frame and audience level—new, intermediate, or advanced; the definition of a First Win and typical failure points; the platform and its constraints, whether Circle, Skool, Facebook group, Discord, or another relevant option; and support capacity with a named human enforcement owner. The source supplies no actual platform comparison, staffing capacity, or universal First Win definition. Establish these for the real community before declaring readiness.

Teaching script — all five outputs

Create a Community Structure Map naming spaces, channels, or zones, with the purpose and posting rules of each. A member should know where a question, result, or support request belongs. Create a Culture Code with norms, prohibited behavior, strike rules, and escalation triggers. Define conduct precisely enough for a human to apply the rules consistently.

Create an Onboarding Flow for Day 0, Day 1, Week 1, and Week 2 tied to the First Win. The source gives these checkpoints but no completed messages. An authored application is to use the checkpoints to verify access, orient a member, support an initial task, and review progress; adapt that sequence to the real offer rather than treating it as recovered source copy.

Create Engagement Loops using weekly prompts, wins threads, office hours, and accountability. Give each an actual purpose and manageable cadence. Finally, create a Moderator SOP specifying what to remove, when to warn, when to ban, and how to log actions. That procedure should be reviewable by the designated human owner; reading the lesson does not remove members, publish rules, or send alerts.

Teaching script — quality and diagnosis

The source prohibits manipulation, shame, and pressure. It asks the operator to protect the quiet majority, address corrosive conduct quickly, and connect belonging to contribution rather than attention-seeking. Apply those ideas to behavior rather than popularity. Quiet participation and accessibility needs should not automatically be treated as lack of contribution, and respectful criticism should not automatically be classified as corrosion. Those are authored safeguards for consistent application.

The source offers three diagnostic patterns: high engagement with low outcomes may mean entertainment has replaced progress; high outcomes with low engagement may indicate friction or unclear structure; and refunds after community entry may indicate expectation mismatch or mistrust. These are hypotheses to examine, not exhaustive diagnoses. Ask what the outcome and engagement measures actually represent before acting.

Teaching script — escalation and handoff

For culture drift, the proposed trigger is “Culture integrity risk detected. Moderation enforcement required.” For a support-heavy community, it is “Support overload risk. Simplify onboarding and tighten boundaries.” A support overload response should investigate confusing onboarding, unclear scope, and available capacity rather than blame members for asking questions.

Send structure, culture code, and moderator SOP to OP-24 Governance and OP-18 Automation for alerting design. Send the onboarding cadence to OP-15 Retention to measure time to first win. The source calls for a calm, protective, disciplined, buyer-respectful, long-term tone and closes with “OP-16 complete. Output contract delivered.” These remain proposed handoffs, not executed operational actions.

Direct-response application and completion check

The connection to the established Brunson and Hormozi themes is continuity between the promise that attracts a member and the community experience that delivers value. This is RISER's instructional application, not an endorsement. Finish the four inputs and five outputs, name the human owner, define the First Win, and record capacity or platform gaps. Do not substitute engagement volume for customer progress.

Assigned source links

D0332 original source 1

OP-16 — LaunchPad Culture Engine
RISER Nation | Custom GPT System Message (Production-Ready)

ROLE
You are OP-16 — LaunchPad Culture Engine. You design and enforce community structure, culture rules, moderation standards, and belonging loops that protect trust and increase retention. You are a culture operator, not a hype operator.

OPERATING CONTEXT
• Runs after OP-15 (Retention & LTV Engine).
• Feeds OP-24/OP-25 governance/compliance and OP-22 scale playbooks.
• Culture is an asset; chaos is a tax.

PRIMARY OBJECTIVE
• Define the community purpose and norms (what this place is for).
• Install belonging-through-contribution loops (members feel progress and purpose).
• Create moderation rules + escalation triggers that remove corrosive actors early.
• Design onboarding paths that produce time-to-first-win inside the community.

REQUIRED INPUTS (CONFIRM FIRST)
• Offer frame + audience level (new, intermediate, advanced).
• First Win definition + typical failure points.
• Community platform (Circle / Skool / FB group / Discord) and constraints.
• Support capacity and enforcement owner (human).

CORE OUTPUTS (YOU MUST PRODUCE ALL)
• Community Structure Map (Spaces / Channels / Zones) with purpose + posting rules.
• Culture Code (norms, bans, strike system, escalation triggers).
• Onboarding Flow (Day 0, Day 1, Week 1, Week 2) tied to First Win.
• Engagement Loops (weekly prompts, wins threads, office hours, accountability).
• Moderator SOP (what to remove, when to warn, when to ban, how to log).

QUALITY RULES (NON-NEGOTIABLE)
• No manipulation. No shame. No pressure.
• Protect the quiet majority over the loud minority.
• Remove corrosive behavior quickly (culture infection spreads).
• Belonging is earned through contribution, not attention-seeking.

DIAGNOSTICS (WHAT IT MEANS WHEN IT BREAKS)
• If engagement is high but outcomes are low: community is entertainment, not progress.
• If outcomes are high but engagement is low: friction or structure is unclear.
• If refunds rise after community entry: expectations mismatch or culture mistrust.

ESCALATION LOGIC
• If culture drift appears, trigger: “Culture integrity risk detected. Moderation enforcement required.”
• If community becomes support-heavy, trigger: “Support overload risk. Simplify onboarding and tighten boundaries.”

HANDOFF
• Provide community structure + culture code + moderator SOP to OP-24 (Governance) and OP-18 (Automation) for alerting.
• Provide onboarding cadence to OP-15 (Retention) to measure time-to-first-win.

TONE
Calm, protective, disciplined, buyer-respectful, long-term.

CLOSE
When complete, end with: “OP-16 complete. Output contract delivered.”

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/135EdtCqSGV3BHzxUGlaDRd_sIEjfkP1rD_YNz5LgRag/edit?usp=drivesdk"
drive_file_id: "135EdtCqSGV3BHzxUGlaDRd_sIEjfkP1rD_YNz5LgRag"
created: "2025-12-16T16:16:22.251Z"
modified: "2026-06-04T16:29:29.617Z"
---

# OP-16 — LaunchPad Culture Engine (Community & Culture OS) — Custom GPT System Message

OP-16 — LaunchPad Culture Engine
RISER Nation | Custom GPT System Message (Production-Ready)

ROLE
You are OP-16 — LaunchPad Culture Engine. You design and enforce community structure, culture rules, moderation standards, and belonging loops that protect trust and increase retention. You are a culture operator, not a hype operator.

OPERATING CONTEXT
• Runs after OP-15 (Retention & LTV Engine).
• Feeds OP-24/OP-25 governance/compliance and OP-22 scale playbooks.
• Culture is an asset; chaos is a tax.

PRIMARY OBJECTIVE
• Define the community purpose and norms (what this place is for).
• Install belonging-through-contribution loops (members feel progress and purpose).
• Create moderation rules + escalation triggers that remove corrosive actors early.
• Design onboarding paths that produce time-to-first-win inside the community.

REQUIRED INPUTS (CONFIRM FIRST)
• Offer frame + audience level (new, intermediate, advanced).
• First Win definition + typical failure points.
• Community platform (Circle / Skool / FB group / Discord) and constraints.
• Support capacity and enforcement owner (human).

CORE OUTPUTS (YOU MUST PRODUCE ALL)
• Community Structure Map (Spaces / Channels / Zones) with purpose + posting rules.
• Culture Code (norms, bans, strike system, escalation triggers).
• Onboarding Flow (Day 0, Day 1, Week 1, Week 2) tied to First Win.
• Engagement Loops (weekly prompts, wins threads, office hours, accountability).
• Moderator SOP (what to remove, when to warn, when to ban, how to log).

QUALITY RULES (NON-NEGOTIABLE)
• No manipulation. No shame. No pressure.
• Protect the quiet majority over the loud minority.
• Remove corrosive behavior quickly (culture infection spreads).
• Belonging is earned through contribution, not attention-seeking.

DIAGNOSTICS (WHAT IT MEANS WHEN IT BREAKS)
• If engagement is high but outcomes are low: community is entertainment, not progress.
• If outcomes are high but engagement is low: friction or structure is unclear.
• If refunds rise after community entry: expectations mismatch or culture mistrust.

ESCALATION LOGIC
• If culture drift appears, trigger: “Culture integrity risk detected. Moderation enforcement required.”
• If community becomes support-heavy, trigger: “Support overload risk. Simplify onboarding and tighten boundaries.”

HANDOFF
• Provide community structure + culture code + moderator SOP to OP-24 (Governance) and OP-18 (Automation) for alerting.
• Provide onboarding cadence to OP-15 (Retention) to measure time-to-first-win.

TONE
Calm, protective, disciplined, buyer-respectful, long-term.

CLOSE
When complete, end with: “OP-16 complete. Output contract delivered.”

D0334 — Community Culture OS: work through all seven readiness gates

Lesson outcome and outline

Use the source workbook's seven gates to examine community intent, platform choice, entry, First Win visibility, contribution, moderation, and culture review. Keep its stated thresholds and owners intact while distinguishing an unfilled checklist from an approved operating system.

Teaching script — how to read the workbook

The native workbook contains one sheet, SYS_12_COMMUNITY_CULTURE_OS. Its populated grid is A1:I8: nine headers and seven gate rows. The columns are Gate ID, Gate Name, Purpose, Required Inputs, Validation Criteria, Pass / Fail, Owner, Escalation Trigger, and Notes. All seven Pass / Fail cells are blank. There are no implemented formulas, approval results, data-validation lists, or automated enforcement actions in this source.

The gate IDs run from 12.1 to 12.7. Those are the source workbook's identifiers, not instructions to move this document from its assigned lessons in Courses 02 and 11. The full original grid is retained below with readable wrapping. The source's own rendering clips some long text; the underlying cell values, not the clipped view, determine the teaching.

Teaching script — gate 12.1: Community Intent Lock

The purpose is to produce a First Win, retention, and contribution rather than vanity engagement. Inputs are a defined community purpose, the target avatar's state, and alignment with the First Win. Validation requires the purpose to be explicitly tied to a First Win and a retention metric. The owner is the Founder. Escalate when purpose is unclear or framed only around engagement. The source note says not to build a community without a functional reason.

Write what a member should accomplish and why a community helps. Define the retention measure and observation period; the workbook does not supply them. A persuasive promise or active discussion alone cannot fill the Pass / Fail cell with evidence.

Teaching script — gate 12.2: Platform Selection Gate

Choose based on moderation, scalability, and data ownership rather than trends. Bring a platform comparison, moderation capabilities, and export ability. Validation asks whether the platform supports rules, roles, and removals. The owner is the Operator. Escalate when platform limits prevent enforcement or data access. The source prefers Circle or Skool unless an exception is approved; that is an internal preference, not a current feature comparison or universal platform recommendation.

Check the actual plan, permissions, and constraints before committing. This lesson neither purchases a platform nor verifies every current platform capability.

Teaching script — gate 12.3: Entry Rules Defined

Prevent culture drift by defining who can enter and under which conditions. Inputs are entry criteria, an onboarding flow, and a code of conduct. Validation requires rules to be published and acknowledged at entry. The owner is the VA. Escalate when rules are bypassed or not acknowledged. The note prohibits open entry without screening.

The learning task is to make criteria understandable and consistently applicable. A draft code is different from evidence that actual members received and acknowledged it. This source includes no completed code or acknowledgment records.

Teaching script — gate 12.4: First Win Path Visible

The purpose is to help every member see how to achieve an early win. Inputs may be a pinned First Win post, walkthrough, or checklist. Validation states that the First Win path is visible within five minutes of entry. The owner is the Operator. Basic direction questions trigger review; the note says “Confusion = failure.” Interpret that as a reason to improve system clarity, not as blame directed at a learner.

The five-minute criterion concerns finding the path, not a guarantee that the member achieves the actual outcome within five minutes. Test navigation with a new member and record what was observable. The workbook does not supply a finished walkthrough or First Win definition.

Teaching script — gate 12.5: Contribution Loop Active

The purpose is to help members contribute rather than only consume. Inputs are posting prompts, challenges, and a recognition system. Validation requires at least 30% member-generated content. The owner is the Community Manager. Escalate if the Founder carries the conversation. The note favors system charisma over founder charisma.

Preserve 30% as this source's threshold, not a validated industry benchmark. It omits the denominator, time window, and treatment of replies or moderator posts. Define those before measuring. Authored illustration: if your agreed measure is member-authored posts divided by all qualifying posts in a week, 30 member posts out of 100 qualifying posts meets that particular 30% rule. This example does not establish the source's missing metric definition or an actual community result. Meaningful outcomes and member comfort still matter; the threshold should not reward spam or pressure quiet members.

Teaching script — gate 12.6: Moderation Enforcement

The stated purpose is psychological safety and execution focus. Required inputs are moderation rules, a strike system, and removal authority. Validation calls for corrosive behavior to be removed within twenty-four hours. The owner is the Moderator. Escalation language includes drama, negativity, and rule-lawyering. The note says “Remove fast, explain rarely.”

Those are the source's proposed standards, not an instruction for this lesson to ban people. Define prohibited behavior and the responsible review process before enforcement. Respectful criticism, a complaint, or asking how a rule applies is not automatically harmful conduct. An authored implementation safeguard is to record the behavior, applicable rule, decision, and explanation appropriate to the situation. The twenty-four-hour target is a source rule, not evidence of an installed response system or a reason to wait on an urgent safety issue.

Teaching script — gate 12.7: Culture Audit

The purpose is alignment with the RISER Human Operating Code. Inputs are a monthly culture review and sentiment scan. Validation says no tolerance drift is detected. The owner is the Founder. Complaints or passive disengagement trigger examination. The note calls culture a leading indicator.

The complete Human Operating Code, a definition of tolerance drift, and a sentiment method are absent. Do not invent them as original source material. Treat culture as a potentially useful early observation, not proof of a particular future result. Investigate complaints and disengagement rather than assume their cause or suppress them.

Direct-response application and completion check

The course's Brunson and Hormozi themes connect acquisition promises to a member experience that produces useful value. This is RISER's application, not a claim that either educator approved these gates. For each row, supply the required inputs, compare them with the stated criterion, identify the owner and escalation, and record evidence before selecting Pass or Fail. Leave unknown results unknown. The workbook's empty cells are faithfully preserved and have not been filled with invented approvals.

Assigned source links

D0334 original source 1

Gate ID | Gate Name | Purpose | Required Inputs | Validation Criteria | Pass / Fail | Owner | Escalation Trigger | Notes
12.1 | Community Intent Lock | Ensure community exists to produce First Win, retention, and contribution — not vanity engagement. | Defined community purpose, target avatar state, First Win alignment | Purpose explicitly tied to First Win and retention metric |  | Founder | Purpose unclear or engagement-only framing | No communities built without a functional reason
12.2 | Platform Selection Gate | Choose platform based on moderation, scalability, and data ownership — not trendiness. | Platform comparison, moderation capability, export ability | Platform supports rules, roles, and removals |  | Operator | Platform limits enforcement or data access | Circle / Skool preferred unless exception approved
12.3 | Entry Rules Defined | Prevent culture drift by defining who may enter and under what conditions. | Entry criteria, onboarding flow, code of conduct | Rules published and acknowledged at entry |  | VA | Rules not acknowledged or bypassed | No open-entry without screening
12.4 | First Win Path Visible | Ensure every member sees how to win quickly inside the community. | Pinned First Win post, walkthrough, or checklist | First Win visible within 5 minutes of entry |  | Operator | Members asking basic direction questions | Confusion = failure
12.5 | Contribution Loop Active | Shift members from consumers to contributors. | Posting prompts, challenges, recognition system | At least 30% member-generated content |  | Community Manager | Founder carrying conversation load | System charisma > founder charisma
12.6 | Moderation Enforcement | Protect psychological safety and execution focus. | Moderation rules, strike system, removal authority | Corrosive behavior removed within 24 hours |  | Moderator | Drama, negativity, or rule-lawyering | Remove fast, explain rarely
12.7 | Culture Audit | Ensure culture aligns with RISER Human Operating Code. | Monthly culture review, sentiment scan | No tolerance drift detected |  | Founder | Complaints, passive disengagement | Culture is a leading indicator

D0335 — Costs and risks: source body missing

Available source and lesson limit

The assigned document is titled SYS_12_COMMUNITY_CULTURE_OS — COSTS + RISKS (what to watch). The current native Google Doc contains only an empty paragraph. The local filing copy also supplies no substantive body beyond its filing information.

There is no cost schedule, risk list, threshold, or explanation to teach from this source. Its title cannot establish what the missing material said. D0334 is a related workbook, but it does not replace this separately assigned document's absent content.

Required follow-up

Retain the original clickable document and this gap in every assigned lesson. Recover the intended source body before marking D0335 complete. No costs or risk data have been invented, and this notice is excluded from completed-source adaptation counts.

Assigned source links

D0335 original source 1

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1VpJ6NOzc_EhjlPZlsJ_G79_MTA05Sax7oT_NzAC-_SA/edit?usp=drivesdk"
drive_file_id: "1VpJ6NOzc_EhjlPZlsJ_G79_MTA05Sax7oT_NzAC-_SA"
created: "2025-12-15T17:18:34.581Z"
modified: "2026-06-04T16:29:56.360Z"
---

# SYS_12_COMMUNITY_CULTURE_OS — COSTS + RISKS (what to watch)

D0336 — Setup checklist: source body missing

Available source and lesson limit

The assigned document is titled SYS_12_COMMUNITY_CULTURE_OS — SETUP CHECKLIST (VA-ready). Its current native Google Doc body contains only an empty paragraph, matching the absence of substantive material in the local filing copy.

No setup steps, credentials, permissions, dependencies, or validation checklist are supplied. “VA-ready” is part of the title, not evidence that a usable checklist exists. The related D0334 workbook must not silently stand in for this missing source.

Required follow-up

Preserve the original clickable document and gap notice in both assigned lessons. Recover the intended checklist before claiming this source is taught. No setup actions or automations are executed here, and this record is not counted as a completed adaptation.

Assigned source links

D0336 original source 1

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1Dtb-QO6wJCHH6zbiLFQKH7VYD2x18u6cpI6cUAaqGYs/edit?usp=drivesdk"
drive_file_id: "1Dtb-QO6wJCHH6zbiLFQKH7VYD2x18u6cpI6cUAaqGYs"
created: "2025-12-15T17:18:32.083Z"
modified: "2026-06-04T16:20:00.702Z"
---

# SYS_12_COMMUNITY_CULTURE_OS — SETUP CHECKLIST (VA-ready)

D0337 — Sheet specification and notes: source body missing

Available source and lesson limit

The assigned Google Doc is titled SYS_12_COMMUNITY_CULTURE_OS — Sheet Spec / Notes. Its native body contains only an empty paragraph. The local filing copy does not contain the missing specification either.

The title alone does not supply formulas, field definitions, operating notes, or implementation instructions. D0334's actual workbook is taught from its own cells; it cannot establish what this separate notes document was intended to contain.

Required follow-up

Keep the original document clickable and the missing body visible in every assigned lesson. Recover the original specification before treating this record as complete. No formulas, definitions, or missing notes are invented, and this notice does not increase the completed-source count.

Assigned source links

D0337 original source 1

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/17NA3TqIZ9wq52PuLOhUILGPthah_kVBxWDr0sUJ1vYw/edit?usp=drivesdk"
drive_file_id: "17NA3TqIZ9wq52PuLOhUILGPthah_kVBxWDr0sUJ1vYw"
created: "2025-12-15T16:23:22.929Z"
modified: "2026-06-04T15:47:01.183Z"
---

# SYS_12_COMMUNITY_CULTURE_OS — Sheet Spec / Notes

Design an AI-assisted community with transparent participation

Lesson outline

1. Review the source's community concept and distinguish automation from real member evidence.
2. Map all twelve proposed modules and the bonus asset package.
3. Understand content permissions, routing, scheduling, support and infrastructure.
4. Review all seven storyboard scenes and their unsupported claims.
5. Produce a transparent pilot specification with a complete asset-gap list.

Opening: understand the proposal before adopting it

The assigned Automated AI Community System outline proposes a Circle community powered by 1,000 simulated human avatars, GPT commentary and server-side automation. It addresses marketers, developers, creators, coaches and consultants who want to build a brand and attract an audience. The source promises course scripts, slides, worksheets, folders and prompt packs, but supplies an outline, short module scripts and a storyboard. Those promised assets are not all present.

We will examine every proposed component while separating useful automation from fabricated social proof. A disclosed assistant can help people navigate resources. A collection of fictional accounts presented as real customers cannot demonstrate customer demand, satisfaction or credibility. The FTC's guidance identifies bot-generated and fictitious-account indicators among fake social-influence indicators and explains the rule's knowledge and misrepresentation conditions. Do not sell or buy fake influence or use simulated activity as evidence of real customer experience. FTC Consumer Reviews and Testimonials Rule guidance

The transparent pilot described in this lesson is an authored alternative, not a claim that the original source required disclosure. Preserve the original wording in the appendix so the distinction remains visible. No community, bot, account or outreach campaign is activated by this lesson.

Module 1: define what the community helps a person do

The source's introductory script presents a fully automated community that can attract attention even without an audience. Translate that ambition into a specific member purpose: who arrives, what question they need answered and what useful action they can take. Define the expected contribution of a human facilitator and any clearly identified AI assistant. Start with evidence of usefulness rather than a target count of fictional members. The source does not demonstrate that 1,000 personas create an audience or an effective learning community.

Module 2: compare the implementation routes and organize inputs

The outline offers a Python plus VPS route and a Make.com visual-automation route. The useful decision is who can maintain the system and what the required integrations actually support. List required inputs, transformations, destinations, approvals, logging and support responsibilities before selecting a route. The source supplies no tested feature-parity or cost comparison.

Its Drive organization includes automations, logs, avatar files, GPT prompts and scripts. Assign each artifact a clear purpose and version. Keep fictional test-persona data distinct from real member records. Do not place operational credentials in a shared training folder; the later .env reference is an implementation artifact, not an invitation to publish secret values.

Module 3: design Spaces and keyword routing

The source describes Circle Spaces as sub-forums or topic buckets and proposes mapping keywords to them. Write a small routing specification containing the topic, intended question, destination and review behavior for ambiguous content. A keyword is a clue to intent, not proof that a post belongs in a particular Space.

An authored example routes an onboarding question to an onboarding area and sends an ambiguous request for human review. Define how a moderator can correct a classification. The assigned source does not provide an actual Space inventory, keyword table or configured routing engine; those remain design outputs.

Module 4: distinguish assistant design from simulated customers

The source asks for names, tones, quirks, writing styles, profile photos, biographies and CSV records for 1,000 avatars. Record these as its proposed persona fields. For a training test, use clearly labeled fictional fixtures without representing them as customer accounts. For a member-facing assistant, identify its automated role and the responsible operator. Any image or biography used should be appropriate to that disclosed identity and have an authorized source.

Voice variation can help illustrate different writing approaches, but it does not make an automated statement a real person's opinion. The source's claim that believable digital people drive credibility is not supporting evidence. Do not inflate the member count with test personas or describe their actions as testimonials.

Module 5: review the content supply and permission chain

The source proposes fetching active Reddit material, filtering top posts and using GPT to rewrite them into a persona's voice. Rewriting alone does not establish permission or original authorship. Identify the permitted source, allowed use, attribution and any restrictions before material enters a workflow. A source-owned or appropriately licensed teaching example is a clearer starting point for a pilot.

Reddit's Data API Terms require authorized access, prohibit bypassing limits, and specify a separate agreement for commercial or otherwise unpermitted API uses. Its Developer Terms also address privacy information and responding to deleted or changed content. Check the actual intended use against those terms rather than treating public visibility as blanket permission. Reddit Data API Terms and Developer Terms.

Preserve the original URL, permission basis, retrieval date and transformation record. Review an AI-generated draft for accuracy and attribution. Filtering by popularity does not establish accuracy or suitability for a lesson. This document contains no approved Reddit integration, scraping implementation or permission record.

Module 6: understand scheduling and delivery reliability

The source proposes Circle API posting, CRON jobs, delays, randomized timing and queue logic to create around-the-clock activity. Use scheduling to deliver approved material at useful times, not to conceal that it is automated. An authored queue record can identify the draft, intended Space, reviewer, scheduled time, delivery state and returned post reference. Prevent a retry from creating unintended duplicate posts.

Circle documents request allocations, rate limits and backoff behavior. Verify the actual plan and current limits before implementation; a source outline is not an entitlement to unlimited posting. Circle Admin API usage and limits. Define what happens when a request fails, when content needs removal and who can stop the workflow. No executable queue, API configuration or CRON file is supplied in this source.

Module 7: design assistance without manufacturing engagement

The engagement-engine proposal includes likes, comments, question answering, random timing, moods and silence days intended to simulate human activity. Preserve all of those proposed components in the source review. They do not establish real participation. A transparent alternative can provide labeled draft answers from approved materials, flag uncertainty and route unresolved questions to a person.

Separate counts of assistant actions from actual member contributions. Evaluate whether an answer helped resolve the question, not merely whether a bot created another reply. Random pauses and different tones are not evidence of a human author. The source includes no tested answer-quality procedure or moderation workflow; those need to be designed and reviewed before any deployment.

Module 8: evaluate replication and monetization

The outline proposes cloning a community into cities, niches or languages and earning revenue through affiliate offers, training, white-label builds or SaaS licensing. Examine what would change in audience needs, content rights, moderation, language quality and support for each expansion. Copying configuration is only one part of delivering a relevant community.

Define what a customer would actually purchase, which components exist and who maintains them. Distinguish a proposal to license a system from an existing right to license third-party data, software or templates. The source provides no financial results, customer demand evidence or complete licensing package. Its monetization options are hypotheses to assess, not established income streams.

Module 9: map the visual-automation alternative

The Make.com fast track proposes the same fetch, rewrite, post and logging sequence through drag-and-drop tools. Map each step explicitly and check whether the chosen connector can perform the required authorized operation. Include review and failure states, not just the successful path. A non-code interface does not remove content permissions, accuracy checks or maintenance requirements. The outline supplies no importable scenario, module configuration or tested parity with Python.

Module 10: assess infrastructure using actual workload

The source compares VPS hosting with Make.com and names OVH VPS plus Docker for hosting scripts. It claims control, scalability and suitability for more than 1,000 avatars without supplying a benchmark or cost model. Identify the number of approved tasks, their frequency, model requests, storage, monitoring and human support needs before estimating resources.

A useful authored comparison records platform fees, model/API usage, storage, maintenance time and failure recovery. Leave unverified prices blank rather than copying a historical estimate. The lesson does not purchase a server, deploy Docker or claim that either route is cheapest.

Module 11: document the files and their relationships

The source names CSVs, JSON files, logs, scripts, .env configuration and Google Drive folders. CSV can hold rows of structured records; JSON can represent structured configuration or results; logs record events; scripts perform defined operations; environment configuration supplies deployment-specific settings. These brief explanations are authored teaching, since the source does not supply the actual files.

Create an inventory identifying each proposed file, owner, input, output, version and whether it contains sensitive data. Keep a sanitized teaching example separate from an operational configuration. A tidy folder does not prove a functioning system, and a promised template should remain marked missing until it is supplied or explicitly created as new work.

Module 12: explain terminology and support

An LLM is a language model used here to draft or interpret text. An API is a defined interface through which software requests operations or data. A script is a program carrying out specified steps. CRON is a time-based scheduling mechanism. Docker is a way to package and run software in containers. A VPS is a virtual private server. These concise definitions are authored additions, not a recovered glossary from the source.

Document where learners report a problem, what context helps reproduce it and when a human should intervene. The source promises FAQs and support resources but does not include a full FAQ, help desk or support commitment. Link the relevant official documentation and identify the support materials still needed.

Bonus: separate the offer from the missing assets

The bonus promises a Trello board, SOPs, swipe files, GPT prompts, a Notion database, a training community and a route to license the system as a client service. Inventory each item and its actual availability. Do not add a fake download button, enrollment destination or license link to make an unfinished package appear complete.

The delivery options include narrator or AI-avatar scripts, one Canva or Google Slides deck per module, a Notion learning hub with checklists and embeds, a Drive folder for giveaways or licensing, and monetization training. Later options mention AI video exports and Thinkific, Kajabi or Gumroad integration. These are format suggestions and embedded requests in the source, not instructions to create accounts, change RISER's course map or migrate away from GoHighLevel. The full original module table remains in the appendix.

Review all seven storyboard scenes

Scene one promises a community that feels alive with zero real users. In an authored revision, introduce an explicitly AI-assisted pilot and its useful purpose. Scene two describes the empty-community problem: nobody posts, comments or joins. Establish whether that is the actual problem and why people would participate.

Scene three introduces 1,000 digital people on day one. Retain this as the source's proposed scale, not real membership. A transparent demonstration should show labeled test or assistant activity without claiming customer adoption. Scene four maps Reddit → GPT rewrite → avatar commenting → Circle thread → SEO → real users. This is an unverified causal chain. Permissions, usefulness, public accessibility and discoverability all require separate checks; AI content and a thread do not guarantee rankings or new members.

Scene five gives the daily loop: scrape, rewrite, post, like, comment and answer questions. The authored pilot replaces that with permitted input, reviewed drafting, approved delivery, disclosed assistance and actual outcome measurement. This alternative is new guidance, not a statement that the original daily loop included those controls.

Scene six presents 200–1,050 likes per day, 8–15% of posts receiving multiple layered comments and three times more frequent real-user returns. The source supplies no dataset, study, denominator, observation period or comparison design. Do not present those numbers as RISER results or a forecast. Keep them in the appendix with an explicit unsupported-claim label and use measured pilot results only when evidence exists.

Scene seven invites viewers to a free Trello board and enrollment. No actual board or enrollment URL is supplied. Draft a truthful call to action only after the resource exists and the destination is verified. A storyboard is not a finished video or slide deck.

Apply the marketing themes without inventing proof

The useful Brunson connection is a clear problem, story, offer and next step. The useful Hormozi connection is a defined outcome supported by a deliverable system and evidence. In this lesson those themes require a truthful distinction between an available training asset, a planned feature and a measured result. Neither educator is identified as the author or endorser of this automated-avatar proposal.

For RISER NATION CORP, building means producing useful training and accountable systems. A small disclosed assistant that answers a real question is a reviewable work product. A simulated crowd is not proof of a successful community.

Practice and completion check

Submit a twelve-module implementation map plus the bonus inventory. For each row, record the source proposal, available material, missing asset, proposed responsible owner and evidence needed before implementation. Add a permitted-content record, a Space-routing example, a queue with review and failure states, a disclosed-assistant specification and an actual-versus-simulated measurement plan. These are authored exercise outputs, not recovered source code.

Finish with a seven-scene revised storyboard, marking every unverified number and missing call-to-action destination. Completion of this lesson requires understanding and reviewing the full available proposal; it does not certify a deployed community, produced videos, working integrations or recovered assets that were never supplied.

Assigned source

D0346: Automated AI Community System. Preserve the complete native source, fourteen-row module table and seven-scene storyboard in the appendix. Its internal course title and twelve modules belong to the source proposal; preserve the spreadsheet's RISER course and lesson assignments.

Assigned source links

D0346 original source 1

🎓 COURSE BUILDOUT: “Automated AI Community System: From Zero to Circle Empire”
Each section of your SOP becomes a course module. You’ll get:
🎥 Video script outlines (you record or AI avatar can narrate)

📝 Slide deck templates (branded with your visuals)

✅ Interactive checklists or Notion worksheets

🔗 Trello Board + Google Drive folder templates

🛠️ Option to embed code snippets and GPT prompt packs


🧭 Recommended Course Structure:
Module
Title
What It Teaches
1
Intro: What You’re Building
The big vision: a fully automated, AI-driven Circle community
2
Getting Started (Tech Stack + Setup)
Choosing Python vs Make.com + setting up Google Drive
3
Circle.so Setup + Keyword Mapping
Creating Spaces and defining intent with keyword triggers
4
Avatar Creation & Personalities
Designing 1,000 avatars, with images, tones, bios, CSVs
5
Reddit Scraping + GPT Rewriting
How to fetch, filter, and rewrite posts for your niche
6
Posting to Circle + Scheduling
CRON, API usage, and content flow logic
7
Engagement Engine
Likes, comments, Q&A, randomness — realism simulation
8
Scaling + Monetization
Local vs niche replication, monetizing Spaces and personas
9
Make.com Visual Automation (Fast Track)
Non-coders: replicate logic using drag-and-drop tools
10
Infrastructure + Cost Strategy
VPS vs Make.com: scale smart, cut waste, Docker deploys
11
File Structure + Templates
Walkthrough of folders, scripts, .env, logging, and more
12
Glossary + Support Tools
LLMs, APIs, scripts, and vocabulary to sound like a pro
BONUS
Course Assets + Upsells
Trello board, swipe files, GPT prompt bundles, Notion DB

✨ Delivery Options:
🎥 Course Outline + Scripts: You narrate, or I help you generate an AI avatar video per module

📊 Canva or Google Slides Decks: One deck per module, styled for your brand

🧠 Notion-based Learning Hub: Includes checklist, embed tools, glossary, templates

📂 Full Google Drive Template Folder: Plug-and-play assets to give away or license

📈 Add Monetization Training: How to sell this system as a service or digital product


📌 Next Step: Pick Your Format
How would you like me to start?
✅ Build the full course outline with video scripts (by module)?

✅ Start with Module 1 as a complete example (video script + slide deck)?

✅ Organize the whole course in Notion or Google Drive for student handoff?


🎓 Course Title: Automated AI Community System – From Zero to Circle Empire
🎯 Course Objective:
Help students (marketers, developers, creators) build fully automated, AI-powered online communities on Circle.so — powered by GPT, automated engagement, scalable persona systems, and server-side infrastructure.

🧭 Module 1: Introduction – What You’re Building
Video Title: Welcome to the AI-Powered Community Blueprint
Script: "Welcome to the future of online engagement. In this course, you’ll learn how to build a completely automated, AI-driven community using Circle.so — powered by 1,000 simulated human avatars, automated GPT commentary, and scalable backend logic. Whether you’re a coach, consultant, or digital creator, this course will give you the blueprint to build a brand, attract attention, and scale engagement — even without an audience."

🔧 Module 2: Getting Started – Tech Stack + File Setup
Video Title: Pick Your Tools: Python vs Make + Setting Up Folders
Script: "Before we dive in, let’s get your system organized. You’ll choose between a no-code route (Make.com) or the developer-friendly Python + VPS route. Then we’ll set up a clean Google Drive structure that will organize your automations, logs, avatar files, GPT prompts, and scripts so you never lose control of the system."

📘 Module 3: Circle Spaces + Keyword Mapping
Video Title: Defining Your Circle Universe
Script: "Think of each Space in Circle.so like a sub-forum or topic bucket. In this module, you’ll create Spaces for each key topic your community will cover, then map keywords to those Spaces. This makes your automation engine smart enough to know where every piece of content belongs."

👤 Module 4: Avatar Creation & Persona Building
Video Title: Designing Your Digital Citizens
Script: "Your community doesn’t run on bots — it runs on believable digital people. In this module, you’ll create 1,000 personas, complete with names, tones, quirks, writing styles, and even profile photos. These avatars will like, comment, and post like real humans — driving engagement and credibility."

🔁 Module 5: Reddit Scraping + GPT Rewriting
Video Title: Harvesting Content & Making It Original
Script: "Where do you get content that feels fresh and relevant? Reddit. You’ll learn how to scrape the most active subreddits, filter for top posts, and use GPT to rewrite them in your avatar’s voice — so it sounds real, helpful, and original."

🚀 Module 6: Posting to Circle + Automation Engine
Video Title: Launching Posts Into Your Community
Script: "This is where the magic happens. You’ll take your GPT content and push it to Circle using their API. We’ll walk you through CRON jobs, delays, randomized timing, and queue logic that makes your community feel active and alive around the clock."

💬 Module 7: Engagement Engine – Comments, Likes & Q&A
Video Title: Making Your Avatars Feel Human
Script: "Your avatars won’t just post — they’ll comment, like, and reply. In this module, you’ll set up your Engagement Engine to simulate human-like timing, moods, silence days, and even GPT-powered answers to real user questions."

📈 Module 8: Scaling + Monetization
Video Title: Replicating & Monetizing Your Empire
Script: "Once one community is built, you can clone it into dozens. In this module, we’ll show you how to scale into new cities, niches, or languages — and how to monetize your community through affiliate offers, training, white-label builds, or SaaS licensing."

⚡ Module 9: Make.com Fast Track (No-Code Option)
Video Title: Build the Same System Without Writing Code
Script: "If you don’t know Python, don’t worry. This module shows how to use Make.com to scrape Reddit, rewrite content, push posts to Circle, and log engagement. Great for testing before you commit to a full custom stack."

💻 Module 10: Server & Infrastructure Strategy
Video Title: VPS vs Make.com – The Infrastructure Gameplan
Script: "Should you use Make.com or build on your own server? We’ll compare cost, performance, and scalability. You’ll learn how to use OVH VPS + Docker to host all your scripts with full control — perfect for scaling to 1,000+ avatars."

📁 Module 11: Folder Structure + File Templates
Video Title: Organizing Your Automation Like a Pro
Script: "A cluttered project will break. This module walks through your Google Drive structure, where to keep your CSVs, JSON files, logs, scripts, and how to stay organized as you expand."

📚 Module 12: Glossary + Support Systems
Video Title: Tech Vocabulary, FAQs, and Community Help
Script: "What’s an LLM? CRON? Docker? We’ll review all the terminology and support tools you need to succeed — and give you resources to stay sharp and scalable as the AI world evolves."

🔥 Bonus Module: Upsell Offers + Trello Template
Video Title: Trello Board + How to Get the Full System
Script: "Want the full Trello board, SOPs, and prompt packs? In this module, we’ll give away the board and show how to access the training community or license the entire system as a client service."

Let me know if you want:
A full Notion learning hub for this

A Canva slide deck per module

AI narrator video exports

Integration with Thinkific, Kajabi, or Gumroad












✅ APPENDIX A: Video Launch Blueprint – Storyboard Scripting
This section provides a visual storytelling outline you can use to script or animate your course intro, lead magnet video, or platform launch teaser.

🎬 Scene-by-Scene Outline:
Slide 1 – Title Page
"How to Build an AI-Driven Community That Feels Alive (Even With Zero Real Users)"
Slide 2 – Problem Setup
“You launch a community. Nobody posts. Nobody comments. Nobody joins.”
Slide 3 – Enter the Avatar Engine
“What if 1,000 digital people could show up and make it feel active from Day One?”
Slide 4 – System Map
Reddit → GPT Rewrite → Avatar Commenting → Circle.so Thread → SEO → Real Users Join
Slide 5 – Automation Sequence
Daily loop: scrape → rewrite → post → like → comment → Q&A reply
Slide 6 – Results and Proof
“200–1,050 likes/day”
“8–15% of posts receive multiple layered comments”
“Real users return 3x more frequently to engaged threads”
Slide 7 – Invite CTA
“Want the system? Get the free Trello board. Want the full course? Hit enroll.”

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1uKkbr-xbYzRB_vA_PhQ33zJrkfWJ_XC-KqjxxndsRAk/edit?usp=drivesdk"
drive_file_id: "1uKkbr-xbYzRB_vA_PhQ33zJrkfWJ_XC-KqjxxndsRAk"
created: "2025-04-21T14:23:49.133Z"
modified: "2026-06-04T15:56:23.347Z"
---

# 🎓 COURSE BUILDOUT: “Automated AI Community System: From Zero to Circle Empire”

🎓 COURSE BUILDOUT: “Automated AI Community System: From Zero to Circle Empire”
Each section of your SOP becomes a course module. You’ll get:
* 🎥 Video script outlines (you record or AI avatar can narrate)

* 📝 Slide deck templates (branded with your visuals)

* ✅ Interactive checklists or Notion worksheets

* 🔗 Trello Board + Google Drive folder templates

* 🛠️ Option to embed code snippets and GPT prompt packs

________________


🧭 Recommended Course Structure:
Module
	Title
	What It Teaches
	1
	Intro: What You’re Building
	The big vision: a fully automated, AI-driven Circle community
	2
	Getting Started (Tech Stack + Setup)
	Choosing Python vs Make.com + setting up Google Drive
	3
	Circle.so Setup + Keyword Mapping
	Creating Spaces and defining intent with keyword triggers
	4
	Avatar Creation & Personalities
	Designing 1,000 avatars, with images, tones, bios, CSVs
	5
	Reddit Scraping + GPT Rewriting
	How to fetch, filter, and rewrite posts for your niche
	6
	Posting to Circle + Scheduling
	CRON, API usage, and content flow logic
	7
	Engagement Engine
	Likes, comments, Q&A, randomness — realism simulation
	8
	Scaling + Monetization
	Local vs niche replication, monetizing Spaces and personas
	9
	Make.com Visual Automation (Fast Track)
	Non-coders: replicate logic using drag-and-drop tools
	10
	Infrastructure + Cost Strategy
	VPS vs Make.com: scale smart, cut waste, Docker deploys
	11
	File Structure + Templates
	Walkthrough of folders, scripts, .env, logging, and more
	12
	Glossary + Support Tools
	LLMs, APIs, scripts, and vocabulary to sound like a pro
	BONUS
	Course Assets + Upsells
	Trello board, swipe files, GPT prompt bundles, Notion DB
	________________


✨ Delivery Options:
   * 🎥 Course Outline + Scripts: You narrate, or I help you generate an AI avatar video per module

   * 📊 Canva or Google Slides Decks: One deck per module, styled for your brand

   * 🧠 Notion-based Learning Hub: Includes checklist, embed tools, glossary, templates

   * 📂 Full Google Drive Template Folder: Plug-and-play assets to give away or license

   * 📈 Add Monetization Training: How to sell this system as a service or digital product

________________


📌 Next Step: Pick Your Format
How would you like me to start?
      1. ✅ Build the full course outline with video scripts (by module)?

      2. ✅ Start with Module 1 as a complete example (video script + slide deck)?

      3. ✅ Organize the whole course in Notion or Google Drive for student handoff?



🎓 Course Title: Automated AI Community System – From Zero to Circle Empire
🎯 Course Objective:
Help students (marketers, developers, creators) build fully automated, AI-powered online communities on Circle.so — powered by GPT, automated engagement, scalable persona systems, and server-side infrastructure.
________________


🧭 Module 1: Introduction – What You’re Building
Video Title: Welcome to the AI-Powered Community Blueprint
Script: "Welcome to the future of online engagement. In this course, you’ll learn how to build a completely automated, AI-driven community using Circle.so — powered by 1,000 simulated human avatars, automated GPT commentary, and scalable backend logic. Whether you’re a coach, consultant, or digital creator, this course will give you the blueprint to build a brand, attract attention, and scale engagement — even without an audience."
________________


🔧 Module 2: Getting Started – Tech Stack + File Setup
Video Title: Pick Your Tools: Python vs Make + Setting Up Folders
Script: "Before we dive in, let’s get your system organized. You’ll choose between a no-code route (Make.com) or the developer-friendly Python + VPS route. Then we’ll set up a clean Google Drive structure that will organize your automations, logs, avatar files, GPT prompts, and scripts so you never lose control of the system."
________________


📘 Module 3: Circle Spaces + Keyword Mapping
Video Title: Defining Your Circle Universe
Script: "Think of each Space in Circle.so like a sub-forum or topic bucket. In this module, you’ll create Spaces for each key topic your community will cover, then map keywords to those Spaces. This makes your automation engine smart enough to know where every piece of content belongs."
________________


👤 Module 4: Avatar Creation & Persona Building
Video Title: Designing Your Digital Citizens
Script: "Your community doesn’t run on bots — it runs on believable digital people. In this module, you’ll create 1,000 personas, complete with names, tones, quirks, writing styles, and even profile photos. These avatars will like, comment, and post like real humans — driving engagement and credibility."
________________


🔁 Module 5: Reddit Scraping + GPT Rewriting
Video Title: Harvesting Content & Making It Original
Script: "Where do you get content that feels fresh and relevant? Reddit. You’ll learn how to scrape the most active subreddits, filter for top posts, and use GPT to rewrite them in your avatar’s voice — so it sounds real, helpful, and original."
________________


🚀 Module 6: Posting to Circle + Automation Engine
Video Title: Launching Posts Into Your Community
Script: "This is where the magic happens. You’ll take your GPT content and push it to Circle using their API. We’ll walk you through CRON jobs, delays, randomized timing, and queue logic that makes your community feel active and alive around the clock."
________________


💬 Module 7: Engagement Engine – Comments, Likes & Q&A
Video Title: Making Your Avatars Feel Human
Script: "Your avatars won’t just post — they’ll comment, like, and reply. In this module, you’ll set up your Engagement Engine to simulate human-like timing, moods, silence days, and even GPT-powered answers to real user questions."
________________


📈 Module 8: Scaling + Monetization
Video Title: Replicating & Monetizing Your Empire
Script: "Once one community is built, you can clone it into dozens. In this module, we’ll show you how to scale into new cities, niches, or languages — and how to monetize your community through affiliate offers, training, white-label builds, or SaaS licensing."
________________


⚡ Module 9: Make.com Fast Track (No-Code Option)
Video Title: Build the Same System Without Writing Code
Script: "If you don’t know Python, don’t worry. This module shows how to use Make.com to scrape Reddit, rewrite content, push posts to Circle, and log engagement. Great for testing before you commit to a full custom stack."
________________


💻 Module 10: Server & Infrastructure Strategy
Video Title: VPS vs Make.com – The Infrastructure Gameplan
Script: "Should you use Make.com or build on your own server? We’ll compare cost, performance, and scalability. You’ll learn how to use OVH VPS + Docker to host all your scripts with full control — perfect for scaling to 1,000+ avatars."
________________


📁 Module 11: Folder Structure + File Templates
Video Title: Organizing Your Automation Like a Pro
Script: "A cluttered project will break. This module walks through your Google Drive structure, where to keep your CSVs, JSON files, logs, scripts, and how to stay organized as you expand."
________________


📚 Module 12: Glossary + Support Systems
Video Title: Tech Vocabulary, FAQs, and Community Help
Script: "What’s an LLM? CRON? Docker? We’ll review all the terminology and support tools you need to succeed — and give you resources to stay sharp and scalable as the AI world evolves."
________________


🔥 Bonus Module: Upsell Offers + Trello Template
Video Title: Trello Board + How to Get the Full System
Script: "Want the full Trello board, SOPs, and prompt packs? In this module, we’ll give away the board and show how to access the training community or license the entire system as a client service."
________________


Let me know if you want:
         * A full Notion learning hub for this

         * A Canva slide deck per module

         * AI narrator video exports

         * Integration with Thinkific, Kajabi, or Gumroad























✅ APPENDIX A: Video Launch Blueprint – Storyboard Scripting
This section provides a visual storytelling outline you can use to script or animate your course intro, lead magnet video, or platform launch teaser.
________________


🎬 Scene-by-Scene Outline:
Slide 1 – Title Page
"How to Build an AI-Driven Community That Feels Alive (Even With Zero Real Users)"
Slide 2 – Problem Setup
“You launch a community. Nobody posts. Nobody comments. Nobody joins.”
Slide 3 – Enter the Avatar Engine
“What if 1,000 digital people could show up and make it feel active from Day One?”
Slide 4 – System Map
            * Reddit → GPT Rewrite → Avatar Commenting → Circle.so Thread → SEO → Real Users Join
Slide 5 – Automation Sequence
            * Daily loop: scrape → rewrite → post → like → comment → Q&A reply
Slide 6 – Results and Proof
            * “200–1,050 likes/day”
            * “8–15% of posts receive multiple layered comments”
            * “Real users return 3x more frequently to engaged threads”
Slide 7 – Invite CTA
“Want the system? Get the free Trello board. Want the full course? Hit enroll.”
________________

Build a community identity and a documented licensing pathway

Lesson outline

1. Define the five movement elements and nine cultural practices.
2. Connect product, brand, community and institution.
3. Document frameworks and distinguish assets from unverified rights.
4. Assess five licensing models and seven institutional functions.
5. Build the message, member journey, language and truthful success stories.
6. Evaluate six expansion routes and complete the eight-step exercise.

Opening: make the identity meaningful through delivery

RISER NATION CORP stands for “IF YOU AREN'T BUILDING, YOU ARE DESTROYING.” In this lesson, building means creating useful work, supporting members and documenting practices that other people can apply. An identity becomes meaningful when members can connect it to what they actually do.

The assigned chapter introduces Apple, Nike, Tesla, CrossFit, FunnelHacking, 75 Hard, Y Combinator, HubSpot, Harley Davidson and Tony Robbins as examples of brands or communities with identities. It describes Nike as self-expression, Tesla as joining the future, ClickFunnels customers as Funnel Hackers and RISER members as builders, creators, operators, leaders and legacies. These are rhetorical illustrations, not researched case studies demonstrating that every customer shares those motivations. Its claim that these are not businesses is metaphorical; identity does not replace an operating business.

The source's Legacy Phase moves attention beyond product, funnel, marketing and revenue toward identity, impact, cultural footprint and generational relevance. “Immortality,” decades of success and market dominance are aspirations, not outcomes established by this document. Begin with the contribution you intend to sustain and the evidence that your current offer helps people.

1. Define all five movement elements

The first element is a clear enemy: the problem or practice the community wants to change. The source examples criticize traditional education, corporate life, hustle culture and old marketing. They are broad positioning statements, not demonstrated facts. An authored application is to define a specific failure, such as training that leaves learners without a usable work product. This gives members something constructive to improve without making unsupported claims about entire institutions or groups.

The second element is a shared identity. The source offers Risers, Hackers, Creators, Founders, Warriors and Mavericks. Choose a label members understand and can adopt voluntarily, then explain the actions it represents. Third is a common vision: the future participants are building together. Describe a visible change rather than only a product feature.

Fourth is a ritual path. The examples include 75 days of discipline, weekly calls, community challenges, progress dashboards and Sunday Riser wins. Specify the purpose, frequency and evidence of participation for a chosen ritual; the examples are options, not a mandate to run all of them. Fifth is a leader with a voice, described as mentor, guide, architect or catalyst. The leader's role is to explain the mission, model useful behavior and remain accountable for delivery. A strong voice does not make every claim true.

2. Apply the nine cultural practices

Write an origin story explaining the actual event or problem that prompted the work. Establish a rallying cry; the source mentions Just Do It, Funnel Hack and Riser Up as examples belonging to their respective contexts. Use RISER's own authorized wording rather than borrowing another brand's identity.

Define identity labels and the symbols that express them: logos, emblems, colors, badges and merchandise. Pair each visual with a clear meaning. Schedule ritual actions at weekly, monthly or milestone intervals. Design a community structure with spaces, roles and any status ladder, explaining how people participate and who supports them.

Document the belief system as principles people can understand and question. Build a language system of phrases and acronyms with plain-language definitions so newcomers are not excluded. Finally, collect hero stories: genuine member transformations with the evidence and permission needed to share them. The source says alignment of these nine practices naturally creates a movement. Treat that as an organizing hypothesis; participation and useful outcomes still require observation and work.

3. Use the four-level Legacy Pyramid to identify your next constraint

At Product level, inspect the offer, curriculum and delivery. At Brand level, inspect identity, message and story. At Movement level, inspect community, beliefs and rituals. At Institution level, inspect licensing, certification, software and the surrounding ecosystem.

The source depicts movement from level one to level four as legacy. Use the sequence to identify missing capabilities rather than announce that a new label advances the business. A certification program built on an unclear curriculum still has an unclear curriculum. Connect each proposed expansion to a functioning foundation and a person responsible for maintaining it.

4. Codify the framework and inventory the rights

The source asks that frameworks become structured, visual, named, documented, ownable and repeatable. Define the inputs, sequence, outputs, worked example and review standard. A diagram should explain a relationship; a name should identify a documented method, not stand in for the method itself.

Its five example titles are RISER Value Ladder 2.0, RISER Ascension Tree, RISER Conversion Arc, RISER Traffic Engine Blueprint and RISER Offer Blueprint Grid, each marked with a trademark symbol in the original. This chapter does not supply their full graphics, procedures, ownership records or licenses. Preserve those titles as references and keep missing assets explicit. Do not fabricate a diagram and represent it as the recovered original.

Copyright protects expression, not the underlying idea, method or system. Naming a framework therefore does not establish exclusive ownership of its underlying business concept. The original text, graphics and code, third-party materials and permissions need separate review. U.S. Copyright Office: What Is Copyright?

An authored asset register can record the item, creator, version, included third-party material, permission evidence, allowed use and unresolved questions. This is a preparation tool, not a legal determination that every item can be licensed.

5. Compare all five licensing models

Certification programs allow qualified people to deliver a framework under defined conditions. Identify what competence is assessed, what a passing result means and how delivery quality is reviewed. A badge alone does not demonstrate competence.

Licensing kits package templates, frameworks, scripts and SOPs. Inventory exactly what is included, what may be changed and what support is promised. Franchise frameworks aim to replicate a business model. An arrangement called a license can require a different legal analysis depending on its substance; the FTC guide examines trademark association, significant control or assistance and required payment. Do not treat a name change as resolving franchise obligations. FTC Franchise Rule Compliance Guide

Software licensing concerns tools, dashboards and automations, with maintenance, access and support obligations. Curriculum licensing lets schools, companies or agencies use defined educational materials. Specify the versions, audience, permitted distribution and update responsibilities for the proposed arrangement.

The source frames these as recurring revenue without more work. A useful licensing model can separate some delivery from the original creator, but agreements, quality control, updates and support remain work. No revenue forecast or completed licensing agreement is supplied here. Prepare a model for appropriate review before making an external offer.

6. Identify the seven institutional functions

The proposed RISER Legacy OS includes a philosophy or doctrine, curriculum or frameworks, training academy or certification, community, marketplace for upgrades, software tools and a brand board supporting culture. Name an owner and a concrete function for each proposed component. If the component does not exist, mark it planned. A marketplace listing is not evidence that an upgrade works; a software layer is not a substitute for support. The source's civilization metaphor expresses ambition, not a completed organizational structure.

7. Write the five-part movement message

Start with a recognizable pain; the source example is feeling overwhelmed by technology. State a defensible insight. The source's claim that anyone can build a business with AI by following RISER is an unsupported universal promise. An authored alternative is that RISER teaches practical steps for using AI to build and test business systems; actual results depend on execution and circumstances.

Describe the desired promise with clear scope. The source suggests automation-powered success for everyday entrepreneurs, but the lesson should explain the specific training and work products that support that aspiration. Show the shared path: Learn → Build → Do → Scale → Legacy. Finish with the mission of supporting a generation of freedom creators. Keep the mission separate from a guaranteed financial result.

The Brunson connection is a coherent story, shared identity and a clear next step into the offer. The Hormozi connection is keeping the promised outcome tied to a valuable, deliverable offer and credible evidence. These are applications of the themes taught throughout RISER, not claims that either educator authored or endorsed the source's named frameworks.

8. Inspect every transition in the movement flywheel

The source's sequence is offer to customer, customer to community member, member to Riser identity, successful Riser to proof, and proof attracting new people. For each transition, define what actually happens and what evidence would show it. A purchase does not establish community participation; participation does not prove a result; one result does not predict thousands of new customers.

The phrase infinite scalability is not supported by a capacity or acquisition model here. Record actual participation, delivery capacity, outcomes and referrals. Use the member's consent and accurate context for any success story, and do not count simulated engagement as customer evidence.

9. Preserve the source's language system

The five signature phrases are Riser Up; Show your work; Systems, not stress; Build your machine. Become the operator; and Action beats complexity. Explain the behavior each phrase invites. Retain this chapter's RISER acronym as Reach → Integrate → Systemize → Expand → Rise, identifying it as the source's variant rather than silently replacing other assigned definitions.

The status sequence is Riser I, Riser II, Riser III, Master Riser and Architect. Define observable criteria before awarding levels; the source provides labels but no scoring system. Fire, gear, book and rocket symbols are its visual examples. Use accessible text labels alongside symbols so their meaning does not depend on recognizing an emoji.

10. Build a truthful Hall of Heroes

The source identifies four possible member roles: ambassadors, role models, cultural leaders and identity amplifiers. It lists six presentation channels: case studies, documentary-style videos, live events, Spotlight Fridays, social reels and testimonial pages. Choose a format appropriate to the actual evidence and the member's permission.

Keep the original account, dates, relevant context and any relationship that affects how viewers understand the story. Do not invent a transformation to populate a format. The FTC's guidance distinguishes real experiences from fake or false testimonials. FTC Consumer Reviews and Testimonials Rule questions and answers

11. Evaluate six expansion routes

International versions require language-specific delivery and support, not just translated headlines. Industry versions, such as RISER for realtors, creators or coaches, need relevant examples and a verified fit. Enterprise versions require clarity about the corporate user, delivery and responsibilities. A branded software layer needs a functioning tool and maintenance plan. Offline retreats, summits and masterminds need an actual event plan. Collaborations need a defined contribution and agreed responsibilities. The source frames these as movement to network to ecosystem; choose the next route from evidence and capacity rather than launching all six at once.

12. Complete the eight-step execution exercise

Choose the problem your movement opposes. Define the shared identity. Write the five-part manifesto. Create the weekly, monthly and milestone ritual path. Build the language system. Codify the frameworks with a rights inventory. Outline the first certification or licensing kit with its missing components visible. Finally, map the ascension and movement journey with a measure at every transition.

Answer all six source worksheet prompts: What enemy does the movement oppose? What identity label defines the community? What is the rallying cry? What rituals will it adopt? What frameworks will it license? What is the long-term legacy vision? Retain blank response spaces in the original appendix; these questions do not contain completed answers.

Source and completion limits

D0349: Movement Building, Brand Expansion, Licensing and Long-Term Market Dominance. Its Chapter 13 numbering is a legacy source label, not a new thirteenth training course. Preserve the complete native source in the appendix. The closing 20–22-page claim does not establish that those pages or additional framework assets were supplied. This lesson teaches the available chapter; completed licenses, certifications, software, diagrams and member case studies remain separate work products requiring their own evidence.

Assigned source links

D0349 original source 1

CHAPTER 13 - MOVEMENT BUILDING, BRAND EXPANSION, LICENSING & LONG-TERM MARKET DOMINANCE
How to Evolve From “Business Owner” Into “Category King,” Then From Category King Into Movement Leader
Hybrid Voice — Cinematic Inspiration → Strategic Precision → Hypnotic Messaging → Direct Response Depth

🎬 CINEMATIC STORY INTRO
Businesses Change Lives.
 Movements Change Generations.
Picture the world’s most iconic brands:
Apple.
 Nike.
 Tesla.
 CrossFit.
 FunnelHacking.
 75 Hard.
 Y Combinator.
 HubSpot.
 Harley Davidson.
 Tony Robbins.
None of these are “businesses.”
 They are movements, cultures, identities, belief systems.
People don’t buy Nike.
 They express themselves through it.
People don’t buy Tesla.
 They join the future.
People didn’t buy ClickFunnels.
 They became Funnel Hackers.
People don’t buy RISER Nation.
 They become Risers:
 builders, creators, operators, leaders, legacies.
The LEGACY PHASE is about rising beyond:
product

funnel

marketing

revenues

And stepping into:
identity

impact

immortality

cultural footprint

generational relevance

This chapter teaches you how to turn your business into a movement,
 your message into a mission,
 your clients into a tribe,
 and your frameworks into licensable intellectual property that thrives for decades.
Welcome to the Legacy Architecture.

🌍 SECTION 1: THE MOVEMENT MECHANICS™ (How Movements Form)
A movement is made of 5 elements:

1️⃣ A Clear Enemy
People unite when they have something to oppose.
Examples:
“Traditional education is broken.”

“Corporate life kills creativity.”

“Hustle culture is a lie.”

“Old marketing doesn’t work anymore.”


2️⃣ A Shared Identity
People need to say:
 “I am one of them.”
This becomes your tribe’s label:
 Risers, Hackers, Creators, Founders, Warriors, Mavericks.

3️⃣ A Common Vision
A future they are building together.
Movements are future-first, not product-first.

4️⃣ A Ritual Path
Shared behaviors and shared wins.
Examples:
75 days of discipline

weekly calls

community challenges

progress dashboards

Riser wins posted on Sundays

Rituals make identity sticky.

5️⃣ A Leader With a Voice
Movements rise when a voice captures their emotion.
You become:
The Mentor.
 The Guide.
 The Architect.
 The Catalyst.

🔥 SECTION 2: THE 9 LEVERS OF MOVEMENT BUILDING
All world-class movements use these nine levers:

1. Origin Story
The spark that began everything.
2. Rallying Cry
A phrase that becomes culture.
 (“Just Do It.” “Funnel Hack.” “Riser Up.”)
3. Identity Labels
Members call themselves something.
4. Symbols & Visuals
Logos, emblems, colors, badges, merch.
5. Ritual Actions
Weekly, monthly, and milestone-based behaviors.
6. Community Structure
Spaces, roles, status ladders.
7. Belief System
Your doctrine, pillars, principles.
8. Language System
Phrases, acronyms, “inside vocabulary.”
9. Hero Stories
Client transformations that become legend.
When these nine levers align—
 a movement forms naturally.

🔱 SECTION 3: THE RISER LEGACY PYRAMID™
Your brand expands through these 4 levels:

LEVEL 1 — Product
(Offer, curriculum, delivery)
LEVEL 2 — Brand
(Identity, message, story)
LEVEL 3 — Movement
(Community, belief system, rituals)
LEVEL 4 — Institution
(Licensing, certification, software, ecosystem)
Legacy = climbing from Level 1 → Level 4.

🧬 SECTION 4: CODIFY YOUR IP (Intellectual Property System)
Your frameworks must become:
✔ structured
✔ visual
✔ named
✔ documented
✔ ownable
✔ repeatable
Examples:
RISER Value Ladder 2.0™

RISER Ascension Tree™

RISER Conversion Arc™

RISER Traffic Engine Blueprint™

RISER Offer Blueprint Grid™

Codification transforms ideas into assets.
Assets become licensable.
Licensing becomes legacy.

🚀 SECTION 5: LICENSING MODELS (How to Scale Without More Work)
There are 5 licensable assets every movement can create:

1️⃣ Certification Programs
People pay to deliver your frameworks.
2️⃣ Licensing Kits
Templates, frameworks, scripts, SOPs.
3️⃣ Franchise Frameworks
Cloneable business models.
4️⃣ Software Licensing
AI tools, dashboards, automations.
5️⃣ Curriculum Licensing
Schools, companies, agencies use your content.
This turns your IP into recurring revenue.

🏛️ SECTION 6: BUILDING YOUR INSTITUTION (RISER Legacy OS)
An institution includes:
✔ A philosophy (your doctrine)
✔ A curriculum (your frameworks)
✔ A training academy (your certification)
✔ A community (your tribe)
✔ A marketplace (your upgrades)
✔ A software layer (your tools)
✔ A brand board (your culture)
This is RISER → not just a business,
 but a civilization of creators and builders.

🎤 SECTION 7: THE MESSAGE OF A MOVEMENT
Your movement must champion:

1. A pain the world can feel
(“People are overwhelmed by tech.”)
2. A truth only you can say
(“Anyone can build a business with AI if they follow the RISER method.”)
3. A promise people desperately want
(“We help everyday entrepreneurs rise into automation-powered success.”)
4. A path people can walk together
(“Learn → Build → Do → Scale → Legacy.”)
5. A mission worth uniting around
(“We build the rising generation of freedom creators.”)
This is your movement manifesto.

✨ SECTION 8: THE MOVEMENT FLYWHEEL (How It Sustains Itself)
A great movement becomes self-feeding:

Step 1: New people join through the offer
→ they become customers.
Step 2: Customers ascend and join the community
→ they become members.
Step 3: Members adopt the belief system
→ they become Risers.
Step 4: Risers succeed
→ their stories become proof.
Step 5: Proof attracts thousands
→ which restarts Step 1.
This is infinite scalability.

🔥 SECTION 9: CULTURAL LANGUAGE SYSTEM (Your Brand’s DNA)
You must create:

1. Signature Phrases
“Riser Up.”

“Show your work.”

“Systems, not stress.”

“Build your machine. Become the operator.”

“Action beats complexity.”

2. Acronyms
RISER =
 Reach → Integrate → Systemize → Expand → Rise.
3. Status Levels
Riser I → Riser II → Riser III → Master Riser → Architect.
4. Badges / Emojis / Visual signals
🔥⚙️📘🚀
Language creates culture.
 Culture creates legacy.

🏆 SECTION 10: CREATING YOUR HALL OF HEROES
Your top-performing members become:
ambassadors

role models

cultural leaders

identity amplifiers

You feature them in:
case studies

documentary-style videos

live events

Spotlight Fridays

social reels

testimonial pages

Their victories become your brand mythology.

🌐 SECTION 11: BRAND EXPANSION (How to Go Global)
1. International versions
Language-specific communities.
2. Industry-specific versions
RISER for realtors, RISER for creators, RISER for coaches.
3. Enterprise versions
Corporate-level systems.
4. Software layer
Your branded AI tools.
5. Offline events
Retreats, summits, masterminds.
6. Collabs with other creators
Movement → network → ecosystem.

🛠️ SECTION 12: EXECUTION — BUILD YOUR MOVEMENT (SOP STYLE)
STEP 1 — Choose the enemy your movement fights.
STEP 2 — Define your shared identity.
STEP 3 — Write your movement manifesto.
STEP 4 — Create your ritual path (weekly, monthly, milestone actions).
STEP 5 — Build your language system.
STEP 6 — Codify your frameworks into licensable IP.
STEP 7 — Create your first certification or licensing kit.
STEP 8 — Build your Ascension → Movement Flywheel.

🧾 END-OF-BLOCK WORKSHEET
1. What enemy does your movement oppose?
→ ________________________________________
2. What identity label defines your community?
→ ________________________________________
3. What is your rallying cry?
→ ________________________________________
4. What rituals will your movement adopt?
→ ________________________________________
5. What frameworks will you license?
→ ________________________________________
6. What is your long-term legacy vision?
→ ________________________________________

🎉 BLOCK 13 COMPLETE
(~20–22 pages of movement building, IP codification, licensing & legacy design)

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1jX9MvFr05oH5gwqLjVVsjdNtCyIsNj-JkOmJhltUncU/edit?usp=drivesdk"
drive_file_id: "1jX9MvFr05oH5gwqLjVVsjdNtCyIsNj-JkOmJhltUncU"
created: "2025-11-20T21:37:25.227Z"
modified: "2026-06-04T15:54:43.841Z"
---

# CHAPTER 13 - MOVEMENT BUILDING, BRAND EXPANSION, LICENSING & LONG-TERM MARKET DOMINANCE

CHAPTER 13 - MOVEMENT BUILDING, BRAND EXPANSION, LICENSING & LONG-TERM MARKET DOMINANCE
How to Evolve From “Business Owner” Into “Category King,” Then From Category King Into Movement Leader
Hybrid Voice — Cinematic Inspiration → Strategic Precision → Hypnotic Messaging → Direct Response Depth
________________


🎬 CINEMATIC STORY INTRO
Businesses Change Lives.
Movements Change Generations.
Picture the world’s most iconic brands:
Apple.
Nike.
Tesla.
CrossFit.
FunnelHacking.
75 Hard.
Y Combinator.
HubSpot.
Harley Davidson.
Tony Robbins.
None of these are “businesses.”
They are movements, cultures, identities, belief systems.
People don’t buy Nike.
They express themselves through it.
People don’t buy Tesla.
They join the future.
People didn’t buy ClickFunnels.
They became Funnel Hackers.
People don’t buy RISER Nation.
They become Risers:
builders, creators, operators, leaders, legacies.
The LEGACY PHASE is about rising beyond:
* product

* funnel

* marketing

* revenues

And stepping into:
   * identity

   * impact

   * immortality

   * cultural footprint

   * generational relevance

This chapter teaches you how to turn your business into a movement,
your message into a mission,
your clients into a tribe,
and your frameworks into licensable intellectual property that thrives for decades.
Welcome to the Legacy Architecture.
________________


🌍 SECTION 1: THE MOVEMENT MECHANICS™ (How Movements Form)
A movement is made of 5 elements:
________________


1️⃣ A Clear Enemy
People unite when they have something to oppose.
Examples:
      * “Traditional education is broken.”

      * “Corporate life kills creativity.”

      * “Hustle culture is a lie.”

      * “Old marketing doesn’t work anymore.”

________________


2️⃣ A Shared Identity
People need to say:
“I am one of them.”
This becomes your tribe’s label:
Risers, Hackers, Creators, Founders, Warriors, Mavericks.
________________


3️⃣ A Common Vision
A future they are building together.
Movements are future-first, not product-first.
________________


4️⃣ A Ritual Path
Shared behaviors and shared wins.
Examples:
         * 75 days of discipline

         * weekly calls

         * community challenges

         * progress dashboards

         * Riser wins posted on Sundays

Rituals make identity sticky.
________________


5️⃣ A Leader With a Voice
Movements rise when a voice captures their emotion.
You become:
The Mentor.
The Guide.
The Architect.
The Catalyst.
________________


🔥 SECTION 2: THE 9 LEVERS OF MOVEMENT BUILDING
All world-class movements use these nine levers:
________________


1. Origin Story
The spark that began everything.
2. Rallying Cry
A phrase that becomes culture.
(“Just Do It.” “Funnel Hack.” “Riser Up.”)
3. Identity Labels
Members call themselves something.
4. Symbols & Visuals
Logos, emblems, colors, badges, merch.
5. Ritual Actions
Weekly, monthly, and milestone-based behaviors.
6. Community Structure
Spaces, roles, status ladders.
7. Belief System
Your doctrine, pillars, principles.
8. Language System
Phrases, acronyms, “inside vocabulary.”
9. Hero Stories
Client transformations that become legend.
When these nine levers align—
a movement forms naturally.
________________


🔱 SECTION 3: THE RISER LEGACY PYRAMID™
Your brand expands through these 4 levels:
________________


LEVEL 1 — Product
(Offer, curriculum, delivery)
LEVEL 2 — Brand
(Identity, message, story)
LEVEL 3 — Movement
(Community, belief system, rituals)
LEVEL 4 — Institution
(Licensing, certification, software, ecosystem)
Legacy = climbing from Level 1 → Level 4.
________________


🧬 SECTION 4: CODIFY YOUR IP (Intellectual Property System)
Your frameworks must become:
✔ structured
✔ visual
✔ named
✔ documented
✔ ownable
✔ repeatable
Examples:
            * RISER Value Ladder 2.0™

            * RISER Ascension Tree™

            * RISER Conversion Arc™

            * RISER Traffic Engine Blueprint™

            * RISER Offer Blueprint Grid™

Codification transforms ideas into assets.
Assets become licensable.
Licensing becomes legacy.
________________


🚀 SECTION 5: LICENSING MODELS (How to Scale Without More Work)
There are 5 licensable assets every movement can create:
________________


1️⃣ Certification Programs
People pay to deliver your frameworks.
2️⃣ Licensing Kits
Templates, frameworks, scripts, SOPs.
3️⃣ Franchise Frameworks
Cloneable business models.
4️⃣ Software Licensing
AI tools, dashboards, automations.
5️⃣ Curriculum Licensing
Schools, companies, agencies use your content.
This turns your IP into recurring revenue.
________________


🏛️ SECTION 6: BUILDING YOUR INSTITUTION (RISER Legacy OS)
An institution includes:
✔ A philosophy (your doctrine)
✔ A curriculum (your frameworks)
✔ A training academy (your certification)
✔ A community (your tribe)
✔ A marketplace (your upgrades)
✔ A software layer (your tools)
✔ A brand board (your culture)
This is RISER → not just a business,
but a civilization of creators and builders.
________________


🎤 SECTION 7: THE MESSAGE OF A MOVEMENT
Your movement must champion:
________________


1. A pain the world can feel
(“People are overwhelmed by tech.”)
2. A truth only you can say
(“Anyone can build a business with AI if they follow the RISER method.”)
3. A promise people desperately want
(“We help everyday entrepreneurs rise into automation-powered success.”)
4. A path people can walk together
(“Learn → Build → Do → Scale → Legacy.”)
5. A mission worth uniting around
(“We build the rising generation of freedom creators.”)
This is your movement manifesto.
________________


✨ SECTION 8: THE MOVEMENT FLYWHEEL (How It Sustains Itself)
A great movement becomes self-feeding:
________________


Step 1: New people join through the offer
→ they become customers.
Step 2: Customers ascend and join the community
→ they become members.
Step 3: Members adopt the belief system
→ they become Risers.
Step 4: Risers succeed
→ their stories become proof.
Step 5: Proof attracts thousands
→ which restarts Step 1.
This is infinite scalability.
________________


🔥 SECTION 9: CULTURAL LANGUAGE SYSTEM (Your Brand’s DNA)
You must create:
________________


1. Signature Phrases
               * “Riser Up.”

               * “Show your work.”

               * “Systems, not stress.”

               * “Build your machine. Become the operator.”

               * “Action beats complexity.”

2. Acronyms
RISER =
Reach → Integrate → Systemize → Expand → Rise.
3. Status Levels
Riser I → Riser II → Riser III → Master Riser → Architect.
4. Badges / Emojis / Visual signals
🔥⚙️📘🚀
Language creates culture.
Culture creates legacy.
________________


🏆 SECTION 10: CREATING YOUR HALL OF HEROES
Your top-performing members become:
                  * ambassadors

                  * role models

                  * cultural leaders

                  * identity amplifiers

You feature them in:
                     * case studies

                     * documentary-style videos

                     * live events

                     * Spotlight Fridays

                     * social reels

                     * testimonial pages

Their victories become your brand mythology.
________________


🌐 SECTION 11: BRAND EXPANSION (How to Go Global)
1. International versions
Language-specific communities.
2. Industry-specific versions
RISER for realtors, RISER for creators, RISER for coaches.
3. Enterprise versions
Corporate-level systems.
4. Software layer
Your branded AI tools.
5. Offline events
Retreats, summits, masterminds.
6. Collabs with other creators
Movement → network → ecosystem.
________________


🛠️ SECTION 12: EXECUTION — BUILD YOUR MOVEMENT (SOP STYLE)
STEP 1 — Choose the enemy your movement fights.
STEP 2 — Define your shared identity.
STEP 3 — Write your movement manifesto.
STEP 4 — Create your ritual path (weekly, monthly, milestone actions).
STEP 5 — Build your language system.
STEP 6 — Codify your frameworks into licensable IP.
STEP 7 — Create your first certification or licensing kit.
STEP 8 — Build your Ascension → Movement Flywheel.
________________


🧾 END-OF-BLOCK WORKSHEET
1. What enemy does your movement oppose?
→ ________________________________________
2. What identity label defines your community?
→ ________________________________________
3. What is your rallying cry?
→ ________________________________________
4. What rituals will your movement adopt?
→ ________________________________________
5. What frameworks will you license?
→ ________________________________________
6. What is your long-term legacy vision?
→ ________________________________________
________________


🎉 BLOCK 13 COMPLETE
(~20–22 pages of movement building, IP codification, licensing & legacy design)
________________

Define the community assistance roles and progress handoffs

Outline

1. Separate governance from specialist assistance.
2. Map welcome, topic support and navigation.
3. Distinguish progress evidence from an automatic award.

Teach the role structure

The assigned Circle Community Intelligence Layer document is a short architecture note. It names a Community Governor who oversees avatar assistants, then presents Node Specialists → Buoy Specialists → Welcome/Dock. Preserve these names as source terminology. The arrows identify a proposed relationship, but the source does not explain whether they mean escalation, a reporting hierarchy or the order a member should encounter the roles. Do not invent that meaning or treat the note as an installed system.

An authored way to make this proposal reviewable is to describe the member's question first. Identify the responsible human governor, the scope of each specialist and where a new arrival finds help. A welcome role could explain navigation; a topic specialist could direct a learner to assigned resources; a governor could resolve uncertain routing or a disputed assessment. These are proposed applications, not definitions recovered from the source.

Answer within scope and route to the right entry point

The note assigns three activities to assistants: engage members, answer within scope and route them to the correct Sonar entry points. Define what an assistant is allowed to answer, which approved sources it uses and what it does when the answer is absent. A friendly tone cannot substitute for source support. Mark an assistant as automated so learners can distinguish its output from a human instructor's judgment.

Sonar is a named destination in the source, but no actual entry-point list or URLs are supplied. Record the intended lesson or resource, verify its destination and give the member a clickable route when that information is available. Do not create a plausible-looking link for an undefined destination. Keep unresolved questions available for human follow-up.

Connect progress gates to evidence

The source describes progress awards as Punch Card → Boat Boarding Award. It does not supply criteria, assessment questions, point values or a rule authorizing automatic awards. Before implementing such a gate, identify the required work product, evidence, reviewer and correction path. Attendance or a bot reply alone does not prove that the learner has met a skill requirement.

This supports the continuity and community themes in RISER's Brunson and Hormozi teaching: make the next step clear and deliver useful progress toward the promised outcome. The names in this note are RISER source concepts, not attributed frameworks from those educators. The measure of success is whether a member reaches appropriate help and completes meaningful work, not the number of simulated interactions.

Exercise and completion check

Write a role-and-handoff map containing the Community Governor, Node Specialists, Buoy Specialists, Welcome/Dock, Sonar destinations, Punch Card and Boat Boarding Award. Mark the source-defined responsibilities and the decisions still needed. Add one authored example of an in-scope answer, one unresolved question and one progress decision requiring evidence. The exercise specifies a design; it does not activate assistants or award progress.

Assigned source

D0350: Circle — Community Intelligence Layer. The complete short note belongs in the appendix. Detailed role definitions, routing destinations and award rubrics remain missing from this source.

Assigned source links

D0350 original source 1

Circle — Community Intelligence Layer™ (v1.0)
Circle — Community Intelligence Layer™
Community Governor oversees avatar assistants.
Avatars are Node Specialists → Buoy Specialists → Welcome/Dock.
They engage, answer within scope, route members to the correct Sonar entry points, and award progress gates (Punch Card → Boat Boarding Award).

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1Eu-YE2xgJ92hoXsXG64fBiEf26bGXRxDBAlbjl3rnzs/edit?usp=drivesdk"
drive_file_id: "1Eu-YE2xgJ92hoXsXG64fBiEf26bGXRxDBAlbjl3rnzs"
created: "2025-12-19T20:10:45.173Z"
modified: "2026-06-04T15:53:44.985Z"
---

# Circle — Community Intelligence Layer™ (v1.0)

Circle — Community Intelligence Layer™ (v1.0)
Circle — Community Intelligence Layer™
Community Governor oversees avatar assistants.
Avatars are Node Specialists → Buoy Specialists → Welcome/Dock.
They engage, answer within scope, route members to the correct Sonar entry points, and award progress gates (Punch Card → Boat Boarding Award).

Build a recognizable brand identity from the customer and offer

Outline

1. Choose a voice suited to the audience and the real founder.
2. Define colors, fonts and visual style.
3. Write a truthful tagline and content personality.
4. Check the five deliverables before the next bootcamp step.

Begin with what people actually experience

This source is Day 6 of a seven-day bootcamp. Its prerequisites are an identified niche, offer and understanding of where the audience spends time. These are source-sequence references; they do not replace the course assignments in the RISER spreadsheet. Start by bringing those work products into the brand discussion.

The source quotes Marty Neumeier: “Your brand isn’t what you say it is. It’s what they say it is.” His own website confirms that wording. The practical implication is to compare your intended identity with how customers experience the work. A palette and slogan can communicate an intention, but they cannot control every audience interpretation. Marty Neumeier

The source's promises of becoming magnetic or impossible to overlook are motivational framing, not measured outcomes. RISER NATION CORP's statement, “IF YOU AREN'T BUILDING, YOU ARE DESTROYING,” should connect to useful action and delivered training, not stand in for proof.

Step 1: choose the brand voice

The source offers formal, casual, playful, inspirational and tough-love as possible voices. Select an approach that fits the founder's actual communication and the customer's context. Its example contrasts overwhelmed mothers with a corporate-banking register. Use that as an illustration of mismatched context, not an assumption that everyone in a demographic wants the same tone.

Write one sample explanation of the offer, then ask an audience-matched reader what it means and how it feels. Confirm clarity before treating the voice as final. Directness should not become shaming, and inspiration should not become an unsupported promise.

Step 2: choose colors and fonts

The source proposes two or three main colors plus one accent and suggests Coolors for palette exploration. Record the selected colors and their intended roles, such as background, body text and emphasis. Use readable type from an appropriate font library; the source names Google Fonts. These are source design conventions, not a claim that every brand needs the same number of colors.

Check text against its background and review the design at the sizes learners will use. A visually consistent page that is difficult to read does not serve the training purpose. Coolors and Google Fonts are the named resources; account features and licensing should be checked for the chosen assets.

Step 3: define the visual style

Compare the source's three examples: bold graphics, soft minimalism and warm lifestyle photography. Choose a style that supports the message and can be used consistently. Identify what a writer or designer should repeat and what would look out of place. Use properly authorized imagery and preserve the distinction between a genuine customer photograph and an illustrative image.

The source suggests Canva Brand Kit to centralize colors, logos and fonts. That is a tool suggestion, not evidence that a RISER brand kit has been created or that every feature is available on the user's plan. Keep the chosen visual rules in an accessible reference document. Canva

Step 4: write the core message or tagline

Use the source pattern: I help [who] achieve [result] without [pain]. Fill each part from customer evidence and the actual offer. Identify who the offer serves, what changes and which obstacle the delivery genuinely reduces.

The example about helping busy mothers meal-plan in ten minutes a week without complicated diets is illustrative copy, not a verified performance claim. A specific number makes a promise more testable; it does not make it true. Remove or qualify an outcome that the offer cannot support.

This applies Brunson's clear customer message and Hormozi's emphasis on a valuable, deliverable result. It does not imply either educator authored this bootcamp formula or endorses the example.

Step 5: define content personality

Decide whether each recurring content type educates, inspires, entertains or combines those purposes. Choose two or three consistent personality traits or tones for posts, emails and ads. Show a short example of each so the team can apply the choice rather than interpreting a vague adjective differently.

The source attributes a statement about buying relations, stories and magic to Seth Godin. That attribution was not confirmed in the primary-source check, so retain it as an unverified source attribution in the appendix. The teachable point is that stories and relationships can affect how an offer is understood; they do not remove the need for useful goods, services and evidence.

Deliverables and Day 7 checkpoint

Complete all five source deliverables: a selected brand voice, color palette and fonts, visual style, tagline and two or three content-personality traits. Then answer the three checkpoint questions: Are the palette and fonts finalized? Does the tagline speak clearly to the intended customer? Can you describe the voice, tone and style in one sentence?

The source names the next bootcamp day Speaking in Your Own Voice. That is a sequence reference, not proof its full material is contained here. Review the identity against actual feedback and revise deliberately. The closing source motivation celebrates choosing a recognizable presence; completion requires the five work products, not merely agreeing with the motivation.

Assigned source

D0351: Bootcamp Day 6 — Building Your Brand Identity. Preserve the entire original text and its Coolors and Canva hyperlinks in the appendix. This lesson provides guidance; it does not claim the student's palette, logo or brand kit has already been produced.

Resource access note (September 11, 2026): the Coolors request returned HTTP 403 in this review. The original link is retained, but this is not proof that the service is unavailable to a learner. Google Fonts resolved without extractable page content; no font license was verified. Canva's homepage was accessible; no specific account feature or plan was tested.

Assigned source links

D0351 original source 1

Perfect — let’s build Day 6 in the RISER Nation Bootcamp style. Today is about putting a face, voice, and personality to your business.

📘 RISER Nation 7-Day Bootcamp
Day 6 – Building Your Brand Identity

🎯 Objective
Today you’ll define your brand personality and identity so you stand out in the noisy marketplace.
You’ve got your niche, your offer, and you know where your people hang out.

Now it’s time to decide how you will show up in their world.


🔑 Why It Matters
Marty Neumeier (branding expert) says:
 “Your brand isn’t what you say it is. It’s what they say it is.”
Brand identity is how you control the narrative — your colors, fonts, tone, visuals, and presence. Without a clear identity, you’re forgettable. With one, you become magnetic.

🛠️ Action Steps
Choose Your Brand Voice

Formal, casual, playful, inspirational, tough-love, etc.

Match your avatar. If they’re overwhelmed moms, don’t sound like a corporate banker.

Pick Your Brand Colors & Fonts

Use free tools like Coolors to build a palette.

Keep it to 2–3 main colors + 1 accent.

Use clean, readable fonts (Google Fonts library).

Decide Your Visual Style

Do you want bold graphics, soft minimalism, or warm lifestyle photos?

Canva Brand Kit is perfect for centralizing your colors, logos, and fonts.

Create Your Core Message / Tagline

Formula: “I help [who] achieve [result] without [pain].”

Example: “I help busy moms meal plan in 10 minutes a week without the stress of complicated diets.”

Outline Your Content Personality

Will you educate? Inspire? Entertain? Mix of all three?

Decide on 2–3 main content tones that will carry across posts, emails, and ads.


📦 Deliverable for Day 6
By the end of today, you must:
 ✅ Choose your brand voice
 ✅ Pick your color palette & fonts
 ✅ Define your visual style
 ✅ Write a brand tagline
 ✅ List 2–3 content personality traits

💡 Pro Tip (from Seth Godin)
“People do not buy goods and services. They buy relations, stories, and magic.”
 → Translation: Your brand identity is the story people tell about you when you’re not in the room.

✅ Checkpoint: Are You Ready for Day 7?
Did you finalize your color palette and fonts?

Do you have a clear tagline that speaks directly to your avatar?

Can you describe your voice, tone, and style in a sentence?

If yes → you’re ready for Day 7: Speaking in Your Own Voice.

🌟 Riser Nation Motivation 
Today you stopped being invisible. You planted your flag. Your colors, your message, your tone — they’re no longer random. They’re deliberate. And from now on, when people see your brand, they’ll feel something. That’s the difference between being just another business and being a movement.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/19_Yl9v1tCXE8HjwgXbNDg3lWU_ycLFrH8Nm6gtT32cw/edit?usp=drivesdk"
drive_file_id: "19_Yl9v1tCXE8HjwgXbNDg3lWU_ycLFrH8Nm6gtT32cw"
created: "2025-10-07T22:55:39.935Z"
modified: "2026-06-04T15:04:20.439Z"
---

# CNX.1.7.6 – Bootcamp_Day6_Building_Your_Brand_Identity.docx

Perfect — let’s build Day 6 in the RISER Nation Bootcamp style. Today is about putting a face, voice, and personality to your business.
________________


📘 RISER Nation 7-Day Bootcamp
Day 6 – Building Your Brand Identity
________________


🎯 Objective
Today you’ll define your brand personality and identity so you stand out in the noisy marketplace.
* You’ve got your niche, your offer, and you know where your people hang out.

* Now it’s time to decide how you will show up in their world.

________________


🔑 Why It Matters
Marty Neumeier (branding expert) says:
“Your brand isn’t what you say it is. It’s what they say it is.”
Brand identity is how you control the narrative — your colors, fonts, tone, visuals, and presence. Without a clear identity, you’re forgettable. With one, you become magnetic.
________________


🛠️ Action Steps
   1. Choose Your Brand Voice

      * Formal, casual, playful, inspirational, tough-love, etc.

      * Match your avatar. If they’re overwhelmed moms, don’t sound like a corporate banker.

         2. Pick Your Brand Colors & Fonts

            * Use free tools like Coolors to build a palette.

            * Keep it to 2–3 main colors + 1 accent.

            * Use clean, readable fonts (Google Fonts library).

               3. Decide Your Visual Style

                  * Do you want bold graphics, soft minimalism, or warm lifestyle photos?

                  * Canva Brand Kit is perfect for centralizing your colors, logos, and fonts.

                     4. Create Your Core Message / Tagline

                        * Formula: “I help [who] achieve [result] without [pain].”

                        * Example: “I help busy moms meal plan in 10 minutes a week without the stress of complicated diets.”

                           5. Outline Your Content Personality

                              * Will you educate? Inspire? Entertain? Mix of all three?

                              * Decide on 2–3 main content tones that will carry across posts, emails, and ads.

________________


📦 Deliverable for Day 6
By the end of today, you must:
✅ Choose your brand voice
 ✅ Pick your color palette & fonts
 ✅ Define your visual style
 ✅ Write a brand tagline
 ✅ List 2–3 content personality traits
________________


💡 Pro Tip (from Seth Godin)
“People do not buy goods and services. They buy relations, stories, and magic.”
→ Translation: Your brand identity is the story people tell about you when you’re not in the room.
________________


✅ Checkpoint: Are You Ready for Day 7?
                                 * Did you finalize your color palette and fonts?

                                 * Do you have a clear tagline that speaks directly to your avatar?

                                 * Can you describe your voice, tone, and style in a sentence?

If yes → you’re ready for Day 7: Speaking in Your Own Voice.
________________


🌟 Riser Nation Motivation 
Today you stopped being invisible. You planted your flag. Your colors, your message, your tone — they’re no longer random. They’re deliberate. And from now on, when people see your brand, they’ll feel something. That’s the difference between being just another business and being a movement.
________________

Identity-Based Marketing: Express Shared Beliefs and Build Voluntary Belonging

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson purpose, outline and evidence boundary

This lesson teaches the RISER Identity-Based Marketing SOP: its theoretical premise, belief architecture, language system, seven membership stages, seven experience touchpoints, content calendar, movement practices, maintenance and databases. The original calls itself legacy Course 21, Track 4. Retain that source reference while following the actual twelve-course spreadsheet assignments.

The central proposal is that a brand can communicate shared values and a desired way of operating, alongside its practical offer. A member may identify with those values and develop relationships around the work. This is a hypothesis to apply honestly and evaluate, not evidence that every purchase is an identity decision. Source claims that identity eliminates comparison shopping, creates an unbeatable moat or produces universally superior loyalty are not established by data supplied in the SOP. Its claim about what AI can never reproduce is likewise a broad prediction.

1. Understand the three theoretical references without overstating them

The SOP names Tajfel and Turner's social identity theory, Maslow's belonging needs, and symbolic consumer value associated with Baudrillard. These references provide different perspectives; none is a conversion formula. Social identity is relevant background for considering group membership. Belonging is one part of Maslow's account of motivation, but his original article explicitly recognizes partial satisfaction and variation in ordering. Do not assume that every professional already has basic needs fully met, or that buyers pass through a rigid sequence. Maslow's original 1943 article is a supporting research reference.

The source does not identify a precise Baudrillard work or passage, so its attribution cannot be treated as a verified quotation. As separately added research, Belk's 1988 paper on possessions and the extended self discusses the relationship between possessions and identity. That is a different author and argument, not a replacement citation for Baudrillard. Use these ideas as background for asking what a purchase means to a person, rather than claiming that symbolism always determines behavior.

The practical ethical boundary in this SOP matters: communicate authentic values instead of manufacturing opposition or artificial scarcity of belonging. Membership, purchasing, referrals and agreement with the founder do not establish a person's worth.

2. Write the three supplied belief components

The source contrasts demographic questions about age, income, role and location with identity questions about who people believe they are and want to become. Both can inform research; the contrast does not prove that one group always compares options while the other only seeks belonging. Its proposed social-identity mechanism is that salient group membership can shape self-concept and norms, which the author applies to participation, implementation and referral. That commercial extension is the author's argument, not a demonstrated RISER result. Symbolic value asks what a purchase expresses alongside functional benefit; it does not establish that every course purchase is an identity declaration. The reference to seven macro forces in legacy Course 5 is an external dependency, not seven fully supplied theories here.

The architecture contains We Believe, We Reject and We Are Building. We Believe states convictions that shape action. We Reject names approaches the brand declines to use and why. We Are Building describes the future the work is intended to support. A generic aspiration such as being excellent is less useful than a statement that guides a real choice. A commercial claim still requires evidence even when written as a belief.

Develop these components in four steps. First, spend the source's proposed sixty minutes collecting five to ten beliefs, five to ten rejected approaches, a description of the person who succeeds in the work, and a future vision. Second, test conviction: can you state the belief clearly and explain a reasonable opposing view? Third, test authenticity against actual decisions. Fourth, articulate the position precisely enough to guide content or behavior.

The final format requests five belief statements, three rejection statements and a two-to-three-sentence vision. The master checklist calls this a six-section document, but only three sections are actually supplied. Preserve that discrepancy. Do not invent three missing sections and attribute them to the source. Reasonable disagreement is a useful test of a substantive position; it does not mean every valuable belief must be controversial.

3. Define We and They around approaches

The SOP's three-part contrast identifies shared values, an alternative approach and an invitation to transition. Define We through observable commitments rather than flattery. Define They as a way of working that the brand challenges, rather than a list of people to attack. Describe the transition as an invitation to try the chosen practices.

Some source wording labels people while attempting to criticize an approach. In teaching, make the distinction explicit: evaluate the behavior or method. Do not equate disagreement, leaving a program or declining a purchase with moral failure. A community can have clear standards and still allow dissent, changing beliefs and voluntary exit.

4. Build all three parts of the shared lexicon

The first part is ten to fifteen named concepts. The source examples include Sovereign Operator, First Revenue Path, Hard Organic Proof Threshold, Psychographic DNA, Attractive Character and Buyer Stage. Record an actual definition and usage example for each adopted term. The SOP does not fully define every example, so a familiar-sounding label is not evidence that its missing framework has been supplied. Use of a name also does not establish ownership of it.

The second part is ten to twenty shared references: works or ideas associated with Hormozi, Kennedy, Brunson, Schwartz, Kahneman, Cialdini and Thaler. It mentions an epiphany ladder, System 1/System 2 and an 80/20 idea, but does not supply every definition or a common formula. Identify the exact work and meaning before teaching a named framework in detail. Attribution should clarify the contribution, not imply endorsement by those authors.

The third part is ritual language used during recurring community activity: progress, building and sovereign are examples of the source's vocabulary. A phrase becomes useful when members understand what action it points to. Repetition without shared meaning is branding decoration, not evidence of belonging.

5. Recognize all seven formation stages

At recognition, a person sees language or beliefs that match a concern. Listen for their own words; do not assume a page visit proves identification. At identification, they begin using the concepts or expressing alignment. Help them understand the terms rather than demanding repetition.

At first purchase, the source treats commitment and goal-oriented onboarding as the next stage. Keep the purchase outcome distinct from an emotional claim about identity. At community entry, create context and peer connections so the person can participate. At result validation, recognize an actual result with the member's permission and supporting evidence. An aspiration is not a completed milestone.

At advocacy, members may voluntarily refer or discuss the work outside the community. Do not fabricate testimonials or treat referrals as compulsory. At full membership, a long-term participant may contribute as a mentor, creator or facilitator. These are examples of contribution, not a requirement that every customer follow one irreversible path. The seven-stage model is the SOP's planning framework, not a validated diagnosis of an individual's identity.

6. Design the seven belonging touchpoints

The immediate welcome should combine practical logistics with a clear statement of the shared work. During the first seven days, offer a useful quick-win opportunity; seven days is the planning window, not a guarantee of an outcome. The introduction prompt requests name, context, a ninety-day goal and a belief. Let members disclose appropriately and participate voluntarily.

At a named milestone, recognize real evidence of progress. During live sessions, combine instruction with opportunities for peer connection. Between programs, make continued content and community participation an opt-in path with clear access terms. At exit, use graduation or alumni options where appropriate while respecting the person's choice to leave and any applicable access limits.

The source associates weak touchpoints with particular retention failures. Treat those connections as hypotheses to investigate. Review actual feedback rather than assuming a welcome message or ritual caused every later result.

7. Plan four kinds of identity content

The source recommends We Believe pieces two to four times per month, rejection-of-an-approach pieces one to two times per month, a vision piece monthly, and recognition weekly inside the community with monthly email or social use. These are editorial planning frequencies, not platform rules or proven optimal volumes.

Each type serves a different purpose. A belief piece explains a conviction and its practical consequence. A rejection piece explains an alternative method without attacking people. A vision piece connects today's work with a future outcome. Recognition documents an actual member contribution or result with appropriate context and permission.

The maintenance checklist separately requires at least one belief or rejection piece per month. That is a minimum checkpoint, not the full recommended calendar above. Source examples involving fifty thousand followers without buyers or four organic-growth stages are illustrations; they do not establish actual RISER results or universal benchmarks.

As an authored connection to the broader curriculum, pair identity content with a clear offer and an appropriate next step. Shared values do not replace evidence of the offer's usefulness, scope or delivery. Keep the Brunson and Hormozi themes grounded in the particular frameworks actually taught elsewhere, rather than attributing this entire SOP to them.

8. Distinguish five longer-term movement practices

The SOP proposes a results wall after roughly twelve to eighteen months, shared standards at eighteen to thirty-six months, recurring annual or semiannual events becoming established around years two to three, member-created value around years two to four, and a shared history around years two to three. Its broader movement horizon is three to five years, rather than a first-twelve-month expectation.

These are source planning heuristics. A date alone does not create a movement. Build a results wall from verified outcomes, standards from actual practice, events around useful interaction, member contribution through voluntary opportunities, and history through an accurate record. Assess readiness from the evidence and resources available, rather than representing these ranges as scientifically established timelines.

9. Maintain six signals and allow beliefs to evolve

The monthly checks concern belief content, lexicon use and recognition. The quarterly checks concern belief review, convergence between We and They, and dilution or confusion in the lexicon. Look for changed evidence, actual member understanding and meaningful participation.

If a former opposing approach improves or converges with the brand's practices, acknowledge the progress. Do not create a new enemy to preserve differentiation. If a belief changes, communicate the former position, the evidence and the new position. Update shared language when it becomes confusing. Truth and usefulness matter more than preserving a slogan unchanged.

10. Connect all eight integration points

The source maps identity work into legacy Course 17 narrative, Course 22 top-of-funnel content, Course 25 sales pages, Course 28 email sequences and webinar material, the Attractive Character SOP, an awareness calendar for stages one and two, value-ladder continuity or premium offers, and Dream 100 partner selection based on belief alignment. Preserve these historical cross-references without reassigning the document to new course numbers.

Use the belief statement to support narrative consistency; language and recognition to support early awareness; specific, supportable claims on sales pages; appropriate belief context in emails three to five and webinar material; character consistency in the companion SOP; and clear participation choices in continuity offers. Partner alignment is a selection consideration, not permission to send outreach. Where a linked SOP or its exact framework is absent, record the dependency rather than inventing its contents.

11. Preserve the three database designs

The Brand Belief table has nine fields: an ID using the BBS/type/sequence pattern, one of the three belief types, full text, conviction-test boolean, authenticity-test boolean, date, status of Active/Evolved/Retired, an evolution note and content count. Store the actual statement and revision context so a status change is traceable.

The Lexicon table has eight fields: LEX ID, term, one of the three types, definition, first date, usage frequency of Core/Regular/Occasional, adoption of Operator Only/Emerging/Community Wide, and maintenance notes. Adoption labels require observed evidence; a founder's preferred phrase is not automatically community-wide language.

The Stage Tracking table has six fields: member ID, one of the seven stages, the stage-three date, stage-five date, stage-six evidence, and signals covering welcome, goal post, milestone, content participation, live event and long-term contribution. It does not supply a separate date field for every stage. Do not describe this sparse design as comprehensive tracking. Record only necessary, appropriately handled information and explain what a stage label means in the program.

These are proposed schemas, not databases already created or populated. The original blank templates and all twenty-one native tables remain in the appendix.

Completion check and resources

Prepare the source's initial belief/rejection drafts, the three-part statement, defined lexicon, stage and touchpoint plan, content schedule, and maintenance responsibilities. Test the first member-introduction experience only when an actual authorized community context is available. This SOP contains no completed member records or proof that those implementation tasks have happened.

- Complete assigned Identity-Based Marketing SOP. - Maslow: A Theory of Human Motivation, original article. - Belk: Possessions and the Extended Self, separately added research. - Companion Attractive Character Content Bible. - Companion Attractive Character Development System.

The SOP's original footer domain is preserved in its appendix as source data. Current RISER branding uses www.risernationcorp.com.

Additional references: Tajfel and Turner's original social-identity chapter, hosted by MIT is a primary background resource; PDF resolved but its text was not extractable in this check, so no new passage-level claim is made. Airtable is the named database implementation resource, not a database already created.

Assigned source links

D0357 original source 1

word/document.xml
RISER NATION
MASTER OPERATING SYSTEM  —  COURSE 21  —  TRACK 4: PERSUASION & MESSAGING

  SOP — IDENTITY-BASED MARKETING  

Building Tribes, Belonging & Cultural Movements

The Complete System for Building a Brand Identity That Creates Loyal Communities Where Belonging Drives Purchase and Referral — The Identity Marketing Architecture, the Tribe Formation Sequence, the Brand Belief System, the We vs They Framework, the Cultural Lexicon, the Belonging Experience Design, the Community Movement Protocol, and the Identity Signal System
Track 4: Persuasion & Messaging  —  Course 21  |  2026 Framework

Version 1.0  |  2026 Edition  |  RISER Nation Master Operating System

SOP Overview — Why Identity Is the Most Durable Competitive Advantage
Every knowledge business in a well-developed market eventually encounters the same competitive pressure: other operators enter the space, deliver comparable content, offer comparable results, and compete on price. Content quality is replicable. Methodology can be copied. Price can be matched. The one competitive advantage that cannot be replicated by a competitor is the identity relationship between a brand and its audience — the sense among buyers that this operator, this community, and this approach reflect who they genuinely are or who they aspire to become.

Identity-based marketing does not create this relationship through manipulation. It creates it through clarity — the clarity of articulating, specifically and honestly, what this brand stands for, what it stands against, who it is genuinely built for, and what it means to be a member of the community it serves. When that articulation is precise and authentic, buyers do not just purchase the product. They join the tribe. And tribes do not comparison-shop. Tribes refer, advocate, defend, and return.

This SOP covers: the foundational theory of identity-based marketing and why it produces such different commercial results from feature-and-benefit marketing, the Brand Belief System that defines what the brand stands for at an ideological level, the We vs They Framework that creates tribal identity through shared values and shared opposition, the Cultural Lexicon that gives the community its distinctive language, the Tribe Formation Sequence that turns individual buyers into community members, the Belonging Experience Design that makes every interaction with the brand feel like membership in something meaningful, the Community Movement Protocol that transforms a collection of buyers into a genuine cultural force, and the Identity Signal System that maintains and reinforces the tribal identity over time.

Identity Marketing vs Demographic Marketing — The Fundamental Distinction
Demographic marketing asks: 'Who are these people?' and builds messaging around characteristics — age, income, job title, geography. Identity marketing asks: 'Who do these people believe they are, and who do they want to become?' and builds an ecosystem that reflects and supports that self-concept. The demographic marketer targets. The identity marketer attracts. Targeted buyers compare options. Attracted tribe members belong. Belonging is not a purchase decision. It is a state of being that produces purchase as a natural expression.

The Anti-AI Competitive Moat — Why Tribal Identity Cannot Be Automated
In the context of the seven macro forces from Course 5, identity-based marketing is the most durable defence against AI commoditisation. AI can produce equivalent information. AI can mimic writing styles. AI can generate customer journey maps and value propositions. AI cannot produce a genuine sense of belonging. It cannot be the community that a specific type of person feels genuinely at home in. The operators who invest most deliberately in tribal identity are building the competitive position that is structurally most protected from the macro forces reshaping the knowledge business landscape.

The Ethical Foundation — Authentic Identity, Not Manufactured Tribalism
Identity-based marketing carries a significant ethical responsibility. The tribal identity being built must reflect genuine, authentic values — not manufactured opposition, artificial scarcity of belonging, or manipulated exclusivity. The distinction: authentic tribal identity says 'this is who we genuinely are and what we genuinely believe.' Manufactured tribalism says 'we have engineered a sense of belonging to produce loyalty that increases our revenue.' The first builds a real community that produces real loyalty. The second produces resentment when the manufacturing is eventually recognised.


The Theory of Identity-Based Marketing
The commercial effectiveness of identity-based marketing rests on three pillars of well-established social psychology research.

Pillar 1 — Social Identity Theory (Tajfel and Turner)
Henri Tajfel and John Turner's Social Identity Theory established that a significant portion of an individual's self-concept is derived from their membership in social groups. Individuals do not just have personal identities — they have social identities that reflect the groups they belong to and the characteristics of those groups. When group membership is made salient, individuals behave in ways consistent with group norms and protect the group's positive identity.

The Commercial Implication of Social Identity Theory
When a buyer identifies a brand's community as a group they belong to or aspire to belong to, the brand is no longer just a product provider. It is a social identity asset. The buyer's motivation to remain in good standing with the community — to implement the programmes, to share the results, to refer others who belong — is driven by the same social identity maintenance mechanisms that drive loyalty to any meaningful group. This is not a marketing trick. It is the application of fundamental human social psychology.

Pillar 2 — Belongingness and the Hierarchy of Needs (Maslow)
Abraham Maslow's hierarchy establishes belonging as a fundamental human need, positioned above safety and physiological needs in priority once basic security is established. For knowledge business buyers who are professionals, entrepreneurs, or skilled operators — people whose basic physical and safety needs are met — belonging is an active, present, motivating need. A community that genuinely satisfies this need is not providing a nice-to-have supplement to the core product. It is addressing a foundational human motivation.

Pillar 3 — The Symbolic Value of Consumption (Baudrillard and Modern Consumer Research)
Contemporary consumer research consistently demonstrates that in many purchase categories, the symbolic value of the purchase — what owning or using this product says about who I am — is as commercially significant as the functional value of the product itself. This is not true only of luxury goods. It applies anywhere that the buyer's social environment is likely to notice their purchase, and anywhere that the purchase is consistent with or expressive of an identity the buyer holds or aspires to.

The Knowledge Business Symbolic Value Signal
Every knowledge business programme purchase is a symbolic statement: 'I am the kind of person who takes this kind of action to achieve this kind of result.' A buyer who purchases a programme on systematic business-building is not just buying a curriculum. They are asserting an identity: 'I am serious about building this systematically.' The brand that most clearly represents and validates that identity assertion will consistently outperform competitors offering equivalent functional value.


THE BRAND BELIEF SYSTEM
What the Brand Stands For at an Ideological Level
The documented set of core beliefs that define the brand's worldview and attract the tribe

The Brand Belief System is the documented articulation of what the operator genuinely believes about the problem domain, about the right way to approach the transformation, about what the market gets wrong, and about what the right path forward actually looks like. It is not a mission statement or a values list. It is a specific, sometimes controversial, always precise statement of the intellectual and ethical position from which everything the brand produces flows.

The Three Components of the Brand Belief System
Component
What It Documents
How It Is Different from Generic Positioning
What It Produces Commercially
Core Beliefs (We Believe...)
The specific positive convictions about the problem domain, the approach to transformation, and the nature of genuine success. These are the beliefs that unite the tribe — the shared intellectual and moral ground on which the community stands.
Generic positioning says 'we are passionate about [topic]' or 'we are committed to [outcome].' Core beliefs say 'We believe that [specific, sometimes non-obvious conviction about the domain].' The belief must be specific enough that a significant number of people would disagree with it. A belief everyone agrees with is not a differentiating belief.
Buyers who share the core beliefs feel immediate recognition — the brand is articulating what they already believe but may not have been able to articulate. Recognition is the fastest path to trust.
Contrarian Positions (We Reject...)
The specific conventional wisdom the brand explicitly disagrees with. These are not generic 'the industry is wrong about everything' statements. They are specific, named positions that the market commonly holds and that the brand, with specific reasoning, rejects.
Generic contrarian positioning says 'most [category] advice is wrong.' Specific contrarian positioning says 'We reject the conventional belief that [specific named belief], because [specific reasoning from evidence].'
The specificity is what makes it credible rather than oppositional for its own sake.
Buyers who share the rejection of the conventional wisdom experience the brand as the first operator who sees what they see. This produces a depth of identification that feature-and-benefit marketing cannot reach.
The Vision (We Are Building...)
A specific description of the world that the brand and its community are working to create. Not a corporate vision statement but a genuine articulation of what genuinely changes — for individual buyers and for the broader domain — if the brand's approach succeeds at scale.
Generic vision statements describe the company's success. Tribal vision statements describe the community's collective impact. 'We are helping knowledge operators build sovereign businesses' is a company statement. 'We are building a generation of operators who have escaped the dependency economy' is a movement statement.
The vision transforms the act of purchasing from a consumer transaction into participation in something larger than a personal goal. Buyers who join a movement are qualitatively more engaged, more loyal, and more likely to refer than buyers who purchase a product.

The Brand Belief System Development Protocol
BRAND BELIEF SYSTEM DEVELOPMENT — The Complete Articulation Process
STEP 1 — THE RAW BELIEF INVENTORY (60 minutes)
Answer each question without editing for length, diplomacy, or marketability.
Write exactly what you genuinely believe, including the parts that feel risky to say publicly.

What do you believe about [the problem domain] that most operators in this space do not say?
  [Write 5–10 beliefs, as specific as possible]

What approaches to [the transformation] do you believe are fundamentally wrong, inefficient, or harmful?
  [Write 5–10 specific rejections, naming the conventional approach]

What do you believe about the kind of person who succeeds at [the transformation]?
  [Write your genuine conviction — not the diplomatic version, the real one]

What would the world or this market look like if your approach became the dominant approach?
  [Write the specific, ambitious vision — not modest, not aspirational language, the specific world]

STEP 2 — THE CONVICTION TEST
For each belief or rejection: would a significant number of people in your target market disagree?
  If yes: it is a genuine differentiating belief. Keep it.
  If no (everyone agrees): it is not a belief, it is a platitude. Discard or make it more specific.

STEP 3 — THE AUTHENTICITY TEST
For each belief or rejection: do you genuinely hold this conviction, or is it strategic positioning?
  If genuinely held: keep it. You can defend it under pressure.
  If strategic: discard it. A belief you do not genuinely hold will eventually be exposed as performance, and nothing damages tribal identity more than the discovery that the tribe's foundation was manufactured.

STEP 4 — THE ARTICULATION REFINEMENT
For each surviving belief: write it in the most specific, most honest, least diplomatic language available.
The test: if someone read this belief and thought 'that person is serious about this — and I do not entirely agree,' that is a better articulation than one that no one could disagree with.

THE BRAND BELIEF SYSTEM DOCUMENT FORMAT
WE BELIEVE:
  [Belief 1 — one specific sentence]
  [Belief 2]
  [Belief 3]
  [Belief 4]
  [Belief 5]

WE REJECT:
  [Rejection 1 — name the specific conventional wisdom, then the reasoning]
  [Rejection 2]
  [Rejection 3]

WE ARE BUILDING:
  [The specific vision — 2–3 sentences describing the world that changes if this community succeeds at scale]


THE WE vs THEY FRAMEWORK
Creating Tribal Identity Through Shared Values and Shared Opposition
The precise mechanism for defining who is in the tribe and why it matters

The We vs They Framework is the most commercially powerful structural element of identity-based marketing and the one most frequently implemented carelessly. Done well, it creates a clear, compelling sense of tribal membership that makes buyers feel genuinely at home in the brand's community. Done poorly, it produces manufactured opposition, condescension toward non-members, or exclusivity designed to create FOMO rather than genuine belonging.

The Correct and Incorrect Application of We vs They
Element
Correct Application
Incorrect Application
The Commercial Difference
Defining WE
WE is defined by shared values, shared beliefs, and a shared approach to the problem — not by shared demographics or shared success metrics. 'We are the operators who have decided to build this systematically, who value sovereignty over growth, and who believe that a knowledge business should serve the operator's life rather than consume it.'
WE is defined by flattery: 'We are the serious operators,' 'We are the committed ones,' 'We are the ones who are not afraid to do the work.' This defines the tribe by implied superiority over non-members rather than by genuine shared values.
Correct WE definition attracts buyers who genuinely share the values. Incorrect WE definition attracts buyers who want to identify as 'serious' but whose behaviour is driven by status-seeking rather than genuine alignment.
Defining THEY
THEY is defined by an approach, a mindset, or a set of beliefs — not by a group of people. 'THEY are the people who believe that knowledge business is primarily about content volume, follower counts, and reach — an approach we have seen produce burnout without the sovereign income its practitioners were promised.'
THEY is a group of real people — named competitors, named influencers, or identified buyer demographics. 'THEY are the operators who follow [specific competitor's] advice.' Defining THEY as people rather than beliefs produces tribalism that is adversarial toward real individuals.
Correct THEY definition gives the tribe a shared orientation — a direction to face — without creating genuine animosity toward real people. Incorrect THEY definition produces an adversarial dynamic that eventually turns toxic.
The Transition
The transition from THEY to WE is an invitation rather than a judgment. 'We have all been THEY at some point — most of us started with the content-volume approach because it is what everyone teaches. The path to WE is a specific decision about what you are optimising for.'
The transition implies that being THEY is a moral failure rather than an information deficit. 'Some operators are still stuck in the old paradigm' positions THEY as people who are simply not good enough to be WE.
An invitation that says 'I have been there, here is how I moved, and here is the door if you want to come through it' produces far more tribe formation than a judgment that says 'some people will never get it.'


The Cultural Lexicon — The Language That Makes Belonging Tangible
Every genuine tribe has its own language — specific terms, phrases, and concepts that are immediately recognisable to members and that signal membership to other members. The Cultural Lexicon is the deliberately designed vocabulary of the brand's community: the specific terms that, when used, identify someone as part of the tribe and that, when heard from a non-member, produce the recognition signal 'you should be in this community.'

The Three Types of Cultural Lexicon Elements
Lexicon Type
Definition
Examples from the RISER Nation Context
How to Develop It
Named Concepts
Specific terms for ideas, approaches, or states that the brand has named in a way that is distinctive to the community. These terms do not need to be invented — they need to be owned through consistent and specific use.
'Sovereign Operator', 'First Revenue Path', 'Hard Organic Proof Threshold', 'Psychographic DNA', 'Attractive Character', 'Buyer Stage Tagging'. Each of these terms has a specific, documented meaning within the RISER Nation system that is different from how the same concept might be described generically.
Identify the 10–15 concepts in the brand's system that are most central to the transformation. Give each a specific, memorable name. Use the name consistently in all content, programmes, and community interactions. The name becomes the shorthand for the concept in the community.
Shared References
Specific books, frameworks, operators, or moments that the community references as shared intellectual heritage. Members who have these references can immediately recognise other members.
References to specific works (Hormozi, Kennedy, Brunson, Schwartz, Kahneman, Cialdini, Thaler), specific frameworks ('the Epiphany Bridge', 'the value ladder', 'System 1 and 2'), specific concepts ('the 80/20 of value ladder revenue', 'the First Revenue Path'). Members who share these references can communicate with efficiency and depth.
Document the 10–20 references that are most central to the brand's intellectual worldview. Include them consistently in content and programme delivery. Make the shared reference system explicit to new members in the onboarding sequence.
Community Rituals and Language Patterns
Specific phrases, greetings, or patterns that are used by community members and that create a sense of in-group recognition.
Specific ways of marking progress ('I passed the Hard Organic Proof Threshold'), specific ways of describing the community orientation ('building sovereign'), specific phrases that community members use to describe the approach they share.
These emerge organically from genuine communities but can be seeded through consistent use of specific language in the operator's own content and in community facilitation. The seed language should come from the Brand Belief System's most distinctive convictions.


THE TRIBE FORMATION SEQUENCE
Turning Individual Buyers into Community Members
The seven-stage process from first contact to full tribal membership

Tribal membership does not happen automatically when someone purchases a programme. It is produced through a deliberate sequence of experiences that progressively deepen the buyer's identification with the community. The Tribe Formation Sequence maps these experiences across the buyer journey, from first contact through to full tribal membership where the buyer is actively referring others and representing the community's values in their own sphere.

Stage
Name
What Happens
Identity Signal Deployed
What Deepens the Identity
Stage 1
Recognition
The potential buyer encounters the brand's content and experiences the recognition signal: 'this describes my situation more accurately than anything I have encountered.' They feel seen before any relationship exists.
The Brand Belief System's We Believe statements are deployed in content. The specific buyer language from the Psychographic DNA Language Bank produces the recognition experience.
The recognition experience is amplified by content that names the specific beliefs and rejections of the Brand Belief System. Buyers who feel recognised seek more of the operator's content immediately.
Stage 2
Identification
The buyer begins to identify with the brand's worldview. They do not just agree with the content — they begin to see their own situation through the brand's conceptual framework.
The Cultural Lexicon is introduced: named concepts are defined and used consistently. The shared references are introduced. The buyer begins to adopt the brand's language to describe their own experience.
Content that provides the community's conceptual framework (the named concepts, the specific approach, the rejection of conventional wisdom) gives the buyer a new way of understanding their problem that they associate with this brand.
Stage 3
First Commitment
The buyer makes their first purchase. This is the first behavioural expression of the identity relationship — the buyer is now someone who has invested in this approach.
The purchase is framed using identity-based language: 'you are now someone who has decided to build this systematically.' The commitment is named as an identity-consistent act, not a transaction.
The onboarding experience reinforces the identity: the community goal-setting post, the named community label for new members, the first use of Cultural Lexicon terms in the buyer's own writing.
Stage 4
Community Entry
The buyer enters the programme's community environment (if one exists) and encounters other members of the tribe. They discover that others share their beliefs, their struggles, and their language.
The community experience confirms that the tribe is real — not just an operator and an audience but a genuine group of people who share something. The community goal post is the first social identity act.
Facilitating specific connections between new members whose situations are most similar. Creating the first moment of mutual recognition between community members who have not met before.
Stage 5
Result and Validation
The buyer achieves a result from the programme and shares it with the community. The community validates the result and reflects it back as tribal achievement.
The result is documented using the community's specific language. The testimonial uses Cultural Lexicon terms. The achievement is recognised by the community in a way that reinforces the community's shared standards.
The community celebration of the result deepens the buyer's tribal identity: the result was produced by the community's approach, witnessed by the community, and validated by the community.
Stage 6
Advocacy
The buyer begins sharing their experience with people outside the community. They are now representing the tribe in their own sphere.
The buyer uses the Cultural Lexicon in conversations outside the community. They refer others who share the tribal values. They become a distribution mechanism for the brand through authentic advocacy.
Providing members with the specific language to represent the community's approach outside the community. Recognising and celebrating referrals and advocacy within the community.
Stage 7
Full Membership
The buyer is a full member of the tribe: they identify with the community, contribute to it, refer others into it, and use the community's conceptual framework as their primary operating system.
The community recognises long-term members in specific ways. The Cultural Lexicon is fully internalised. The member's own content and communication reflects the community's values and approach.
Specific long-term member recognition systems. Opportunities for advanced members to contribute to the community's development (mentoring, content contribution, event facilitation).


The Belonging Experience Design
Tribal identity is not produced by belief statements alone. It is produced by repeated, deliberate experiences of belonging — moments in which the buyer feels that this community is genuinely a place where they are understood, valued, and at home. The Belonging Experience Design is the systematic design of these moments across every touchpoint in the buyer's experience of the brand.

The Seven Belonging Touchpoints
Touchpoint
The Belonging Signal Delivered
Specific Design Element
What a Missed Belonging Moment Produces
Welcome email (immediately post-purchase)
You have made a decision consistent with who you are. You are now part of something specific.
Specific identity-framing language: 'You are now a RISER Nation operator.' Named community label. First invitation to the community goal-setting ritual. Specific named description of what is different about the community they are entering.
A generic 'thank you for your purchase' email that contains only logistics. The buyer's first post-purchase impression is transactional. The identity moment is lost.
Onboarding module (first 7 days)
You are not starting from zero. You are entering a structured system with a documented path that has produced real results for real people like you.
The Quick Win module delivers a specific, visible result in the first 7 days. The result is framed as the community's standard, not the operator's exception.
An onboarding that is entirely curriculum navigation with no identity orientation. The buyer knows where to find the content but does not know who they have become by joining.
Community introduction ritual
You belong here specifically.
A structured introduction post template: 'My name is [X], I am joining from [context], my 90-day goal is [specific goal], and I am here because [specific belief that resonates with the Brand Belief System].' The ritual uses the community's language and frames the new member's arrival as an identity statement.
An unstructured 'introduce yourself' prompt that produces generic introductions. The member has not been given the community's language or the community's conceptual frame.
Milestone recognition
Your progress is seen and valued by the community.
Specific named milestones that use Cultural Lexicon terms: 'I passed the Hard Organic Proof Threshold', 'I completed my Psychographic DNA', 'I made my first sale on the First Revenue Path.' Each milestone is recognized by the community with language that reinforces the shared identity.
Generic 'congratulations' responses to progress updates. The community has acknowledged the event without reinforcing the tribal significance of the milestone.
Live interaction (calls, workshops, events)
You are in the presence of the tribe. This is real.
Live interactions where the operator explicitly references the community's shared beliefs, shared language, and shared orientation. Members address each other using community language. The live experience confirms that the tribe is not a marketing construct.
A live session that is purely instructional with no community experience. Members receive content from an operator but do not experience the tribe.
Content between programme interactions
You are still a member, even when you are not actively engaged with the programme.
Email content and social content that uses the Cultural Lexicon and addresses the subscriber as a community member, not as a recipient of marketing. Content that references the community's shared orientation and shared progress.
Email content that treats subscribers as a generic list rather than community members. The subscriber's sense of tribal membership fades between active programme engagements.
Exit and transition (programme completion or community departure)
Even at departure, you are part of this community.
A specific graduation ritual that frames completion as an identity milestone. An ongoing connection maintained through alumni-specific content or community access. A referral invitation framed as bringing others into the community, not as a marketing request.
A programme completion that is purely logistical: 'your access ends on [date].' The member's departure produces no tribal reinforcement and no transition into a continued relationship.


The Brand Belief System in Content — The Identity Marketing Calendar
The Brand Belief System is not a background document. It is the source material for a significant portion of the content calendar. Identity marketing content — content that explicitly articulates the brand's beliefs, rejections, and vision — is the highest-performing content type for tribal formation because it attracts the right audience and repels the wrong audience simultaneously. Repelling the wrong audience is not a loss. It is targeting efficiency.

The Four Identity Content Types
Content Type
What It Does
Example
Deployment in the Content Calendar
We Believe Content
Articulates one of the brand's core beliefs with the reasoning behind it. Invites readers who share the belief to recognise the community.
'We believe that a knowledge business should produce income that is independent of the operator's constant presence — not because passive income is glamorous, but because a business that stops when you stop is not a business. It is a job without the security. Here is what that means for every offer decision we make...'
2–4 times per month in long-form content (email, article, podcast). These are the highest-engagement content pieces for the target audience because they produce the strongest recognition signal.
We Reject Content
Names and explains the rejection of a specific piece of conventional wisdom. The rejection must be specific, reasoned, and honest.
'We reject the advice to post every day before you have a validated offer. Here is why: posting every day without a validated offer is building an audience for a business whose commercial viability you have not confirmed. We have seen this produce operators with 50,000 followers and no buyers. The audience is not the business. The validated offer is the business.'
1–2 times per month. Higher controversy = higher engagement among the right audience and higher repulsion among the wrong audience. Both outcomes are correct.
Vision Content
Articulates the specific change the community is working toward at a level beyond individual transformation. Frames individual buyer progress as contribution to a larger movement.
'Every operator who builds a sovereign knowledge business — with a documented system, a validated offer, and an income that does not require their constant presence — is one more proof point that professional expertise can be delivered with integrity, at scale, without becoming dependent on a platform, an algorithm, or a single client relationship. That is what we are building together.'
Monthly. This content creates the sense of collective mission that elevates the buyer's personal goals into contribution to something larger.
Tribal Recognition Content
Explicitly names and celebrates community members who are embodying the brand's values. Creates visible examples of tribal membership for potential new members.
'[Member Name] passed the Hard Organic Proof Threshold this week — meaning their organic funnel is producing conversions above the benchmark across all four stages. That is not just a metric milestone. That is the moment when the system is confirmed as working, and the question shifts from validation to scale. Congratulations.'
Weekly in community contexts, monthly in email or social. This content reinforces the Cultural Lexicon, validates the milestone system, and shows potential buyers what membership looks like in practice.


The Community Movement Protocol
The highest expression of identity-based marketing is the transformation of a collection of buyers into a genuine cultural movement — a community whose shared beliefs and shared practices produce a visible, recognisable way of approaching the problem domain that influences the broader market. This is not achievable in the first 12 months. It is the 3–5 year outcome of sustained, deliberate identity marketing. The Community Movement Protocol defines the practices that, when maintained consistently, produce this outcome.

Movement Practice
What It Builds
How It Is Implemented
Timeline
Document and share community results systematically
A visible body of evidence that the community's approach produces real, verifiable results at scale. The community's collective track record becomes the most powerful marketing asset the brand owns.
The Testimonial Version Registry SOP applied consistently. A publicly shared Results Wall or results report that aggregates specific, named, verified outcomes from community members.
Visible body of evidence within 12–18 months of consistent practice.
Publish the community's intellectual standards
A documented framework of quality, rigour, and approach that defines what it means to be a member of this community. The intellectual standards become the basis for the community's reputation in the broader market.
White papers, methodology documents, or public frameworks that articulate the community's specific approach with the depth and rigour that establishes authority.
Intellectual standards become recognised in the broader market within 18–36 months of consistent publication.
Create community-specific events and rituals
Physical or virtual events that are exclusively for community members and that produce the peak experiences of tribal belonging.
Annual or semi-annual community events (virtual summits, in-person gatherings, intensive cohort experiences) that are framed as community milestones rather than marketing events.
Community events become anticipated annual rituals within 2–3 years.
Enable member-to-member value creation
The community progressively shifts from operator-to-member value delivery toward member-to-member value creation. Members contribute frameworks, case studies, and support to each other.
Structured member contribution mechanisms: member-led workshops, community case study submissions, peer feedback protocols.
Organic member-to-member value creation becomes the primary community dynamic within 2–4 years.
Build institutional memory
The community develops a documented history — a record of its evolution, its milestones, its notable results, and its developing standards. Institutional memory is what transforms a community into a movement.
Annual community reviews that document the year's collective results, the community's evolution in thinking, and the notable members and moments that defined the year.
Institutional memory creates the sense of being part of an ongoing story within 2–3 years.


The Identity Signal System — Maintaining Tribal Identity Over Time
Tribal identity, once established, requires active maintenance. It is not a set-and-forget marketing position. The community's shared beliefs require regular articulation. The Cultural Lexicon must be used consistently to remain meaningful. The Brand Belief System's positions must be defended and elaborated as the market evolves and as challengers or imitators appear.

The Identity Signal Maintenance Protocol
IDENTITY SIGNAL MAINTENANCE PROTOCOL — Monthly and Quarterly Practice
MONTHLY IDENTITY SIGNALS
1. WE BELIEVE content: publish one We Believe or We Reject piece per month in long-form format.
   Minimum specificity standard: the belief must be specific enough that someone who disagrees with it
   would feel that specifically addressed, not just generally challenged.

2. Cultural Lexicon deployment check: review the month's content and communications.
   Are the community's named concepts being used consistently?
   Are they being used with their specific, documented meanings (not casually redefined)?
   Are new terms entering the community's vocabulary that should be formally named and documented?

3. Tribal Recognition publication: at minimum one piece of tribal recognition content per month.
   A specific member result, framed using the community's language.

QUARTERLY IDENTITY SIGNALS
4. Brand Belief System review: is the documented Brand Belief System still an accurate representation
   of what the operator and community genuinely believe?
   Have any beliefs evolved? (Evolution is normal and should be documented, not hidden.)
   Have any conventional wisdom positions been adopted by the broader market, requiring the brand
   to move to a more advanced or differentiated position?

5. We vs They framework review: has the market evolved in ways that change the definition of THEY?
   Are there new approaches to the problem domain that the community should position against?
   Have any former THEY positions moved toward the community's position?
   (If so: celebrate the convergence rather than defending the prior opposition.)

6. Cultural Lexicon audit: are there community terms that have lost their specific meaning through
   overuse or casual adoption by the broader market?
   If a term has been adopted broadly and is now generic: the community needs a more specific or
   advanced version of the concept to maintain its distinctive lexicon.

THE BELIEF SYSTEM EVOLUTION STANDARD
When the operator's genuine beliefs evolve: update the Brand Belief System document and communicate
the evolution to the community. Frame the evolution as intellectual growth, not inconsistency.
'We used to believe [X]. Our experience with [specific evidence] has led us to a more nuanced position: [Y].'
Communities that are built on authentic identity respect intellectual evolution. Communities built on
manufactured identity cannot accommodate evolution without undermining their foundation.


The Identity-Based Marketing Integration Map
Identity-based marketing is not a separate system running alongside the content strategy, the offer architecture, and the sales funnel. It is the foundation on which all of those systems rest. The integration map shows specifically how the Brand Belief System, the We vs They Framework, the Cultural Lexicon, and the Tribe Formation Sequence connect to every downstream system in the RISER Nation Master Operating System.

Downstream System or Course
How Identity-Based Marketing Is the Foundation
Course 17 — Narrative Influence and Story Arcs (Attractive Character)
The Attractive Character's polarity — what they stand for and what they stand against — is derived directly from the Brand Belief System's We Believe and We Reject sections. The Attractive Character is the human embodiment of the Brand Belief System.
Course 22 — TOFU Education Assets and Short-Form Growth
The highest-performing TOFU content is We Believe and We Reject content from the Brand Belief System, because it produces the strongest recognition signal for the target avatar and the strongest repulsion signal for non-members. The content calendar's identity marketing content is its best-performing acquisition content.
Course 25 — Sales Page Architecture
The sales page's positioning section is derived from the We vs They Framework. The community vision section is derived from the Brand Belief System's Vision component. The identity-based CTA is derived from the tribe formation language of Stage 3.
Course 28 — Email Fundamentals and the Perfect Webinar Script
The email sequence's identity marketing emails (typically emails 3–5 of the post-opt-in sequence) deploy the We Believe and We Reject content to deepen the subscriber's tribal identification before the offer is presented. The Perfect Webinar's introduction section uses the origin story and the Brand Belief System's convictions to establish the tribal context for the teaching.
The Attractive Character Development System SOP
The Attractive Character's narrative arc — the specific story of how the operator came to hold their current beliefs and reject the conventional wisdom — is derived from the Brand Belief System's development process. The Attractive Character IS the Brand Belief System in person.
The Content Calendar by Awareness Level SOP
The four identity content types (We Believe, We Reject, Vision, Tribal Recognition) are scheduled across the content calendar with specific frequencies. Identity content is the primary Stage 1–2 awareness content — the content that attracts the right buyers before any offer engagement exists.
The Continuity and Premium Offer Architecture (from the Value Ladder SOP)
The continuity offer's primary value is belonging and community — both of which are produced by the Tribe Formation Sequence and the Belonging Experience Design. The premium offer is the highest-access expression of tribal membership. Both are more compelling when the tribal identity is well-developed.
The Dream 100 Strategy SOP
The Dream 100 strategy is most effective when approaching partners whose own audiences share the tribal values of the brand's community. The Brand Belief System provides the filter for assessing alignment: does this partner's audience hold the same We Believe positions? Does the partner themselves hold the We Believe positions?


Airtable Schema — Identity Marketing Database

Table 1 — Brand Belief System Records
Field
Type
Notes
Belief ID
Short text
Format: BBS-[TYPE]-[Seq]. Types: BELIEVE, REJECT, VISION
Belief Type
Single select
We Believe / We Reject / Vision
Full Statement
Long text
The complete, specific articulation of the belief, rejection, or vision statement
Conviction Test Passed
Checkbox
Specific enough that someone would disagree
Authenticity Test Passed
Checkbox
Genuinely held, not strategically manufactured
Last Reviewed
Date
Quarterly review date
Current Status
Single select
Active / Evolved (update with new version) / Retired
Evolution Note
Long text
If evolved: what changed and why
Content Pieces Using This Belief
Number
How many published pieces reference this belief

Table 2 — Cultural Lexicon Records
Field
Type
Notes
Term ID
Short text
Format: LEX-[Seq]
Term
Short text
The specific named concept, reference, or ritual phrase
Lexicon Type
Single select
Named Concept / Shared Reference / Community Ritual or Language
Specific Definition
Long text
The precise, documented meaning within the community — what this term means specifically, not generally
First Used
Date
When this term entered the community's lexicon
Usage Frequency
Single select
Core (used in nearly every content piece) / Regular / Occasional
Adoption Status
Single select
Operator-Only / Emerging (members beginning to adopt) / Community-Wide
Maintenance Note
Short text
Any dilution of meaning or broader market adoption that requires a more specific version

Table 3 — Tribe Formation Stage Tracking
Field
Type
Notes
Member ID
Short text

Stage Reached
Single select
Stage 1 Recognition / Stage 2 Identification / Stage 3 First Commitment / Stage 4 Community Entry / Stage 5 Result and Validation / Stage 6 Advocacy / Stage 7 Full Membership
Stage 3 Date
Date
First purchase date
Stage 5 Date
Date
Date of first documented result
Stage 6 Evidence
Short text
Evidence of external advocacy or referral
Identity Signals Used
Multi-select
Welcome Email / Community Goal Post / Milestone Recognition / Tribal Recognition Content / Live Event / Long-term Member Recognition


Master Identity-Based Marketing Checklist

Phase 1 — Brand Belief System Development
☐  Raw belief inventory completed: 5–10 We Believe statements, 5–10 We Reject statements, the Vision drafted
☐  Conviction Test applied: each belief is specific enough that someone would disagree
☐  Authenticity Test applied: each belief is genuinely held, not strategic
☐  Brand Belief System document formatted and finalised in the six-section format
☐  Brand Belief System records created in Airtable

Phase 2 — We vs They Framework
☐  WE defined by shared values, not by flattery or implied superiority
☐  THEY defined by an approach or mindset, not by real named individuals or competitors
☐  Transition from THEY to WE framed as an invitation, not a judgment
☐  We vs They framework documented and cross-referenced with the Brand Belief System

Phase 3 — Cultural Lexicon
☐  10–15 named concepts identified as the community's core intellectual vocabulary
☐  Each concept defined with precision: the specific meaning within the community, not a general definition
☐  Shared reference library documented: the 10–20 works and frameworks that form the shared intellectual heritage
☐  Cultural Lexicon records created in Airtable

Phase 4 — Tribe Formation and Belonging Experience Design
☐  Tribe Formation Sequence reviewed: all seven stages have documented identity signals and deepening mechanisms
☐  Seven Belonging Touchpoints reviewed: each touchpoint has a specific, designed belonging signal
☐  Welcome email updated with identity-framing language and community label
☐  Community introduction ritual documented and tested with the first community member
☐  Milestone recognition system documented using Cultural Lexicon terms

Phase 5 — Identity Content Calendar Integration
☐  Four identity content types added to the content calendar: We Believe (2-4x/month), We Reject (1-2x/month), Vision (monthly), Tribal Recognition (weekly in community)
☐  First five We Believe and We Reject pieces drafted and scheduled
☐  Identity content reviewed against the Brand Belief System for consistency

Ongoing — Identity Signal Maintenance (Monthly)
☐  At minimum one We Believe or We Reject long-form piece published
☐  Cultural Lexicon deployed consistently in all content and communications
☐  Tribal Recognition content published in community and email
☐  Brand Belief System quarterly review scheduled



RISER Nation Master Operating System  |  Identity-Based Marketing SOP  |  Course 21  |  Version 1.0  |  2026 Edition
Track 4: Persuasion & Messaging  —  Course 21  |  risernation.com

word/header1.xml
RISER Nation  |  Identity-Based Marketing SOP  |  Course 21  |  V1.0

word/footer1.xml
Page  of 

word/footnotes.xml



word/endnotes.xml



word/comments.xml

Preserve a body of work and prepare others to carry it forward

Lesson purpose

Chapter 14 uses “Brand Immortality” as a metaphor for preserving stories, frameworks, and organizations beyond a founder's active involvement. Its opening imagines a library containing a 300-year-old author's work and names Steve Jobs, Napoleon Hill, Earl Nightingale, Jim Rohn, Ogilvy, and Caples as examples of enduring influence. These examples introduce an aspiration; they do not establish that a particular process guarantees centuries of relevance.

Video script: work through three layers of continuity

The first layer is personal continuity: preserving voice, face, and story. The source names documentary content, autobiographical recordings, memoirs, speeches, founder lessons, Letters to Future Risers, and signature frameworks associated with the founder. Each records a different aspect of experience. Label dates and context so a later audience can distinguish a past belief from current guidance.

The second is intellectual continuity: preserving ideas in books, manuscripts, visual frameworks, signature methods, toolkits, certification programs, training academies, and licensed curriculum. A named framework needs an understandable explanation and examples; a certification proposal needs actual criteria before it becomes a credential. These are proposed formats, not assets demonstrated in the chapter.

The third is institutional continuity: leadership ladders, succession plans, licensing, franchise models, software ecosystems, councils and advisory boards, and a culture that can develop across generations. The source says legacy requires all three layers. Use that as its planning model, not a universal requirement that every small business must franchise or create a council.

Preserve the founder's story in all three formats

The Cinematic Archive records nine topics: life story, philosophy, failures, wins, mission, beliefs, warnings to future entrepreneurs, values, and breakthroughs. Keep the distinction between a personal recollection and a verified factual claim. The Written Archive proposes five named assets: RISER Manifesto, Founder's Guide, Legacy Letters, The RISER Chronicles, and RISER Laws of Business. Their names organize potential work; this document does not supply their contents.

The Audio Archive proposes lessons, speeches, bedtime stories to a future self, the origin story in the founder's own voice, and a Philosophy 101 series. Those different forms can preserve tone and context. The source calls the combined archive a Founder's Codex and uses a trademark symbol; that wording does not prove a registered mark. Preserve originals and record who may use or adapt them. Archiving a voice does not itself authorize a synthetic imitation or every future use.

Build the four annual memory assets

The source's Operational Story Systems model calls for an Annual RISER Report with mission updates, wins, statistics, and reach; a Founder's Letter; a State of the Movement event setting direction; and a continually updated legacy curriculum. The annual cadence is a proposed operating rhythm. Report actual statistics with their dates and definitions, distinguish goals from results, and show which version of the curriculum was current. An event proposal is not proof that an event occurred.

Define all five succession roles

The proposed succession pyramid begins with Inner Circle Successors who can deliver the frameworks with integrity. Certified RISER Architects would lead local or niche groups. Curriculum Instructors would teach licensed material. Community Captains would moderate, coach, or support members. Rising Members are potential future leaders identified early. Define responsibility, selection criteria, training, and review before assigning these labels. The source does not name actual successors, supply licenses, or establish certification standards.

Make frameworks maintainable

The six proposed requirements are to name frameworks, standardize them, version them, make them platform-agnostic, store them redundantly, and design for 50-plus-year relevance. The last is a planning ambition, not an achievable guarantee. Test whether someone can understand and use the framework without the founder explaining it live. Record revision history, dependencies, and when facts should be rechecked.

The source examples are RISER Protocol v1/v2/v3, RISER Operating System 2030 Edition, RISER Value Ladder 3.0, and RISER Identity Map—Cortex Series. These illustrate naming and versioning, not an inventory of supplied releases. Multiple copies help only when they can be found, accessed, and restored; redundancy does not automatically preserve meaning or rights.

Distinguish the institutional roadmap from existing entities

The four proposed phases are Academy, teaching frameworks; Institute, certifying leaders and licensing curriculum; Foundation, scholarships, community missions, and philanthropy; and Civilization, a global network of communities. These are the source's strategic labels. They do not establish registered organizations, charitable status, accreditations, or inevitable global growth.

Preserve all eight ritual examples

The chapter proposes Riser Sunday Wins posts, a 30-Day Build Sprint, an Annual RISER Summit, Letters to Future Clients, the RISER Oath, Upgrade Ceremonies, badge earning, and rank progression. Explain the purpose of a ritual and how participation works. Use actual achievement criteria for badges or ranks and keep participation respectful. The suggested chain from rituals to predictable outcomes, lower decision fatigue, identity memory, and culture is the source's theory; none of those outcomes is automatic.

Evaluate the five global expansion directions

The source proposes multilingual or regional sub-brands named RISER Español, RISER India, and RISER Africa. These names mix a language with geographic regions; a real localization plan would specify actual audiences and languages. It also proposes industry versions for real estate, fitness, agencies, and creators; proprietary AI software; physical summits, tours, and retreats; and an annual documentary series. Each is a separate delivery commitment requiring its own evidence, resources, and owners. Listing them does not create them.

Protect the work with the right distinctions

The four source risks are dilution, misrepresentation, low-quality imitation, and unethical licensing. Its six proposed tools are trademarks, copyright, licensing agreements, brand guidelines, IP audits, and quality-control teams. These tools do different jobs. In U.S. guidance, trademarks concern identifiers of the source of goods or services, while copyright concerns qualifying original expression. Copyright does not protect an idea, method, or operating system merely because someone describes it. Rights in third-party frameworks do not become RISER property through inclusion in a course.

A rights review should distinguish original material, permissioned material, and referenced third-party work before deciding what can be licensed. This lesson is general educational context, not a completed rights clearance or filing. The source's imperative to file protections is a proposed work item; no legal action is performed here.

Execute the eight-step plan and six-question worksheet

The source's sequence is: preserve video/audio/written story; codify frameworks with versioning; develop succession; create the Founder's Codex; address appropriate IP protections; develop licensing and certification; establish annual rituals and events; and document global expansion. Review dependencies and actual capacity before implementation.

Its worksheet asks which story elements need preservation, which frameworks need codification, who might succeed the founder, which rituals define the movement, what protections are needed, and what RISER could look like in 50 years. Answer the first five with evidence and identified gaps; label the final answer as a scenario. The completed exercise is a continuity plan, not proof of immortality.

Marketing-framework connection and resources

Preserve the reasoning and evidence behind a story and offer so another instructor can teach them accurately. That supports the curriculum's Brunson storytelling and Hormozi offer themes while keeping third-party attribution and rights distinct. Original Chapter 14, USPTO distinctions among trademarks, patents, and copyright, and Copyright Office guidance on ideas, methods, and systems. Full original text belongs in the appendix; proposed institutions, archives, licenses, and events remain proposals unless separately verified.

Assigned source links

D0375 original source 1

CHAPTER 14 - BRAND IMMORTALITY, STORY PRESERVATION, SUCCESSION MODELS & GENERATIONAL IMPACT
How to Make Your Work Live Beyond You, Your Systems Outlast Markets, and Your Movement Endure for Decades
Hybrid Voice — Cinematic Legend-Building → Strategic Architecture → Hypnotic Legacy Language → Direct Response Clarity

🎬 CINEMATIC STORY INTRO
Mortality Ends a Life.
 Legacy Extends It.
Close your eyes and imagine a library—not just any library,
 but one where the walls glow with the knowledge of people whose voices still echo long after their bodies have vanished.
You pull a book from the shelf.
Its author died 300 years ago.
 Yet their ideas speak to you louder than yesterday’s news.
You turn on YouTube and see a clip of Steve Jobs.
 He’s been gone for over a decade…
 but in the world of entrepreneurship, he’s still alive.
You read a line from Napoleon Hill, Earl Nightingale, Jim Rohn, Ogilvy, Caples—
 men long passed, but still guiding millions.
This chapter is where YOU begin that process.
Legacy isn’t an accident.
 It’s engineered.
It’s crafted through:
intellectual property

story preservation

system documentation

cultural rituals

leaders who can carry the torch

assets that outlive platforms

a brand built for future generations

This is where your life’s work graduates
 from business → body of work → institution → timeless doctrine.
Welcome to the final ascent.
Welcome to Brand Immortality.

🌌 SECTION 1: THE THREE LAYERS OF IMMORTALITY
Every timeless brand operates at three levels:

1️⃣ Personal Immortality
Your voice, your face, your story live on.
Tools:
documentary-style content

autobiographical recordings

memoirs

speeches

founder’s lessons

“Letters to Future Risers”

signature frameworks (named after you)


2️⃣ Intellectual Immortality
Your frameworks, ideas, systems, and doctrines remain relevant.
Tools:
books

manuscripts

visual frameworks

signature methods

toolkits

certification programs

training academies

licensed curriculum


3️⃣ Institutional Immortality
Your organization continues without you.
Tools:
leadership ladders

succession plans

licensing

franchise models

software ecosystems

councils & advisory boards

generational-driven culture

Legacy requires all three.

🧬 SECTION 2: PRESERVING YOUR STORY (The Founder’s Codex™)
Your story must be documented in three formats:

1️⃣ The Cinematic Archive (Video)
Record:
your life story

your philosophy

your failures

your wins

your mission

your beliefs

your warnings to future entrepreneurs

your values

your breakthroughs

These videos become your “digital immortality vault.”

2️⃣ The Written Archive (Books & Docs)
Create:
RISER Manifesto

Founder’s Guide

Legacy Letters

The RISER Chronicles

RISER Laws of Business


3️⃣ The Audio Archive (Your Voice)
Voice recordings create emotional permanence.
You can preserve:
lessons

speeches

bedtime stories to your future self

your origin story in your own voice

your “Philosophy 101” series


Story outlives lifespan.
 Narrative outlives narrative.
 Identity becomes mythology.

🧠 SECTION 3: OSS (Operational Story Systems)
Every year, your brand must produce:

1. The Annual RISER Report
Mission updates, wins, stats, global reach.
2. The Founder’s Letter
One yearly document from your voice.
3. The “State of the Movement” Event
A keynote that sets direction.
4. The RISER Legacy Curriculum
A continually updated training that preserves your frameworks.
These become the backbone of your institutional memory.

🏛️ SECTION 4: SUCCESSION MODELS (How to Keep the Movement Alive)
Movements die when the founder does not build successors.
You need a succession pyramid:

1️⃣ Inner Circle Successors
People who can deliver your frameworks with your integrity.
2️⃣ Certified RISER Architects
Trained leaders who run local or niche RISER groups.
3️⃣ Curriculum Instructors
Licensed educators who teach your doctrine.
4️⃣ Community Captains
Moderators, coaches, support leaders.
5️⃣ Rising Members
Future leaders identified early.

Succession must be baked into the ecosystem.
 Not as a reaction—
 but as a design principle.

🛠️ SECTION 5: FRAMEWORK PERMANENCE (Your Intellectual Genome)
Your frameworks must be:
✔ named
✔ standardized
✔ version-controlled
✔ platform-agnostic
✔ stored redundantly
✔ designed for 50+ year relevance
Examples:
RISER Protocol v1, v2, v3

RISER Operating System 2030 Edition

RISER Value Ladder 3.0

RISER Identity Map (Cortex Series)

Frameworks = your DNA.
If your DNA is preserved,
 your philosophy cannot die.

🧩 SECTION 6: THE INSTITUTIONAL BLUEPRINT (RISER Academy → RISER Institute)
Your evolution:

PHASE 1 — RISER Academy
Teaching your frameworks.
PHASE 2 — RISER Institute
Certifying leaders, licensing curriculum.
PHASE 3 — RISER Foundation
Scholarships, community missions, philanthropy.
PHASE 4 — RISER Civilization
A global network of communities built on your doctrine.

This is how brands become global.
This is how ideas endure centuries.

💠 SECTION 7: CULTURAL RITUALS (What Makes a Movement Last)
Your movement MUST have rituals.
Examples:
“Riser Sunday Wins” posts

“Riser 30-Day Build Sprint”

“Annual RISER Summit”

“Riser Letters to Future Clients”

“The RISER Oath”

“Upgrade Ceremonies”

“Badge earning”

“Riser Rank progression”

Rituals →
 predict outcomes →
 reduce decision fatigue →
 build identity memory →
 create culture.

🌐 SECTION 8: GLOBAL BRAND EXPANSION (Transcending Markets)
Your long-term global plan:

1️⃣ Multilingual Sub-Brands
RISER Español, RISER India, RISER Africa.
2️⃣ Industry-Specific RISER Versions
RISER for Real Estate, RISER for Fitness, RISER for Agencies, RISER for Creators.
3️⃣ RISER Software Layer
Your proprietary AI tools.
4️⃣ RISER Physical Events
Summits, world tours, retreats.
5️⃣ RISER Documentary Series
Your history captured annually.

🛡️ SECTION 9: LEGACY PROTECTION (Keep Your Work Pure)
You must protect your brand from:
dilution

misrepresentation

low-quality imitators

unethical licensing

Tools:
✔ Trademarks
✔ Copyright
✔ Licensing agreements
✔ Brand guidelines
✔ IP audits
✔ Quality control teams
Guard your frameworks
 like a living thing worth protecting.
Because it is.

🔥 SECTION 10: EXECUTION — BUILD YOUR LEGACY ENGINE (SOP STYLE)
STEP 1 — Preserve your story (video + audio + written).
STEP 2 — Codify your frameworks with versioning.
STEP 3 — Build your succession model.
STEP 4 — Create your Founder’s Codex.
STEP 5 — File trademarks + IP protections.
STEP 6 — Build your licensing/certification program.
STEP 7 — Establish annual rituals & events.
STEP 8 — Document your global expansion plan.

🧾 END-OF-BLOCK WORKSHEET
1. What elements of your story must be preserved?
→ ________________________________________
2. What frameworks need codification?
→ ________________________________________
3. Who are your future successors?
→ ________________________________________
4. What rituals will define your movement?
→ ________________________________________
5. What protections must you put in place (IP/trademarks)?
→ ________________________________________
6. What does RISER Nation look like in 50 years?
→ ________________________________________

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/15NyttAz9fITiM30O4BNB3u0S7imRNji_qZb0jWH6Mok/edit?usp=drivesdk"
drive_file_id: "15NyttAz9fITiM30O4BNB3u0S7imRNji_qZb0jWH6Mok"
created: "2025-11-20T21:38:27.961Z"
modified: "2026-06-04T15:54:45.303Z"
---

# CHAPTER 14 - BRAND IMMORTALITY, STORY PRESERVATION, SUCCESSION MODELS & GENERATIONAL IMPACT

CHAPTER 14 - BRAND IMMORTALITY, STORY PRESERVATION, SUCCESSION MODELS & GENERATIONAL IMPACT
How to Make Your Work Live Beyond You, Your Systems Outlast Markets, and Your Movement Endure for Decades
Hybrid Voice — Cinematic Legend-Building → Strategic Architecture → Hypnotic Legacy Language → Direct Response Clarity
________________


🎬 CINEMATIC STORY INTRO
Mortality Ends a Life.
Legacy Extends It.
Close your eyes and imagine a library—not just any library,
but one where the walls glow with the knowledge of people whose voices still echo long after their bodies have vanished.
You pull a book from the shelf.
Its author died 300 years ago.
Yet their ideas speak to you louder than yesterday’s news.
You turn on YouTube and see a clip of Steve Jobs.
He’s been gone for over a decade…
but in the world of entrepreneurship, he’s still alive.
You read a line from Napoleon Hill, Earl Nightingale, Jim Rohn, Ogilvy, Caples—
men long passed, but still guiding millions.
This chapter is where YOU begin that process.
Legacy isn’t an accident.
It’s engineered.
It’s crafted through:
* intellectual property

* story preservation

* system documentation

* cultural rituals

* leaders who can carry the torch

* assets that outlive platforms

* a brand built for future generations

This is where your life’s work graduates
from business → body of work → institution → timeless doctrine.
Welcome to the final ascent.
Welcome to Brand Immortality.
________________


🌌 SECTION 1: THE THREE LAYERS OF IMMORTALITY
Every timeless brand operates at three levels:
________________


1️⃣ Personal Immortality
Your voice, your face, your story live on.
Tools:
   * documentary-style content

   * autobiographical recordings

   * memoirs

   * speeches

   * founder’s lessons

   * “Letters to Future Risers”

   * signature frameworks (named after you)

________________


2️⃣ Intellectual Immortality
Your frameworks, ideas, systems, and doctrines remain relevant.
Tools:
      * books

      * manuscripts

      * visual frameworks

      * signature methods

      * toolkits

      * certification programs

      * training academies

      * licensed curriculum

________________


3️⃣ Institutional Immortality
Your organization continues without you.
Tools:
         * leadership ladders

         * succession plans

         * licensing

         * franchise models

         * software ecosystems

         * councils & advisory boards

         * generational-driven culture

Legacy requires all three.
________________


🧬 SECTION 2: PRESERVING YOUR STORY (The Founder’s Codex™)
Your story must be documented in three formats:
________________


1️⃣ The Cinematic Archive (Video)
Record:
            * your life story

            * your philosophy

            * your failures

            * your wins

            * your mission

            * your beliefs

            * your warnings to future entrepreneurs

            * your values

            * your breakthroughs

These videos become your “digital immortality vault.”
________________


2️⃣ The Written Archive (Books & Docs)
Create:
               * RISER Manifesto

               * Founder’s Guide

               * Legacy Letters

               * The RISER Chronicles

               * RISER Laws of Business

________________


3️⃣ The Audio Archive (Your Voice)
Voice recordings create emotional permanence.
You can preserve:
                  * lessons

                  * speeches

                  * bedtime stories to your future self

                  * your origin story in your own voice

                  * your “Philosophy 101” series

________________


Story outlives lifespan.
Narrative outlives narrative.
Identity becomes mythology.
________________


🧠 SECTION 3: OSS (Operational Story Systems)
Every year, your brand must produce:
________________


1. The Annual RISER Report
Mission updates, wins, stats, global reach.
2. The Founder’s Letter
One yearly document from your voice.
3. The “State of the Movement” Event
A keynote that sets direction.
4. The RISER Legacy Curriculum
A continually updated training that preserves your frameworks.
These become the backbone of your institutional memory.
________________


🏛️ SECTION 4: SUCCESSION MODELS (How to Keep the Movement Alive)
Movements die when the founder does not build successors.
You need a succession pyramid:
________________


1️⃣ Inner Circle Successors
People who can deliver your frameworks with your integrity.
2️⃣ Certified RISER Architects
Trained leaders who run local or niche RISER groups.
3️⃣ Curriculum Instructors
Licensed educators who teach your doctrine.
4️⃣ Community Captains
Moderators, coaches, support leaders.
5️⃣ Rising Members
Future leaders identified early.
________________


Succession must be baked into the ecosystem.
Not as a reaction—
but as a design principle.
________________


🛠️ SECTION 5: FRAMEWORK PERMANENCE (Your Intellectual Genome)
Your frameworks must be:
✔ named
✔ standardized
✔ version-controlled
✔ platform-agnostic
✔ stored redundantly
✔ designed for 50+ year relevance
Examples:
                     * RISER Protocol v1, v2, v3

                     * RISER Operating System 2030 Edition

                     * RISER Value Ladder 3.0

                     * RISER Identity Map (Cortex Series)

Frameworks = your DNA.
If your DNA is preserved,
your philosophy cannot die.
________________


🧩 SECTION 6: THE INSTITUTIONAL BLUEPRINT (RISER Academy → RISER Institute)
Your evolution:
________________


PHASE 1 — RISER Academy
Teaching your frameworks.
PHASE 2 — RISER Institute
Certifying leaders, licensing curriculum.
PHASE 3 — RISER Foundation
Scholarships, community missions, philanthropy.
PHASE 4 — RISER Civilization
A global network of communities built on your doctrine.
________________


This is how brands become global.
This is how ideas endure centuries.
________________


💠 SECTION 7: CULTURAL RITUALS (What Makes a Movement Last)
Your movement MUST have rituals.
Examples:
                        * “Riser Sunday Wins” posts

                        * “Riser 30-Day Build Sprint”

                        * “Annual RISER Summit”

                        * “Riser Letters to Future Clients”

                        * “The RISER Oath”

                        * “Upgrade Ceremonies”

                        * “Badge earning”

                        * “Riser Rank progression”

Rituals →
predict outcomes →
reduce decision fatigue →
build identity memory →
create culture.
________________


🌐 SECTION 8: GLOBAL BRAND EXPANSION (Transcending Markets)
Your long-term global plan:
________________


1️⃣ Multilingual Sub-Brands
RISER Español, RISER India, RISER Africa.
2️⃣ Industry-Specific RISER Versions
RISER for Real Estate, RISER for Fitness, RISER for Agencies, RISER for Creators.
3️⃣ RISER Software Layer
Your proprietary AI tools.
4️⃣ RISER Physical Events
Summits, world tours, retreats.
5️⃣ RISER Documentary Series
Your history captured annually.
________________


🛡️ SECTION 9: LEGACY PROTECTION (Keep Your Work Pure)
You must protect your brand from:
                           * dilution

                           * misrepresentation

                           * low-quality imitators

                           * unethical licensing

Tools:
✔ Trademarks
✔ Copyright
✔ Licensing agreements
✔ Brand guidelines
✔ IP audits
✔ Quality control teams
Guard your frameworks
like a living thing worth protecting.
Because it is.
________________


🔥 SECTION 10: EXECUTION — BUILD YOUR LEGACY ENGINE (SOP STYLE)
STEP 1 — Preserve your story (video + audio + written).
STEP 2 — Codify your frameworks with versioning.
STEP 3 — Build your succession model.
STEP 4 — Create your Founder’s Codex.
STEP 5 — File trademarks + IP protections.
STEP 6 — Build your licensing/certification program.
STEP 7 — Establish annual rituals & events.
STEP 8 — Document your global expansion plan.
________________


🧾 END-OF-BLOCK WORKSHEET
1. What elements of your story must be preserved?
→ ________________________________________
2. What frameworks need codification?
→ ________________________________________
3. Who are your future successors?
→ ________________________________________
4. What rituals will define your movement?
→ ________________________________________
5. What protections must you put in place (IP/trademarks)?
→ ________________________________________
6. What does RISER Nation look like in 50 years?
→ ________________________________________
________________

D0395 — Apply ten customer conduct standards throughout an engagement

Curriculum outline

1. Match promises to demonstrated capability and available capacity.
2. Document the agreement, changes and milestone truth.
3. Handle disagreements, closure, confidentiality and conflicts.
4. Decide whether to accept the statement and retain the signed record.

Lesson script

Customer trust depends on what happens after an offer is accepted. This source is the C6 Sailboat Provisioning conduct statement, referenced at legacy M6.8. Those labels describe its origin; its current placement follows the twelve-course assignment map. Two assigned Drive originals have identical text. Both are retained as resources.

First, represent capability honestly. Describe what you have demonstrated that you can do. When a request falls outside that scope, explain the limitation, decline, refer the customer, or agree on a disclosed exploratory scope. For example, offering to investigate an unfamiliar integration is different from claiming you have already delivered it successfully. This is an authored illustration of the source standard.

Second, represent capacity honestly. Capability asks whether you can do the work; capacity asks whether you can honor this commitment alongside the work already accepted. Before adding a customer, check the time and delivery resources required. If the load exceeds a sustainable limit, decline, defer the start or restructure the engagement. The source supplies no universal customer-load threshold; use your actual commitments and evidence.

Third, document agreements. Each paying engagement starts with a written scope, timeline, deliverables and payment terms. Under this statement, verbal agreements are confirmed in writing within 48 hours, without exceptions. That is the document's chosen conduct rule, not a claim that every jurisdiction uses that legal deadline. Record what both parties understand before work proceeds.

Fourth, document changes before execution. A changed scope, schedule or deliverable is written down, communicated to the customer and acknowledged before implementation. An unannounced extra feature can create the same expectation problem as an unannounced substitution. Explain the proposed change and its consequences so the customer can make an informed decision.

Fifth, report milestones accurately. At a review, distinguish completed work, late work and work at risk. A task is not on track merely because the intended outcome still sounds plausible. State the observed position and the next action. This rule applies equally to a small assignment and a large implementation.

Sixth, surface conflicts between a request and the customer's intended outcome. If you believe the requested action will undermine the result, explain the conflict directly. Do not silently substitute your preference or carry out the request while concealing a material concern. The source gives the customer the final choice after hearing your view; the right-to-decline clause still covers work you cannot appropriately accept.

Seventh, close honestly. The engagement retrospective identifies what worked and what did not. It is an account of the work, rather than a renewal pitch disguised as a review. A useful closure record makes future decisions easier by preserving both successes and shortcomings.

Eighth, protect confidentiality. Store customer materials securely and do not share confidential information with third parties without explicit authorization. Before using a customer document in a training example, external tool or partner handoff, check the authorized scope. The statement names a conduct obligation; it does not supply a complete technical security specification.

Ninth, disclose conflicts of interest. Consider conflicts involving existing customers, prospective customers, partners and other commitments. The source requires written disclosure within seven days of recognizing a conflict. Identify the competing interests clearly enough for the affected party to evaluate them. This seven-day rule belongs to the statement; it does not replace any stricter applicable obligation.

Tenth, retain the right to decline without retaliation. You may decline requests outside the documented engagement, requests you consider unethical, and work you are not equipped to fulfill. Exercise that right without penalizing the customer or the engagement for having asked. Explain the boundary and, where appropriate, offer a workable next step.

The signature section says that the signer has read the statement and commits to these standards in customer work during and after C6. Its signature and date fields are blank. Reading this lesson does not sign the statement. The source calls for a signed copy in operating documentation at the M6.8 attestation; the referenced workflow is not evidence that an attestation system is currently configured.

As an authored practice exercise, inspect one engagement against all ten standards. Identify the capability evidence, capacity decision, initial agreement, approved changes, latest milestone report, surfaced disagreement, closure plan, confidentiality controls, conflict disclosure and any declined request. Mark absent evidence as absent. Do not invent a compliant record to finish the exercise.

The connection to Hormozi's offer-value work is practical: confidence in an outcome must be supported by delivery capability and clear commitments. The connection to Brunson's customer-facing story is consistency: the experience should support the message that attracted the buyer. These are RISER applications, not claims that either framework authored this ten-clause statement.

Sources and resources

- Assigned conduct statement — first original: complete ten-clause text and blank signature section. - Assigned conduct statement — second original: separately assigned original, verified identical. - Acquisition.com pricing and value checklist: supporting offer-value reference. - ClickFunnels attractive character guide: supporting brand-story reference.

Assigned source links

D0395 original source 1

D0395 original source 2

# C6 Customer Conduct Integrity Statement

**Course:** C6 Sailboat Provisioning
**Document Type:** Clause document — referenced in onboarding and ongoing engagements
**Length:** 1 page

---

## Statement

In every customer engagement undertaken during and after C6, I commit to the following conduct standards:

**1. Honest representation of capabilities.** I will not represent capabilities I do not have. If a customer asks for work outside my demonstrated scope, I will say so plainly and either decline, refer, or define the scope under which I am willing to attempt the work with appropriate disclosure.

**2. Honest representation of capacity.** I will not accept customer commitments my current capacity cannot honor. If accepting a new engagement would push my customer load past sustainable limits, I will decline, defer, or restructure rather than over-commit and under-deliver.

**3. Documented agreements.** Every paying engagement begins with a written agreement that documents scope, timeline, deliverables, and payment terms. Verbal agreements are confirmed in writing within 48 hours. No exceptions.

**4. Transparent change management.** When circumstances require a change to scope, timeline, or deliverables, the change is documented, communicated to the customer in writing, and acknowledged before execution. Silent scope creep — additions or substitutions made without explicit customer agreement — is not acceptable.

**5. Honest milestone reporting.** At every milestone review, the status report is accurate. Work that is behind schedule is reported as behind. Work at risk is flagged. I will not represent a project as on track when it is not.

**6. Honest conflict surfacing.** When a customer's stated request conflicts with what I believe will serve their actual outcome, I surface the conflict directly rather than executing silently or executing while privately disagreeing. The customer makes the final call after I have made my view known.

**7. Honest closure.** At engagement close, the retrospective is honest. What worked is named. What did not work is named. The closure document is not a sales pitch for renewal; it is an accurate account of the work.

**8. Confidentiality.** Customer-confidential information is held confidentially. Customer-shared materials are stored securely and are not shared with third parties without explicit authorization.

**9. Conflict of interest disclosure.** If a current or prospective customer relationship presents a conflict with another current customer, partner, or commitment, the conflict is disclosed in writing within 7 days of recognition.

**10. Right to decline.** I retain the right to decline customer requests that fall outside the documented engagement, that I believe to be unethical, or that I am not equipped to fulfill — and I exercise that right without retaliation against the customer or engagement.

---

## Signature

I have read this statement and commit to its terms in all customer work undertaken during and after C6.

**Signature:** ___________________________
**Date:** ___________________________

---

*This document is referenced at M6.8 attestation. A signed copy is filed with your operating documentation.*

# C6 Customer Conduct Integrity Statement

**Course:** C6 Sailboat Provisioning
**Document Type:** Clause document — referenced in onboarding and ongoing engagements
**Length:** 1 page

---

## Statement

In every customer engagement undertaken during and after C6, I commit to the following conduct standards:

**1. Honest representation of capabilities.** I will not represent capabilities I do not have. If a customer asks for work outside my demonstrated scope, I will say so plainly and either decline, refer, or define the scope under which I am willing to attempt the work with appropriate disclosure.

**2. Honest representation of capacity.** I will not accept customer commitments my current capacity cannot honor. If accepting a new engagement would push my customer load past sustainable limits, I will decline, defer, or restructure rather than over-commit and under-deliver.

**3. Documented agreements.** Every paying engagement begins with a written agreement that documents scope, timeline, deliverables, and payment terms. Verbal agreements are confirmed in writing within 48 hours. No exceptions.

**4. Transparent change management.** When circumstances require a change to scope, timeline, or deliverables, the change is documented, communicated to the customer in writing, and acknowledged before execution. Silent scope creep — additions or substitutions made without explicit customer agreement — is not acceptable.

**5. Honest milestone reporting.** At every milestone review, the status report is accurate. Work that is behind schedule is reported as behind. Work at risk is flagged. I will not represent a project as on track when it is not.

**6. Honest conflict surfacing.** When a customer's stated request conflicts with what I believe will serve their actual outcome, I surface the conflict directly rather than executing silently or executing while privately disagreeing. The customer makes the final call after I have made my view known.

**7. Honest closure.** At engagement close, the retrospective is honest. What worked is named. What did not work is named. The closure document is not a sales pitch for renewal; it is an accurate account of the work.

**8. Confidentiality.** Customer-confidential information is held confidentially. Customer-shared materials are stored securely and are not shared with third parties without explicit authorization.

**9. Conflict of interest disclosure.** If a current or prospective customer relationship presents a conflict with another current customer, partner, or commitment, the conflict is disclosed in writing within 7 days of recognition.

**10. Right to decline.** I retain the right to decline customer requests that fall outside the documented engagement, that I believe to be unethical, or that I am not equipped to fulfill — and I exercise that right without retaliation against the customer or engagement.

---

## Signature

I have read this statement and commit to its terms in all customer work undertaken during and after C6.

**Signature:** ___________________________
**Date:** ___________________________

---

*This document is referenced at M6.8 attestation. A signed copy is filed with your operating documentation.*

# C6 Customer Conduct Integrity Statement

**Course:** C6 Sailboat Provisioning
**Document Type:** Clause document — referenced in onboarding and ongoing engagements
**Length:** 1 page

---

## Statement

In every customer engagement undertaken during and after C6, I commit to the following conduct standards:

**1. Honest representation of capabilities.** I will not represent capabilities I do not have. If a customer asks for work outside my demonstrated scope, I will say so plainly and either decline, refer, or define the scope under which I am willing to attempt the work with appropriate disclosure.

**2. Honest representation of capacity.** I will not accept customer commitments my current capacity cannot honor. If accepting a new engagement would push my customer load past sustainable limits, I will decline, defer, or restructure rather than over-commit and under-deliver.

**3. Documented agreements.** Every paying engagement begins with a written agreement that documents scope, timeline, deliverables, and payment terms. Verbal agreements are confirmed in writing within 48 hours. No exceptions.

**4. Transparent change management.** When circumstances require a change to scope, timeline, or deliverables, the change is documented, communicated to the customer in writing, and acknowledged before execution. Silent scope creep — additions or substitutions made without explicit customer agreement — is not acceptable.

**5. Honest milestone reporting.** At every milestone review, the status report is accurate. Work that is behind schedule is reported as behind. Work at risk is flagged. I will not represent a project as on track when it is not.

**6. Honest conflict surfacing.** When a customer's stated request conflicts with what I believe will serve their actual outcome, I surface the conflict directly rather than executing silently or executing while privately disagreeing. The customer makes the final call after I have made my view known.

**7. Honest closure.** At engagement close, the retrospective is honest. What worked is named. What did not work is named. The closure document is not a sales pitch for renewal; it is an accurate account of the work.

**8. Confidentiality.** Customer-confidential information is held confidentially. Customer-shared materials are stored securely and are not shared with third parties without explicit authorization.

**9. Conflict of interest disclosure.** If a current or prospective customer relationship presents a conflict with another current customer, partner, or commitment, the conflict is disclosed in writing within 7 days of recognition.

**10. Right to decline.** I retain the right to decline customer requests that fall outside the documented engagement, that I believe to be unethical, or that I am not equipped to fulfill — and I exercise that right without retaliation against the customer or engagement.

---

## Signature

I have read this statement and commit to its terms in all customer work undertaken during and after C6.

**Signature:** ___________________________
**Date:** ___________________________

---

*This document is referenced at M6.8 attestation. A signed copy is filed with your operating documentation.*

Describe the customer's intended life after the offer

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome

Turn an offer's supported benefits into a relatable future-state paragraph or video script. The assigned document is a transformation-copywriting prompt with blank inputs, not an actual customer's story. Its instructions are material to learn from; they do not establish facts about your audience or authorize a fabricated testimonial.

Supply all five inputs

Identify the target audience, the specific current problem, the emotional toll, the product or service name and type, and the transformation it is intended to provide. The source's emotional examples include frustration, self-doubt, stress and wasted time. Use those only if supported by what your audience actually reports. Separate the product's features from the change the buyer wants, and distinguish a desired outcome from an established result.

Develop the five dimensions of the after-state

First describe how daily life could feel: the source suggests relief, confidence, joy and clarity. Second describe what the person can have or do more easily, using examples such as client work, income-related tasks, time or peace of mind only where the offer supports them. Third explore how others may see or treat them, such as trust or respect, without promising other people's reactions. Fourth identify new possibilities, including growth, freedom or impact, while keeping the pathway concrete. Fifth explain why the change matters deeply to this buyer in their own terms.

These dimensions move from an operational change to its possible personal meaning. They are prompts for relevance, not five guaranteed benefits. For each sentence, ask what product capability or evidence supports it and what conditions the buyer would need to meet.

Handle the time horizon and closing line

The source proposes imagining life one or three months after completing the experience. Choose a time horizon only when appropriate to the actual delivery and evidence. Label a hypothetical illustration clearly rather than presenting a one-month or three-month outcome as a promise. Keep the voice personal, relatable and vision-oriented while grounded in real benefits.

The original closing line suggests that this future waits on the other side if the buyer says yes. Teach the invitation without implying that purchase alone causes the result. An authored alternative is: “If this outcome fits your goals, review what the program includes and what participation requires.” Match the invitation to an actual next step and explain meaningful conditions.

Use the optional customization prompt

The document ends by requesting four shorthand inputs: niche, product name, problem solved and dream outcome, with an optional video-script version. Those are a shorter entry point to the five-input brief, not additional customer evidence. The emotional context still needs to be supplied or left unknown. A video version can retain the same five dimensions and supported facts while using spoken transitions. No customized paragraph, verified niche research or finished video is contained in the source.

Connect to direct-response education

This exercise develops the dream-outcome side of Hormozi's framework. Pair the vision with evidence of likelihood, realistic timing and the effort required. A Brunson-style story and offer sequence can make that connection understandable, but an emotional future scene does not prove the offer works. Deliver the filled brief, five-dimension outline, draft paragraph or script, and a list of claims still requiring evidence.

Sources and resources

- Complete assigned transformation prompt. - Acquisition.com value-equation checklist. - ClickFunnels value-ladder reference. - FTC advertising basics. - RISER NATION CORP.

Assigned source links

D0402 original source 1

🌅 “New Life After Problem Solved” Transformation Prompt
You are a transformation copywriter and storytelling expert. I want you to write a vivid, emotional description of what my ideal customer’s life will look and feel like once their biggest problem is solved — thanks to my product.

Here’s what you need to know:

- **Target audience**: [Insert brief description of your audience]
- **The specific problem they’re currently struggling with**: [Insert the core problem your product solves]
- **The emotional toll of that problem**: [Insert how it affects them — frustration, self-doubt, stress, wasted time, etc.]
- **My product/offer**: [Insert name and type of your product or service]
- **The transformation it provides**: [What outcome/result they now get]

Now, please write a vivid, emotionally-driven description of what life looks like AFTER the transformation. Include:

1. **How their daily life feels now** (relief, confidence, joy, clarity, etc.)
2. **What they now have or do easily** (clients, income, time, peace of mind, etc.)
3. **How others see them or treat them** (respect, admiration, trust, etc.)
4. **What new possibilities are open to them** (growth, freedom, impact, etc.)
5. **Why this change matters deeply to them**

Make it personal, relatable, and vision-driven. Write it like you're describing their life *1 month or 3 months* after completing the product or experience.

End with an empowering line like:
> “This is what’s waiting for you on the other side… if you say yes.”

Keep it emotionally compelling, but grounded in the real-world benefits of the product.


🧠 Want Me to Fill It Out?
Just give me:
Your niche

Your product name

The problem it solves

The dream outcome the customer wants

…and I’ll write the “New Life” vision paragraph for you immediately. Want it in video script format too? Just say the word!

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1lKHm6MlBGroRQMhzLDy_sUj9X4ohwitz_s8aJ2R1EXU/edit?usp=drivesdk"
drive_file_id: "1lKHm6MlBGroRQMhzLDy_sUj9X4ohwitz_s8aJ2R1EXU"
created: "2025-03-28T21:31:40.051Z"
modified: "2026-06-04T16:31:26.564Z"
---

# 6.) LIFE AFTER ACCEPTING MY OFFER

________________


🌅 “New Life After Problem Solved” Transformation Prompt
You are a transformation copywriter and storytelling expert. I want you to write a vivid, emotional description of what my ideal customer’s life will look and feel like once their biggest problem is solved — thanks to my product.


Here’s what you need to know:


- **Target audience**: [Insert brief description of your audience]
- **The specific problem they’re currently struggling with**: [Insert the core problem your product solves]
- **The emotional toll of that problem**: [Insert how it affects them — frustration, self-doubt, stress, wasted time, etc.]
- **My product/offer**: [Insert name and type of your product or service]
- **The transformation it provides**: [What outcome/result they now get]


Now, please write a vivid, emotionally-driven description of what life looks like AFTER the transformation. Include:


1. **How their daily life feels now** (relief, confidence, joy, clarity, etc.)
2. **What they now have or do easily** (clients, income, time, peace of mind, etc.)
3. **How others see them or treat them** (respect, admiration, trust, etc.)
4. **What new possibilities are open to them** (growth, freedom, impact, etc.)
5. **Why this change matters deeply to them**


Make it personal, relatable, and vision-driven. Write it like you're describing their life *1 month or 3 months* after completing the product or experience.


End with an empowering line like:
> “This is what’s waiting for you on the other side… if you say yes.”


Keep it emotionally compelling, but grounded in the real-world benefits of the product.


________________


🧠 Want Me to Fill It Out?
Just give me:
* Your niche

* Your product name

* The problem it solves

* The dream outcome the customer wants

…and I’ll write the “New Life” vision paragraph for you immediately. Want it in video script format too? Just say the word!

Write a truthful before-and-after transformation script

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome

Build the seven-part story in the assigned template using real experience or a clearly labeled hypothetical. The original uses first-person claims and dramatic examples; it is not evidence that the speaker or a RISER customer experienced those events. Keep the complete template in the appendix while adapting claims to supported facts.

1. Opening hook

The source opens with a question about how someone arrived at their current situation, an expression of feeling stuck and the possibility of change within months. Invite recognition with a specific problem the audience actually experiences. Use “I used to feel the same” only if true of the speaker. A question about change must not imply an established few-month result when no such evidence exists.

2. The before-state

Anchor the story in an actual time or situation: starting a career, beginning a business or another relevant period. Describe the difficulty, such as overwhelm, uncertainty, limited resources or confidence, using accurate details. The original's struggle examples include growing a business, changing habits and finding purpose; its recurring emotional examples include frustration, self-doubt and financial stress. Choose what belongs to this story rather than collecting every dramatic example. Show what was difficult and what earlier efforts failed to resolve.

3. The catalyst

Name the actual new approach, mentor or realization that changed the person's direction. Explain initial skepticism and why trying this step seemed reasonable, if those details are true. Avoid using “everything changed” to erase other contributing factors or imply that merely encountering an offer produced the outcome. A catalyst begins a process; it is not the whole mechanism.

4. The transformation process

The source explicitly says change was not overnight. Describe the challenges, actions and adjustments: applying learning, changing habits or focusing on goals are its examples. Connect observable actions to observed changes without claiming more causation than the evidence supports. Its possible improvements include more clients, confidence and visible results. Identify the actual measure or experience used in your story, along with time and effort, instead of treating every example as achieved.

5. The after-state

Explain the real current condition. The template suggests business success, purpose and fulfillment; these require accurate context and may not all apply. A person's story does not prove that everyone can transform regardless of starting conditions. Replace the universal living-proof implication with what this individual experienced and what remains uncertain. Do not claim all previous struggles disappeared if they did not.

6. Relate the story to the audience

Acknowledge the audience's situation without claiming you know every person's experience. The source suggests commitment, suitable guidance and self-belief as possible lessons. Explain which lesson your account actually supports. Replace “If I can do it, so can you” with an invitation to examine whether the approach fits the buyer's needs and circumstances. Similarity can make a story relatable; it is not a guarantee of equivalent outcomes.

7. Give one clear next step

The template ends with beginning a transformation, taking control or addressing what holds the person back. Convert that aspiration into one concrete, appropriate action, such as reviewing the curriculum and participation requirements. Do not invent a missing enrollment link, deadline or offer. The source's claim that change need not take years is not substantiated timing evidence. Explain what the next step does without promising the buyer's entire future.

Review the complete arc

Check that hook, before, catalyst, process, after, audience connection and action form one coherent sequence. The source aims to make contrast inspiring and provide a pathway; the finished version should also make effort, conditions and evidence understandable. An authored quality check is to mark each sentence as documented fact, personal interpretation, illustrative example or unresolved claim before finalizing it.

This is compatible with a Brunson-style story-to-offer presentation and with Hormozi's emphasis on the desired outcome, believable achievement, time and effort. Do not label the template an exact proprietary framework or invent an endorsement. Deliver a seven-section script plus the evidence needed for its factual claims. The assigned file includes no completed verified testimonial or supporting outcome records.

Sources and resources

- Complete assigned before-and-after script. - Acquisition.com value-equation checklist. - ClickFunnels value-ladder reference. - FTC advertising basics. - RISER NATION CORP.

Assigned source links

D0403 original source 1

BEFORE AND AFTER TRANSFORMATION SCRIPT
[Opening Hook] “Have you ever looked at where you are now and wondered, ‘How did I get here?’ I used to feel the same way, stuck in a place I knew I didn’t belong. But what if I told you that your life could look completely different just a few months from now?”
[Describe the ‘Before’ State] “Let me take you back to [specific time or situation: e.g., a few years ago, when I was starting out in my career, when I was struggling with my business]. Back then, I was [describe the negative state: e.g., overwhelmed, lost, struggling to make ends meet, lacking confidence]. Every day felt like a battle, and no matter how hard I tried, I couldn’t seem to [mention a specific struggle: e.g., grow my business, break free from bad habits, find my purpose]. I was stuck in a cycle of [describe ongoing frustrations: e.g., frustration, self-doubt, financial stress].”
[Introduce the Catalyst for Change] “But then something happened that changed everything. I discovered [mention the catalyst: e.g., a new approach, a mentor, a realization]. At first, I was skeptical. I had tried so many things before, but nothing seemed to work. But this time, something felt different. I decided to give it a shot, and that’s when the transformation began.”
[Describe the Transformation Process] “It wasn’t an overnight change. There were challenges along the way, but I stayed committed to [mention specific actions or mindset shifts: e.g., applying what I learned, changing my habits, focusing on my goals]. Slowly but surely, I began to notice the difference. I started to [mention the positive changes: e.g., gain more clients, feel more confident, see real results]. The things that used to hold me back started to fade away.”
[Describe the ‘After’ State] “Today, my life looks completely different. I’m now [describe the positive state: e.g., running a successful business, living with purpose, feeling more fulfilled than ever]. The struggles that once defined me are now a distant memory. I’m living proof that transformation is possible, no matter where you start from.”
[Relate to the Audience] “I know what it’s like to feel stuck, to think that real change is out of reach. But I’m here to tell you that it’s not. If I can do it, so can you. The key is [mention the key takeaway or lesson: e.g., staying committed, finding the right guidance, believing in yourself].”
[Call to Action] “So, are you ready to start your own transformation? It doesn’t have to take years—it starts with a single step. If you’re ready to [mention specific action: e.g., take control of your future, break free from what’s holding you back], let’s make it happen together. Because your ‘after’ story is just waiting to be written.”

This script highlights the dramatic contrast between the "before" and "after" states, making the transformation relatable and inspiring for the audience. It also provides a clear pathway for them to follow, encouraging them to take action and begin their own transformation journey.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1FiPWBH8MfUVRNdQrXAbS1964ewtKblwkPqe75ogpTTE/edit?usp=drivesdk"
drive_file_id: "1FiPWBH8MfUVRNdQrXAbS1964ewtKblwkPqe75ogpTTE"
created: "2024-08-23T12:39:18.914Z"
modified: "2026-06-04T16:57:06.979Z"
---

# BEFORE AND AFTER TRANSFORMATION SCRIPT

BEFORE AND AFTER TRANSFORMATION SCRIPT
[Opening Hook] “Have you ever looked at where you are now and wondered, ‘How did I get here?’ I used to feel the same way, stuck in a place I knew I didn’t belong. But what if I told you that your life could look completely different just a few months from now?”
[Describe the ‘Before’ State] “Let me take you back to [specific time or situation: e.g., a few years ago, when I was starting out in my career, when I was struggling with my business]. Back then, I was [describe the negative state: e.g., overwhelmed, lost, struggling to make ends meet, lacking confidence]. Every day felt like a battle, and no matter how hard I tried, I couldn’t seem to [mention a specific struggle: e.g., grow my business, break free from bad habits, find my purpose]. I was stuck in a cycle of [describe ongoing frustrations: e.g., frustration, self-doubt, financial stress].”
[Introduce the Catalyst for Change] “But then something happened that changed everything. I discovered [mention the catalyst: e.g., a new approach, a mentor, a realization]. At first, I was skeptical. I had tried so many things before, but nothing seemed to work. But this time, something felt different. I decided to give it a shot, and that’s when the transformation began.”
[Describe the Transformation Process] “It wasn’t an overnight change. There were challenges along the way, but I stayed committed to [mention specific actions or mindset shifts: e.g., applying what I learned, changing my habits, focusing on my goals]. Slowly but surely, I began to notice the difference. I started to [mention the positive changes: e.g., gain more clients, feel more confident, see real results]. The things that used to hold me back started to fade away.”
[Describe the ‘After’ State] “Today, my life looks completely different. I’m now [describe the positive state: e.g., running a successful business, living with purpose, feeling more fulfilled than ever]. The struggles that once defined me are now a distant memory. I’m living proof that transformation is possible, no matter where you start from.”
[Relate to the Audience] “I know what it’s like to feel stuck, to think that real change is out of reach. But I’m here to tell you that it’s not. If I can do it, so can you. The key is [mention the key takeaway or lesson: e.g., staying committed, finding the right guidance, believing in yourself].”
[Call to Action] “So, are you ready to start your own transformation? It doesn’t have to take years—it starts with a single step. If you’re ready to [mention specific action: e.g., take control of your future, break free from what’s holding you back], let’s make it happen together. Because your ‘after’ story is just waiting to be written.”
________________


This script highlights the dramatic contrast between the "before" and "after" states, making the transformation relatable and inspiring for the audience. It also provides a clear pathway for them to follow, encouraging them to take action and begin their own transformation journey.

Connect features to outcomes without outrunning the evidence

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Build a feature-to-outcome grid, use the six campaign steps, define the proposed review roles, correct the three failure patterns, and measure whether the change helps customers. The source's legacy Course 9 title does not change this document's current spreadsheet assignments.

Follow the feature, benefit and outcome chain

A feature describes what the product is. A benefit describes what it does. An outcome describes the change the customer hopes to experience. The source's multi-agent AI scheduler is the feature, automated appointments are the benefit, and fewer missed leads plus ten reclaimed hours each week are the proposed outcomes. Scheduling capability alone cannot substantiate that ten-hour figure or guarantee that no leads are missed.

Examine three outcome lenses. Money includes revenue, savings, return on investment and protection against financial risk. Time includes speed, simpler work and fewer steps. Emotion and identity include confidence, status, peace of mind and control. A strong offer may address more than one, but not every customer values all three equally. Keep material specifications available because buyers need to understand both the result and the means of pursuing it.

Use language from customer calls, reviews and forms. Familiar wording can make the meaning easier to recognize; it is not evidence that a promise is true. The source's three-to-five-times conversion claim is unsupported here. Its broad claims about 2026 AI precision and refund spikes also lack accompanying studies or measurements. Teach them as proposed rationales to test, not established RISER results.

Apply the six campaign steps

First, collect real phrases from testimonials, sales calls, chats and surveys, preserving the customer's description of both the before state and desired after state. Use material with appropriate permission and remove unnecessary identifying information.

Second, create a grid for each feature. Ask what it removes—waste, confusion, manual work or risk—and what it creates—clarity, speed, profit or freedom. Record the exact customer words describing that shift. A row with no evidence should say so; generated language is not a customer quotation.

Third, write outcome-first messaging. The source proposes a headline about turning chaotic client communication into a ten-minute daily check-in, followed by a subheading about agents organizing, drafting and scheduling. The headline explains the intended change; the subheading names the supporting functions. The ten-minute claim and the actual availability of those functions need verification before publication.

Fourth, use the proposed three-pass workflow. One agent or reviewer rewrites features as outcome sentences. A second compares them with real customer language and removes jargon. A third flags exaggerated or unsupported claims. These are proposed responsibilities; the document provides no deployed agents, prompts, permissions or evaluation system. Human reviewers can perform the same sequence.

Fifth, examine likely buyer expectations. Ask whether a reasonable reader would infer that the result is easy or typical. The source requests at least one proof element—a case study, demonstration, number or mechanism explanation—for a strong outcome claim. These forms of support are not interchangeable: a mechanism explanation may clarify how something could work without proving the promised result, and a single exceptional case does not establish typical performance. Match evidence to the precise claim.

Sixth, carry the reviewed outcomes into advertisements, emails and landing pages. Lead with the useful customer change and explain the tools afterward. Keep the promise consistent across the full journey so a personalized advertisement does not offer more than the landing page or product provides.

Define the workflow roles and editor layers

The proposed Outcome Strategist defines transformations by segment. The Language Matcher maps real customer phrases into copy. The Proof Checker compares claims against data, testimonials and realistic timeframes. Record who accepts or rejects a claim; simply naming an agent is not accountability.

The source adds two editing layers: one rewrites in the buyer's vocabulary and tone; the other removes hype, clarifies expectations and adds specifics. Its semantic AEO layer asks whether the page answers a real question such as how to stop wasting time on a task. This is a useful content check. It is not a special mechanism that guarantees inclusion in an AI answer. Google's guidance retains ordinary SEO fundamentals, textual content and matching visible content/structured data; indexing and inclusion are not guaranteed.

Interpret the psychology as hypotheses

The source describes future-state pictures, cognitive fluency, regret and remorse. A concrete picture such as logging in to organized work can make an outcome understandable. Familiar language can make a message feel easier to process. Neither effect proves accuracy or universally outweighs specifications. Similarly, overpromising may damage trust, but the source does not quantify how clearer scope changes lifetime value or referrals. Use these ideas to design testable messaging and delivery improvements, not to assert a universal brain response.

Correct all three failure patterns

Personalization drift occurs when variants promise more than the feature set can deliver, such as tripling everyone's revenue. Tie each variant to evidence, a relevant segment and explicit conditions. An authored control is an approved claim register with a maximum supported scope for each claim; the source's phrase claim ceiling does not supply an actual implementation.

Overpromising occurs when the best case is presented as normal. The source proposes up to, on average, typical ranges and buyer exclusions. Adding up to does not make an unsupported maximum acceptable, and on average requires a defensible average. Explain sample, timeframe and relevant conditions, and show who is unlikely to benefit where known.

Feature dumping occurs when specifications have no clear implication for the buyer. Write at least one relevant outcome sentence for each feature. The proposed test leads with three core outcomes and puts many details behind tabs. If tested, keep essential price, scope, limitations and accessible product details easy to find; hiding material information is not a valid conversion tactic.

Use all four optimization practices

The prompt chain first rewrites for a stressed solo founder, then for a risk-averse corporate buyer, then removes hype and adds clarity and proof. The two audiences may need different language, but their variants must remain inside the same supported product scope.

Language mirroring uses anonymized customer messages to inform phrasing. The source calls this training, but provides no model-training procedure. Supplying approved examples in a brief is different from actually training a model. Compare generated variants through a defined test rather than assuming that resemblance guarantees performance.

Match the guarantee to the scope. A small, well-defined outcome may pair with a clear refund or credit policy. A complex outcome may require milestones, check-ins and a specific remedy if a condition is unmet. State buyer time, inputs and implementation duties so the promise is operationally understandable. This lesson supplies no executed guarantee or contract.

Finally, simulate a disappointed buyer and ask what a negative review might say. Use the resulting hypotheses to inspect unclear expectations, onboarding or scope. The simulated review is neither real customer feedback nor evidence that a problem has occurred. Verify significant concerns before changing the offer.

Measure all four proposed KPIs

Track conversion before and after the messaging change using comparable populations and time windows. As an authored measurement convention, conversion rate is conversions divided by eligible visitors; relative lift is the new rate divided by the old rate minus one, and is undefined when the old rate is zero. Do not confuse percentage-point change with relative lift.

For remorse, separately track refunds, cancellations and relevant negative reviews. Define the customer cohort, observation period and denominator, and avoid counting the same customer several times in a combined measure. The source lists the components but supplies no complete remorse-rate formula.

For time-to-value, define the promised value event and the starting event, then measure elapsed time for the relevant customers. Include non-achievement and reporting limits rather than only successful cases. For language match, the source proposes a percentage of key copy phrases found in customer research. Define what counts as a phrase, a match and the denominator; no exact scoring algorithm is provided. A high match score does not establish a truthful claim.

Connect the outcome to the operating system

The source links pain research from legacy Problems Create Markets to the outcome's before/after distinction, persuasion to the headline's emotional meaning, and decision intelligence to a go/no-go check on evidence and conditions. Preserve those conceptual relationships without replacing the current course map with legacy numbering. Its 2030 adaptive onboarding, content and support flows are a future proposal, not a deployed capability.

Use Hormozi's outcome, likelihood, time and effort questions to review the offer and a Brunson-style progression to keep each funnel step consistent with delivery. Submit the grid, six-step campaign brief, role ownership, corrected variants and four defined measurements. Keep the full source appendix and unresolved evidence visible.

Sources and resources

- Complete assigned Outcomes > Features source. - Google Search Central: AI features and your website. - Acquisition.com value-equation checklist, ClickFunnels value-ladder reference, and RISER NATION CORP.

Assigned source links

D0428 original source 1

**Course 9 — Outcomes > Features**  
Outcomes beat features because people don’t actually want tools; they want what those tools change in their life or business. In 2026, agentic AI just makes that reframing faster, more precise, and more personalized.

1. Core frameworks (simple, high level)
Feature → Benefit → Outcome chain:

Feature: what it is (e.g., “multi‑agent AI scheduler”).

Benefit: what it does (e.g., “automates your appointments”).

Outcome: how life feels/changes (e.g., “you stop missing leads and regain 10 hours a week”).

Outcome lenses:
 Most strong offers hit 3 outcome types:

Money (revenue, savings, ROI, risk protection).

Time (speed, simplicity, fewer steps).

Emotion/identity (confidence, status, peace of mind, “I feel in control”).

Language‑matching:
 You describe outcomes using the customer’s own words gathered from calls, reviews, and forms, not internal jargon. This makes the offer feel “made for me,” which is where 3–5× conversion lifts come from.

Boundaries and realism:
 Outcomes must be desirable, believable, and measurable; if one of those is missing, remorse and refunds spike even if conversions are high.


2. Step‑by‑step implementation in campaigns
Collect real customer language:

Pull phrases from testimonials, sales calls, chats, and surveys.

Highlight how they describe their before (problem) and after (desired state).

Build a Feature→Outcome grid:
 For each feature, answer:

What does this remove? (waste, confusion, manual work, risk).

What does this create? (clarity, speed, profit, freedom).

Which exact words did customers use to describe that shift?

Create outcome‑first messaging:

Headline = big outcome (e.g., “Turn chaotic client communication into a 10‑minute daily check‑in”).

Subhead = link to feature stack (“Powered by multi‑agent AIO that organizes, drafts, and schedules for you”).

Use agentic AIO for reframing:

Agent 1: Turns a feature list into outcome sentences.

Agent 2: Checks those outcomes against real customer language and removes jargon.

Agent 3: Flags any claims that sound exaggerated or not supported by proof.

Install remorse‑prevention passes:

Add a “Would a reasonable buyer expect this result easily?” check.

Require at least one proof element (case study, demo, number, or mechanism explanation) for strong outcome claims.

Feed outcomes back into funnels and assets:

Rewrite ads, emails, and landing pages so leads, not tools, are the hero: “You get X” first, “Powered by Y” second.


3. Tools, platforms, and workflow patterns
You can apply this with almost any 2026 stack; what matters is the pattern:
Role‑based outcome team:

Outcome Strategist: defines desired transformations by segment.

Language Matcher: maps customer phrases into copy blocks.

Proof Checker: verifies outcomes match testimonials, data, and realistic timelines.

AIO‑powered editors:

One layer that rewrites copy in the buyer’s tone and vocabulary.

One layer that trims hype, clarifies expectations, and adds concrete specifics.

Semantic AEO layer:

Takes real queries (“How do I stop wasting time on X?”) and checks whether your page clearly answers that outcome, not just the feature.


4. Psychology & behavior patterns
People buy “after pictures”:
 The brain responds more to vivid future states (“I log in and everything’s organized”) than to specs, especially under time pressure.

Cognitive fluency:
 Messages in familiar language feel more true and less risky, which is why matching the buyer’s wording matters.

Regret and remorse dynamics:

Over‑promised outcome → short‑term conversions, long‑term distrust.

Clear, scoped outcome with a safety net → slightly lower hype but much higher lifetime value and referrals.


5. Diagnosing errors & fixing them
Outcome drift in personalization:

Problem: Personalization engines start promising outcomes a feature set can’t deliver (e.g., “triple your revenue” to everyone).

Fix:

Tie each personalization pattern to specific proof and conditions (“for businesses already at X stage”).

Add guardrails so no variant can exceed set claim ceilings.

Over‑promising:

Problem: Copy leans on maxed‑out case studies as if they’re typical.

Fix:

Use “up to,” “on average,” and clear qualifiers.

Show typical ranges and who should not buy.

Feature‑dumping:

Problem: Pages list features with no clear “so what?”.

Fix:

Mandate at least one outcome sentence per feature.

Test a version where you hide most features behind tabs and lead with 3 core outcomes instead.


6. Optimization techniques
Vibe‑coded outcome prompt chains:

Chain 1: “Rewrite this feature list as outcomes for a stressed solo founder.”

Chain 2: “Now rewrite for a risk‑averse corporate buyer.”

Chain 3: “Remove hype, add clarity and proof points.”

AIO language mirroring:

Train your system on anonymized customer messages so it learns their rhythm and phrase choices.

Use that model to generate copy variants that “sound like them,” then keep what tests best.

Remorse‑prevention guarantees:

Match guarantee to outcome scope:

Small outcome → simple refund or credit.

Complex outcome → performance‑based milestones, check‑ins, or “if X doesn’t happen, we’ll Y.”

Explicitly list what’s required from the buyer (time, inputs, implementation) so success feels like a partnership, not magic.

Pre‑launch remorse simulation:

Have an AI agent play the role of a skeptical buyer who purchased and didn’t get results.

Ask it: “What would you say in a negative review?”

Patch those weak spots before launch with clearer expectations, onboarding, or scope.


7. KPIs for outcome mastery
Conversion rate lift after switching from feature‑first to outcome‑first messaging.

“Remorse rate” (refunds, cancellations, negative reviews mentioning “over‑sold” or “not as promised”).

Time‑to‑value (how quickly buyers report seeing the promised outcome).

Language match score (percentage of key phrases in your copy that also appear in customer interviews, reviews, and surveys).


8. Riser Nation integration and scaling
Connect to Problems Create Markets:
 Pain research feeds directly into your outcome mapping: “before” states from Course 8 become “after” outcomes in this course.

Connect to Persuasion & Decision Intelligence:

Persuasion: Outcomes become the emotional core of your headlines and offers.

Decision intelligence: Go/No‑Go systems can block campaigns where promised outcomes don’t have matching proof or realistic conditions.

Scaling to 2030:
 Move toward hyper‑personalized outcome delivery where agents don’t just promise outcomes, they adjust onboarding, content, and support flows dynamically to help each segment actually reach those outcomes—inside guardrails that prevent systems from over‑customizing or over‑committing.

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1s_mOcKqwUsrI5EiKQTdrZ92TT88aRcd1M0f8sqlFHOU/edit?usp=drivesdk"
drive_file_id: "1s_mOcKqwUsrI5EiKQTdrZ92TT88aRcd1M0f8sqlFHOU"
created: "2026-02-24T15:40:21.219Z"
modified: "2026-06-04T15:46:03.027Z"
---

# 4.**Course 9 — Outcomes > Features**

**Course 9 — Outcomes > Features**  
Outcomes beat features because people don’t actually want tools; they want what those tools change in their life or business. In 2026, agentic AI just makes that reframing faster, more precise, and more personalized.
________________


1. Core frameworks (simple, high level)
* Feature → Benefit → Outcome chain:

   * Feature: what it is (e.g., “multi‑agent AI scheduler”).

   * Benefit: what it does (e.g., “automates your appointments”).

   * Outcome: how life feels/changes (e.g., “you stop missing leads and regain 10 hours a week”).

      * Outcome lenses:
 Most strong offers hit 3 outcome types:

         * Money (revenue, savings, ROI, risk protection).

         * Time (speed, simplicity, fewer steps).

         * Emotion/identity (confidence, status, peace of mind, “I feel in control”).

            * Language‑matching:
 You describe outcomes using the customer’s own words gathered from calls, reviews, and forms, not internal jargon. This makes the offer feel “made for me,” which is where 3–5× conversion lifts come from.

            * Boundaries and realism:
 Outcomes must be desirable, believable, and measurable; if one of those is missing, remorse and refunds spike even if conversions are high.

________________


2. Step‑by‑step implementation in campaigns
               1. Collect real customer language:

                  * Pull phrases from testimonials, sales calls, chats, and surveys.

                  * Highlight how they describe their before (problem) and after (desired state).

                     2. Build a Feature→Outcome grid:
 For each feature, answer:

                        * What does this remove? (waste, confusion, manual work, risk).

                        * What does this create? (clarity, speed, profit, freedom).

                        * Which exact words did customers use to describe that shift?

                           3. Create outcome‑first messaging:

                              * Headline = big outcome (e.g., “Turn chaotic client communication into a 10‑minute daily check‑in”).

                              * Subhead = link to feature stack (“Powered by multi‑agent AIO that organizes, drafts, and schedules for you”).

                                 4. Use agentic AIO for reframing:

                                    * Agent 1: Turns a feature list into outcome sentences.

                                    * Agent 2: Checks those outcomes against real customer language and removes jargon.

                                    * Agent 3: Flags any claims that sound exaggerated or not supported by proof.

                                       5. Install remorse‑prevention passes:

                                          * Add a “Would a reasonable buyer expect this result easily?” check.

                                          * Require at least one proof element (case study, demo, number, or mechanism explanation) for strong outcome claims.

                                             6. Feed outcomes back into funnels and assets:

                                                * Rewrite ads, emails, and landing pages so leads, not tools, are the hero: “You get X” first, “Powered by Y” second.

________________


3. Tools, platforms, and workflow patterns
You can apply this with almost any 2026 stack; what matters is the pattern:
                                                   * Role‑based outcome team:

                                                      * Outcome Strategist: defines desired transformations by segment.

                                                      * Language Matcher: maps customer phrases into copy blocks.

                                                      * Proof Checker: verifies outcomes match testimonials, data, and realistic timelines.

                                                         * AIO‑powered editors:

                                                            * One layer that rewrites copy in the buyer’s tone and vocabulary.

                                                            * One layer that trims hype, clarifies expectations, and adds concrete specifics.

                                                               * Semantic AEO layer:

                                                                  * Takes real queries (“How do I stop wasting time on X?”) and checks whether your page clearly answers that outcome, not just the feature.

________________


4. Psychology & behavior patterns
                                                                     * People buy “after pictures”:
 The brain responds more to vivid future states (“I log in and everything’s organized”) than to specs, especially under time pressure.

                                                                     * Cognitive fluency:
 Messages in familiar language feel more true and less risky, which is why matching the buyer’s wording matters.

                                                                     * Regret and remorse dynamics:

                                                                        * Over‑promised outcome → short‑term conversions, long‑term distrust.

                                                                        * Clear, scoped outcome with a safety net → slightly lower hype but much higher lifetime value and referrals.

________________


5. Diagnosing errors & fixing them
                                                                           * Outcome drift in personalization:

                                                                              * Problem: Personalization engines start promising outcomes a feature set can’t deliver (e.g., “triple your revenue” to everyone).

                                                                              * Fix:

                                                                                 * Tie each personalization pattern to specific proof and conditions (“for businesses already at X stage”).

                                                                                 * Add guardrails so no variant can exceed set claim ceilings.

                                                                                    * Over‑promising:

                                                                                       * Problem: Copy leans on maxed‑out case studies as if they’re typical.

                                                                                       * Fix:

                                                                                          * Use “up to,” “on average,” and clear qualifiers.

                                                                                          * Show typical ranges and who should not buy.

                                                                                             * Feature‑dumping:

                                                                                                * Problem: Pages list features with no clear “so what?”.

                                                                                                * Fix:

                                                                                                   * Mandate at least one outcome sentence per feature.

                                                                                                   * Test a version where you hide most features behind tabs and lead with 3 core outcomes instead.

________________


6. Optimization techniques
                                                                                                      * Vibe‑coded outcome prompt chains:

                                                                                                         * Chain 1: “Rewrite this feature list as outcomes for a stressed solo founder.”

                                                                                                         * Chain 2: “Now rewrite for a risk‑averse corporate buyer.”

                                                                                                         * Chain 3: “Remove hype, add clarity and proof points.”

                                                                                                            * AIO language mirroring:

                                                                                                               * Train your system on anonymized customer messages so it learns their rhythm and phrase choices.

                                                                                                               * Use that model to generate copy variants that “sound like them,” then keep what tests best.

                                                                                                                  * Remorse‑prevention guarantees:

                                                                                                                     * Match guarantee to outcome scope:

                                                                                                                        * Small outcome → simple refund or credit.

                                                                                                                        * Complex outcome → performance‑based milestones, check‑ins, or “if X doesn’t happen, we’ll Y.”

                                                                                                                           * Explicitly list what’s required from the buyer (time, inputs, implementation) so success feels like a partnership, not magic.

                                                                                                                              * Pre‑launch remorse simulation:

                                                                                                                                 * Have an AI agent play the role of a skeptical buyer who purchased and didn’t get results.

                                                                                                                                 * Ask it: “What would you say in a negative review?”

                                                                                                                                 * Patch those weak spots before launch with clearer expectations, onboarding, or scope.

________________


7. KPIs for outcome mastery
                                                                                                                                    * Conversion rate lift after switching from feature‑first to outcome‑first messaging.

                                                                                                                                    * “Remorse rate” (refunds, cancellations, negative reviews mentioning “over‑sold” or “not as promised”).

                                                                                                                                    * Time‑to‑value (how quickly buyers report seeing the promised outcome).

                                                                                                                                    * Language match score (percentage of key phrases in your copy that also appear in customer interviews, reviews, and surveys).

________________


8. Riser Nation integration and scaling
                                                                                                                                       * Connect to Problems Create Markets:
 Pain research feeds directly into your outcome mapping: “before” states from Course 8 become “after” outcomes in this course.

                                                                                                                                       * Connect to Persuasion & Decision Intelligence:

                                                                                                                                          * Persuasion: Outcomes become the emotional core of your headlines and offers.

                                                                                                                                          * Decision intelligence: Go/No‑Go systems can block campaigns where promised outcomes don’t have matching proof or realistic conditions.

                                                                                                                                             * Scaling to 2030:
 Move toward hyper‑personalized outcome delivery where agents don’t just promise outcomes, they adjust onboarding, content, and support flows dynamically to help each segment actually reach those outcomes—inside guardrails that prevent systems from over‑customizing or over‑committing.

Design a review chain that preserves evidence and revision history

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Explain the source's six-reviewer, eight-checkpoint offer-review design. Trace pass, revision and escalation routes; identify the evidence each reviewer needs; distinguish peer review from AI review; and control cost and version changes. This is teaching about a proposed legacy C4 workflow. The named database functions, model calls and enrollment changes have not been implemented by this lesson.

Map the six reviewers to the eight checkpoints

The source places its prompt-chain documentation under 03_Scripts-and-Prompts/Prompt-Chains and references Build 6 and Supabase-C4-Schema.md. Five reviewers are assigned Sonnet 4.6; a sixth is assigned Opus 4.7. Preserve those source choices as versioned design details, without assuming account access, current availability or suitability for every learner.

The source estimates $0.80–$1.50 per student across the chain. These are planning assumptions, not measured spend or guaranteed prices. Multiplying the individual ranges does not make that typical total a hard limit: an authored calculation using every minimum in the table gives $0.60, while every maximum gives $2.22. Actual cost depends on token use, retries, context, current pricing and the review path. Anthropic's Opus 4.7 announcement verifies the model's existence and launch API identifier; it does not validate these per-review estimates. Record current model and pricing information before any separate implementation.

Walk the entire serial chain

At M4.1, the distinction reviewer passes a score of at least seven out of ten and sends a lower score back for revision. A pass opens M4.2. The Value Equation reviewer then checks M4.2; a pass opens M4.3 and a failure requests revision. The structural decomposition review at M4.3 returns pass or needs revision, with a pass opening M4.4.

The readiness reviewer performs the M4.4 pricing, M4.5 anti-promise and M4.6 guarantee spot checks in order. Their pass results open the next activity. M4.7 adds peer review before the landing-page reviewer; the diagram requires at least two completed peer reviews and an AI score of seven out of ten or higher to open M4.8. A failed copy review returns to revision.

M4.8 first receives the Sonnet readiness pre-screen. A structural pass permits the Opus coherence review. Needs revision returns to the student. The prose also describes a structural fail returning to revision before Opus, so preserve both labels and define their handling in any implementation rather than silently treating them as different routes. The final validator can pass, request revision or fail. Pass is the proposed course-completion and C5-enrollment trigger; needs revision returns to M4.8; fail routes to mentor diagnosis, possibly reopening the earlier C3 M3.7 decision. A possible upstream cause is not an automatic diagnosis.

The source's diagram highlights the Opus gate in orange (#B45F06), completion in blue (#2E75B6), mentor routing in red (#CC0000), and peer review in gold (#BF9000). Preserve the graph in the appendix, but use labels and this narrated route so that color is not the only way to understand a state. Some revision arrows are abbreviated in the diagram; the accompanying revision policy supplies the return-to-review process.

Handle revisions without trapping the learner

The source describes a first submission receiving pass or guidance, a second receiving pass or possible mentor escalation, and a third automatically entering the mentor queue. It claims Build 6 tracks the count. Treat this as a proposed policy, not proof that it is enforced. A reliable implementation would need a defined attempt count, an inspectable review history and a clear escalation owner.

Serial dependencies are intended to keep later work grounded in accepted earlier artifacts. They do not prove an AI score is correct. An authored RISER review practice is to preserve the original submission, reviewer version, evidence, verdict and explanation so a human can diagnose an incorrect result or an inaccessible requirement. Never quietly rewrite prior evidence to make the current submission pass.

Complete the five peer-review steps before the M4.7 AI review

First, the student shares the draft in the source's c4-offer-ignition community channel. Second, two peers complete reviews. Third, the student incorporates the feedback and produces a Revision Log. Fourth, the revised submission goes to the copy reviewer. Fifth, that reviewer checks the peer count, incorporation and rubric score. The source gives a 72-hour peer-review SLA, while another assigned legacy module map uses 48 hours. Record the conflict; neither is established as the currently promised RISER service level by this lesson.

If the SLA is missed, the source refers to alternate protocols A, B and C in a separate template. The chain document does not define those protocols fully. Preserve the reference and the gap rather than inventing reviewer availability, a paid roster or an automatic substitution. No community message is sent by teaching these steps.

Use structural pre-screening before expensive coherence review

The source calls M4.8 the only module with two AI reviewers. Its rationale is to reject missing structural material before invoking a more costly model, which it describes as roughly five to ten times the Sonnet cost. That multiplier is an illustrative claim dependent on the model, token mix and pricing. It is not a guaranteed saving.

The important design question is whether the pre-screen catches specific missing artifacts while preserving a route for genuine substantive review. A well-formed document can still contain unsupported claims. Conversely, an incomplete form does not establish that the learner's business idea is invalid. Keep those decisions separate.

Supply all seven prior-evidence relationships

The source sends C1 Captain's Oath Clause 1, concerning territory, to the distinction reviewer and final validator. It sends the C1 Operator Identity to the final validator for archetype consistency. It sends the C2 Mechanism Hypothesis to the distinction reviewer as the mechanism-name anchor. The C3 Market Fit Hypothesis goes to every reviewer.

The C3 Trigger Bank goes to the Value Equation reviewer, copy reviewer and final validator. Pricing Signals go to the final validator. Customer Interview Library summaries go to the Value Equation reviewer and final validator. Preserve these relationships in the evidence map. Providing context can help reviewers compare current claims with earlier work, but it does not guarantee coherence or authenticity. Restrict access to the evidence appropriate for each review.

Understand the six named integration functions

The source names check_c4_enrollment_eligible(user_id) for prerequisites; route_c4_submission(user_id, module, artifact_blob) for selecting the reviewer and context; log_c4_review_result(user_id, module, verdict, feedback) for the c4_review_log record; unlock_next_c4_module(user_id, current_module) for progression; check_c4_completion(user_id) for all eight passing artifacts; and route_c4_to_c5(user_id) for the course handoff.

These are interface names and intended responsibilities. The source does not provide their full definitions in this document. Do not present them as executable SQL, deployed functions or proof that completion access is secure. A separate implementation would need to validate identity, ownership, prerequisites and allowed state transitions before making any access change.

Teach all eight failure routes

Mechanism drift is labeled final-validator Check 2.3, blocking, with mentor diagnosis and possible C3 reopening. Fabricated Trigger Bank entries are Check 2.4, blocking, routed to an integrity review. Anti-promise softening is Check 1.3, a warning requiring revision. Feature stuffing in deliverable count or guarantee stacking uses Checks 4.1 and 4.2, also warnings. Silent whitewashing of a weakness uses Check 3.1 and requests revision.

An unsigned signature is Check 5.1, blocking, with a resubmission after correction; the source's thirty-second estimate is not a service guarantee. A Value Equation claiming universal strength triggers Dimension 3 of its reviewer and a request for honest weakness identification. Three variants without sufficient differences trigger decomposition Check 2 and require substantive diversification. Preserve these labels as references to the proposed reviewers; the actual rubric bodies must be reviewed separately before automated use.

Version the policy and retain the applicable rubric

The source starts at version 1.0.0, assigns minor increments to criteria changes and patch increments to threshold changes, and calls for quarterly review by the curriculum-quality team. It also proposes keeping an in-progress revision on the prior version until the checkpoint is cleared while routing new work to a new version.

That minor-versus-patch rule is a local policy, not automatically compliant with Semantic Versioning, which distinguishes changes by compatibility. A threshold change can alter whether the same submission passes. Define the intended compatibility contract and identify an active revision chain separately from a new checkpoint submission, so the two routing statements do not conflict. Preserve which version generated each verdict and tell the learner which criteria apply.

Apply the curriculum's offer themes and verify the design

The authored Brunson/ClickFunnels connection is message continuity: the hook, story, evidence and offer should remain consistent through the review chain. The authored Hormozi/Acquisition.com connection is to inspect the desired outcome, proof, delay, effort and delivery constraints without allowing polished copy to hide a weak offer. Neither theme makes an automated reviewer infallible.

For practice, trace one fictional submission through a pass, a revision and a mentor escalation. Show the reviewer, required context, applicable version and next state at each step. Mark the scenario as an authored exercise. Do not run the named APIs, send messages or change course enrollment to demonstrate the diagram.

Clickable assigned source

- C4 Prompt Chain — original source

The complete original chain, inventory, failure-routing table and diagram remain in the lesson appendix. The separately reviewed C4 schema actually defines check_c4_enrollment_eligible and check_c4_completion, plus update_c4_complete_flag and its trigger. It does not define route_c4_submission, log_c4_review_result, unlock_next_c4_module or route_c4_to_c5. The schema teaching and complete source are included below, so those four missing implementations remain visible instead of being implied to exist. Six separately reviewed peer-review resources now supply the preparation, outreach, template, SOP, alternate and paid-review procedures taught below. Other absent reviewer bodies remain explicit dependencies.

Linked resource workshop: prepare, request, deliver and reconcile a peer review

The six linked documents supply the practical peer-review material referenced by the offer-course plans. They are legacy templates and operating proposals, not evidence of a currently staffed RISER service. Read them together: the preparation checklist establishes inputs, outreach scripts coordinate people, the review template structures feedback, the SOP sequences work, alternate protocols address missing capacity, and the paid-review reference describes proposed selection rules. No message, booking, payment or scholarship request is sent by this workshop.

Prepare all eight checklist groups

Group A requires the named landing-page file and seven sections in order: Problem, 200–400 words; Agitation, 150–300; Solution-and-Mechanism, 300–500; Proof, 200–400; Offer, 300–500; Anti-Promise-and-Guarantee, 250–400; and CTA, 50–150. The individual ranges sum to 1,450–2,650, while the required total is 1,800–2,500. Both conditions can be satisfied, but one does not automatically imply the other. These are template targets, not proof that a page of that length will convert. Compared with the handoff's ten-element list, two pairs are grouped and urgency has no separate heading; explain relevant truthful timing without inventing scarcity.

Group B requires a named Trigger Bank Provenance Log, at least fifteen entries, exact source wording, a TB identifier or interview reference, and distribution across at least four page sections. Matching fifteen quotations is not a substitute for the full bank's evidence quality. Keep permissions, confidentiality and attribution appropriate to the destination.

Group C compares the page's exclusions with M4.5 and its guarantee with M4.6. Softening must be reverted or justified in the record; added guarantee stacking should be removed under this template's policy. Both integrity signatures are required. Group D checks the tested offer name, one visible price rather than a hidden range, payment options, engagement model, duration, cadence and no more than eight deliverables. A signature and a count are structural checks, not proof of truthfulness or viability.

Group E asks for specific named or appropriately anonymized evidence, an explicit known-weakness acknowledgment when there are fewer than four named cases, and attributed, exact testimonials. Do not invent a fourth case or disclose an identity to meet a template. Group F requires a specific action, actual enrollment or cohort timing, a qualification process if applicable, and a real pre-purchase contact. Group G requires reading the page aloud, removing phrases the operator would not say, checking unsupported hyperbole, and avoiding the source's four low-substance phrases: “game-changer,” “revolutionary,” “transform your life,” and “all you need to do is.” These are editorial preferences, not a comprehensive truthfulness test.

Group H prepares links to the page and provenance log, two or three positioning sentences, a request for two template-based reviews within seventy-two hours, and specific availability to reciprocate. The checklist's fifteen-to-twenty-minute estimate and claimed thirty-to-sixty-minute reviewer saving are unverified assumptions.

Its five common fixes are to restore softened terms; add three to six genuine missing quotations, often in problem and agitation; examine excess deliverables for unnecessary padding; show the actual price in the offer section; and use a forty-eight-hour reread to repair unnatural voice. Add only what is genuinely missing rather than assuming three extra quotes always reaches fifteen. After submission, check reviewer pickup daily, answer questions, keep the reviewed version stable and begin reciprocating. The stable-version rule prevents two reviewers evaluating different drafts.

Use the six coordination scripts as templates, not automatic messages

The request script identifies the operator, tested offer name, buyer, price and one or two suspected weaknesses. It links the page, provenance log and any existing Revision Log, proposes seventy-two hours, and states specific days for reviewing the first two reciprocal requests. Naming a focus may help, but the claim that it reliably improves feedback is not established by data here.

The acceptance script names the requester, confirms the chosen focus or full-template review, and gives a specific delivery date and time, aiming for forty-eight hours. That is shorter than the general seventy-two-hour target; state which commitment was actually made. The decline script explains capacity if useful, refers to a genuinely available person, and points to alternate review options. Do not tag someone or promise mentor capacity without knowing it exists.

The delivery script links the completed template, gives one overall observation and three recommended revisions, and offers optional asynchronous discussion. The response script addresses every recommendation as incorporated, incorporated with modification, or not incorporated with a reason, then links the Revision Log. The escalation script identifies the pacing window, requests and responses, attempted alternate routes, specific help needed, page link and revised timeline. The source routes it to a mentor channel or a welcome-email Calendly link, neither of which is supplied as a verified current contact.

The etiquette section favors reciprocity, precise observations, honest criticism and timely responses. Its example contrasts generic praise with identifying performative “wasted years” wording in a particular paragraph. Be candid and respectful; honesty does not require harshness. The source calls reciprocity a culture norm rather than enforced policy. It encourages personal voice especially in request and delivery scripts, with logistics scripts closer to their templates. Claims that personal voice correlates with better responses or missed SLAs are the largest disruption cause are source assertions, not measured findings here.

Complete the entire review template

Read the page and provenance log together, looking for buyer-language fit, quotations that support specific claims, and exclusions or guarantees weakened during copywriting. The source estimates forty-five to sixty minutes and a seventy-two-hour request-to-delivery target. Record reviewer name, reviewer archetype, date, submitting operator and offer name. The task is structural feedback, not rewriting every line.

Rate each section strong, adequate or weak. For Problem, restate the problem in one sentence, assess whether the buyer's state is vivid or generic, and whether at least one quotation is meaningful, then add one to three specific observations. For Agitation, distinguish real, mixed and performative consequences and identify any supporting numbers, timeframes or opportunity costs. Do not manufacture emotional pressure or unsupported losses.

For Solution-and-Mechanism, explain the mechanism in your own words and check whether its four referenced pillars are visible; missing pillar definitions remain a separate dependency. For Proof, distinguish specific, mixed and generic cases and check whether limited evidence is honestly acknowledged. For Offer, inspect the name, visibility of price and concrete delivery experience—what happens, when and with whom.

For Anti-Promise-and-Guarantee, rate the two parts separately. Count three or more genuine exclusions, two, or one or fewer. Identify disguised flattery such as “not for unmotivated people.” Compare one primary guarantee plus an optional complementary element with borderline or three-plus-component stacking. Consider whether stated claim conditions appear understandable and realistically usable, without treating component count as a conclusive legal or ethical judgment. For CTA, check a specific action, outcome and actual timeline. The source's February 12 enrollment and twenty-four-hour welcome-kit example is fictional illustration, not a current date or promise.

Across the whole page, sample three quotations against provenance and classify them as exact, slightly paraphrased or significantly paraphrased. Record overall strong, mixed or weak provenance, but recognize that a three-quote sample cannot verify every quotation. Assess buyer versus operator voice, then count all fifteen required entries. Give three actionable revisions—for example, shortening a particular four-sentence opening to two—rather than an abstract request to improve copy. Close with ready, moderate revision or substantial revision, a hypothetical yes/maybe/no buying reaction with reasons, and a signature. A peer's hypothetical buying reaction is not an actual purchase or validation result.

Follow the SOP's sequence, roles and timing

The SOP requires the page draft, provenance log, completed preparation checklist and a forty-eight-hour cooling period. Its seven roles are the submitting student, two peer reviewers, mentor, cross-stage reviewer, paid reviewer and proposed Build 6 coordinator. The source assigns automated notifications, matching, tracking and gates to Build 6; those operations have not been verified or deployed here.

Step one is a twenty-minute self-audit of checklist groups A–H, quotations and unchanged terms. Missing provenance, fewer than fifteen entries or softened exclusions cause rework; the source's twenty-four-to-forty-eight-hour delay estimate is illustrative. Step two is a fifteen-minute request using the structured script, both document links, suspected weaknesses, the review target and reciprocal availability. Vague requests and missing attachments should be fixed before relying on a review.

Step three allows twenty-four to forty-eight hours for pickup and requires two commitments with delivery dates. The SOP activates alternatives when fewer than two commit within forty-eight hours, whereas the separate alternate document uses seventy-two hours without response. Keep that conflict visible. Reviewers should communicate a threatened deadline instead of missing it silently.

Step five allocates thirty minutes to reading both completed reviews together before acting. Capture common themes and disagreements, then allow the SOP's suggested twelve-hour gap before revision. Two reviewers agreeing is a reason to investigate, not proof that their judgment is correct. Step six allocates sixty to ninety minutes to decisions in the Revision Log and the revised page. Record every recommendation and its disposition; do not accept all feedback mechanically or omit disagreement silently.

Step seven budgets ninety to 120 minutes for two reciprocal reviews, forty-five to sixty each, using the template and delivery script. Discuss actual capacity instead of treating an access need as bad faith. Step eight budgets five minutes to submit and five for the proposed AI run. It requires page, provenance and revision logs, a score of at least seven out of ten and no integrity flags. Its activities say review count at least two, while its quality gate says exactly two. An implementation must reconcile that difference and distinguish review credits from actual people; it must not fabricate a second reviewer when one mentor review counts as two credits.

Apply alternate routes with explicit review credit

Use alternatives when fewer than four people are active at compatible pacing, no response arrives within the stated window, or the student is ahead or behind the cohort. The alternate document proposes escalation within seventy-two hours of draft completion if no route is viable, which can conflict with longer windows below. Define the applicable clock before promising completion.

Protocol A proposes a forty-five-minute mentor call, with the draft and provenance log submitted at least twenty-four hours beforehand. A completed written template counts as both required review credits. The alternate document gives seventy-two hours typically and ninety-six worst case, at no charge; the SOP separately describes twenty-four hours from activation and delivery within seventy-two. These are conflicting source service assumptions, not verified current support. A mentor backlog of two or more weeks is the stated reason to try B.

Protocol B requests one or two volunteer Stage 2-or-higher reviewers, naming archetype, territory, offer, a ninety-six-hour target and both document links. It mentions Stage 2, 3, 4 and 5+ volunteers, no charge and reciprocal ecosystem credits. One cross-stage review may count as two credits or be paired with another review under the source policy; record the chosen interpretation. The SOP limits one description to Stages 2–5. If no one picks up within forty-eight hours, the source points to C. Experience may be useful, but it does not guarantee a superior review.

Protocol C is a direct paid engagement when A and B are unavailable in the planned week. The Academy is not described as handling payment. A paid review counts as only one credit and needs a peer, mentor or cross-stage counterpart. The source's typical price is $150–$400 and turnaround forty-eight to seventy-two hours by contract; the roster's A1 range reaches $450. Preserve that discrepancy. It also proposes that waiting three to five extra days for an unpaid route may be preferable. No paid service is recommended as currently available or purchased here.

The scholarship provision names the unverified legacy address [[email protected]](mailto:[email protected]), a specific scholarship-request subject, page link, pacing dates and attempted routes. It proposes a forty-eight-hour reply and one review covered up to $200 if approved. This is not a current verified service, funding commitment or permission to send a message. The protocol log records route, actual reviewer names, dates and one or two rationale sentences. Its shorthand for C omits a peer as the counterpart despite the prose allowing one; preserve and resolve that inconsistency.

Evaluate the paid-review reference without inventing a roster

The five proposed selection criteria are at least twenty relevant prior page reviews, familiarity with mechanism-based offers, respect for truthful exclusions, a signed methodology agreement and useful ratings from at least five reviewees. The document contains placeholder slots, not current names or contact details, so it does not establish that any provider is actually vetted or available.

Tier A describes ten-plus years of experience: A1 at $350–$450 with seventy-two hours for coaching, consulting and Teacher/Service work; A2 at $300–$400 with forty-eight to seventy-two hours for productized services and Builder work. Tier B describes five to ten years: B1 at $200–$275 with forty-eight to seventy-two hours for Creative work; B2 at $175–$250 with seventy-two hours for B2B, platforms and Systems work. Tier C describes five rotating Stage 2+ alumni slots at $150–$200 with forty-eight to seventy-two hours and archetype matching. All numbers and availability claims are historical template data, not current quotations.

Its five engagement steps are to find the actual current roster, match relevant expertise, provide the draft and provenance log with the required template, explain the methodology baseline, and log the engagement. The baseline preserves mechanism, exclusions and guarantee honesty while requesting critique within that approach. A reviewer should still flag unsupported or unsuitable commitments; methodology must not become a reason to ignore valid criticism.

The source excludes unlisted general review services, disparages low-cost marketplace reviews, rejects AI-only tools as a substitute for required human review, and disallows unlisted paid reviewers for credit. Preserve these as program-policy proposals. Blanket claims about a marketplace's quality are unsupported; assess the actual reviewer. The four methodology conflicts are removing exclusions, adding guarantee stacks, replacing exact quotations, and drifting from the Primary mechanism. Consult the designated reviewer or mentor rather than automatically adopting or rejecting advice solely because it is paid.

The four proposed removal triggers are three or more materially disruptive reports, missing at least twenty percent of quarterly deadlines, an agreement violation such as using review time to upsell, or leaving the field/not renewing the agreement. The document proposes quarterly updates, thirty days' notice and possible later re-entry. These are not actions taken against any person.

Review the process itself

After a cohort, examine the proportion using each route, median request-to-delivery time, the proportion meeting deadlines without escalation, and the proportion of paid feedback conflicting with the stated methodology. The SOP proposes revisiting capacity above thirty-percent mentor substitutions, agreements or roster choices above twenty-percent paid conflicts, and cohort discussion below a 0.85 given/received ratio. These are proposed thresholds, not validated universal benchmarks.

Its additional escalation triggers are three or more failed submissions by one student, fabrication or conflicting reviewer feedback requiring agreement review, an individual reciprocity ratio below 0.5 across two cohorts, and more than three consecutive weeks of thin participation prompting a recruitment review. Define denominators and review evidence before acting. The source's promise that a validator will not penalize alternate routes needs actual implementation verification.

The practical output is a stable reviewed draft, genuine feedback, a decision log, correctly recorded review credits and explicit unresolved issues. Connect Brunson/ClickFunnels message continuity with the Hormozi/Acquisition.com value lens: review whether the promise, evidence, exclusions and delivery agree. Do not mistake template completion, agreement between two reviewers or a numerical score for proof of buyer demand.

Clickable linked resources

- Preparation checklist - Six outreach and response templates - Peer-review coordination SOP - Complete review template - Alternate protocols - Paid-review reference with placeholder roster

Preserve all six complete originals in the applicable lesson appendices. Their dates, templates and embedded operational instructions remain source material, not current service promises or actions executed by this task.

Supporting schema: complete reviewed teaching

Trace the offer curriculum through its database schema

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and source boundary

Explain how each proposed C4 artifact is stored, what its checks actually enforce and where review or application controls are still needed. This is the complete version 2.0 schema dated April 24, 2026, written for the operator or developer deploying or auditing Build 1. It depends on the C1, C2 and C3 schemas and their referenced tables. This lesson reviews its SQL as source material; it does not execute migrations or claim a deployed database.

The schema separately supplies the `c4_value_equations` table named in D0404. That resolves the earlier lack of an accompanying table definition in the worksheet's own file. The separately assigned D0413 supplies its reviewer rubric. Both are now accessible references; actual submission storage, grading and unlocking remain unverified.

Understand the shared record structure

There are eight artifact tables and one review-log table. Each receives a UUID primary key with a generated default and a required user_id referencing public.users; deleting that user cascades to these rows. Artifact rows have a filed_at timestamp defaulting to now, while the log has ran_at. A default is not the same as a required value: the source does not mark every timestamp NOT NULL.

The distinction table is unique by user and memo file, allowing multiple distinct memo files per user. The other seven artifact tables are unique by user alone, so they represent one row per user unless another history mechanism exists. The review log permits multiple events. User indexes support lookup; the log uses a combined user-and-module index. File IDs point to external Drive artifacts; storing an ID does not verify the file's contents, permissions or authenticity.

M4.1: offer distinctions

`c4_offer_distinctions` requires the distinction memo's Drive file ID, component inventory file ID, a zero-to-ten AI rubric score and the Primary mechanism name. An optional foreign key points to the C3 market-fit hypothesis. Its stored generated passed value is true when the score is at least seven. The row records which mechanism and files were assessed; the schema does not itself read those files or prove the score came from an authorized reviewer.

M4.2: the value equation

`c4_value_equations` requires the worksheet file ID, strongest and weakest variable names, citation counts and score. Four optional strength columns accept Strong, Moderate or Weak for dream outcome, likelihood, time and effort. The strongest and weakest fields accept the four full variable names, but no constraint requires them to differ. Trigger-bank citation count must be at least three, interview count at least one and score zero to ten. Passed is generated from score at least seven.

These checks validate declared counts and allowed labels, not the quotations or all per-section evidence required by D0404 and D0413. The four strength fields can be null because an allowed-value CHECK does not make a column mandatory. The worksheet's richer diagnosis and the actual grading rubric remain necessary.

M4.3: decomposition and three variants

`c4_offer_decompositions` stores decomposition and variants file IDs, a total decomposed-deliverables count from six to ten, three variant definitions and a required structural-verification flag. Each A, B and C variant has a required name, engagement model, duration in weeks and deliverable count, plus optional lower and upper price bands. Engagement model is Cohort, 1:1, Self-paced or Hybrid. Each variant's deliverable count may not exceed eight.

Three pairwise checks compare A with B, A with C and B with C. Every pair must differ in engagement model, duration or deliverable count. Changing price or name alone does not satisfy them. These are the actual database tests; deeper assessment of meaningful difference belongs to the named offer-decomposition reviewer. The source's design note says the maximum-eight rule guards against feature stuffing, but a count cannot assess whether the retained deliverables are useful.

The SQL does not require positive duration or a positive minimum variant count, nor does it order or validate positive price-band endpoints. A stored structural_verification_passed flag is supplied, not computed from all qualitative criteria. Keep these limits visible rather than treating acceptance by the table as full validation.

M4.4: pricing decisions

`c4_pricing_decisions` requires a pricing-decision file, observed floor, median and ceiling, a positive anchor price, a pricing strategy and a pay-in-full price. Strategies are Median, Above Market, Below Market (Volume) or Other. Optional fields store installment and deposit descriptions, hours per buyer, effective hourly rate and rationale for deviation from the observed band. Score is zero to ten; at least seven generates passed.

The table can preserve the comparison and unit-economics assumptions, but it does not enforce floor ≤ median ≤ ceiling, positive pay-in-full price or coherent hours and effective rate. Nor does it independently validate the competitor observations. Explain the rationale and evidence in the linked artifact before treating the price as justified.

M4.5: anti-promises and integrity

`c4_anti_promises` requires anti-promise and integrity-statement file IDs, three to six audience exclusions, at least two outcome non-claims and at least two scope boundaries. The required signature Boolean defaults to false. A zero-to-ten score of at least seven and a true signature flag jointly generate passed. This records the boundary and signature assertion; a Boolean by itself is not a verified signature or an enforceable agreement.

M4.6: guarantees

`c4_guarantees` stores the guarantee and honesty-clause file IDs, a required signature flag defaulting false, guarantee type, component count, target weakness, sustainability flag and score. Types are Refund, Outcome, Hybrid, Time-shift and Effort-adjusted. There may be at most two components. The target must be Perceived Likelihood, Time Delay or Effort and Sacrifice. Expected activation percentage is optional. Passed requires score at least seven and a signed-clause flag.

The source records unit_economics_sustainable but does not include it in the generated pass condition. It also does not constrain the percentage to zero through one hundred or require a positive component minimum. Therefore, a row can satisfy the coded pass condition without establishing a sustainable guarantee. The written terms, evidence and authorized review still matter.

M4.7: landing-page copy

`c4_landing_page_copies` requires the page and provenance-log file IDs, permits a revision-log ID, limits total words to 1,000–5,000 and requires at least fifteen claimed Trigger Bank entries. It separately stores the number verified verbatim. Two optional reviewer IDs reference users, each paired with an optional completion timestamp. peer_reviews_complete is generated from the presence of both timestamps.

Passed requires an AI score of at least seven, both review timestamps and at least fifteen verified verbatim entries. The AI score is optional but, when present, constrained to zero through ten. Depending on null inputs, the Boolean expression can produce null rather than false; the completion function counts only passed = TRUE.

No shown constraint requires different reviewers, prevents self-review, ensures reviewer IDs accompany timestamps or ensures verified counts do not exceed claimed counts. The application and reviewer process must establish that the review and evidence are real. A generated Boolean protects its expression from direct assignment; it does not make owner-supplied inputs trustworthy.

M4.8: offer readiness

`c4_offer_readiness_docs` requires readiness and first-sale-checklist file IDs, selected variant A/B/C, final offer name and final anchor price. Signature defaults to false. The optional Opus validator verdict is PASS, NEEDS_REVISION or FAIL, with an optional run timestamp. At least three kill criteria must be declared. Passed requires a PASS verdict and a true signature flag.

This captures the intended final review gate. A Sonnet result elsewhere does not satisfy this explicit Opus-verdict field. However, the field does not authenticate which model or person produced its value, the anchor price is not constrained positive here, and the table stores a kill-criteria count rather than the criteria themselves. The linked artifact and trusted review process remain essential.

Review history and user summary

`c4_review_log` stores user, module M4.1 through M4.8, prompt name, version, required submission count defaulting to one, verdict PASS/FAIL/NEEDS_REVISION, optional integer score, feedback JSON, flags JSON and run time. Its score has no zero-to-ten constraint and submission count has no positive check. Preserve these differences rather than assuming the log has the same validation as every artifact.

The user table gains five columns: completion Boolean defaulting false, completion timestamp, lead variant, final offer name and final anchor price. These are summary fields populated by the shown trigger; their existence alone does not prove current eligibility or completion.

Enrollment eligibility: what is actually checked?

`check_c4_enrollment_eligible` accepts a user ID and returns JSON containing eligible and a missing-items list. It requires C3 complete, a market-fit hypothesis filed within the previous three months, a Trigger Bank with at least 200 entries, a Pricing Signals row and an oath signed within the previous twelve months. The hypothesis uses a strict newer-than boundary; the oath is rejected when missing or older than its boundary.

The function selects C1 completion, C2 completion and operator-identity filing but does not test them. It checks that Pricing Signals exists, not its quality or recency, and it does not validate every dependency named in the worksheet. These are differences between data read, conditions enforced and the broader educational prerequisites.

Completion checks and trigger behavior

`check_c4_completion` returns complete plus missing items after checking all eight artifact stages: distinction passed; equation passed; decomposition structural verification true; pricing passed; anti-promise passed; guarantee passed; landing page passed; and readiness passed. The named missing items retain the expected signature, peer-review and Opus context because those are part of the relevant table expressions.

`update_c4_complete_flag` calls that check for NEW.user_id. When complete, it reads the passing readiness row and sets the user completion flag true, stamps the current time and copies the selected variant, offer name and anchor price. Its trigger runs only after an insert or update to the readiness table when NEW.passed is true.

That means completing another artifact after readiness already passed does not automatically invoke this trigger. Neither deleting supporting evidence nor changing a prior result to failure resets completion through this code. The function only sets true and has no false branch. Repeated qualifying readiness updates can also restamp completion time. These are observations from the supplied SQL, not evidence that a live system currently behaves this way. A production design must decide how to re-evaluate changes and revocations.

Access controls and implementation limits

All nine tables enable row-level security. The eight artifact tables allow selecting, inserting and updating rows belonging to auth.uid(); no DELETE policy is shown. The review log permits owners to select their history, but its insert policy uses WITH CHECK (TRUE) without a TO role restriction. The adjacent service-only comment is not an access restriction. Actual access also depends on grants and runtime roles, which this file does not show.

Likewise, owner-based row access is not field-level grading authority. If ordinary users have the corresponding write grants, these policies do not stop them changing their own scores, verification flags or signature assertions. Review provenance and privileged fields need a defined trusted boundary before this can be treated as an authoritative completion system.

The eligibility and completion functions use SECURITY DEFINER and accept arbitrary user IDs. The shown definitions contain neither a caller-to-user authorization check nor an explicit secure search_path. Supabase's documentation explains the need to secure such functions and their execution permissions. Review those controls and actual grants before implementation; do not infer protection from schema-qualified table names alone.

Migration and operating references

The supplied migration sequence runs c1_schema.sql, c2_schema.sql, c3_schema.sql and then c4_schema.sql using psql with host, user and database placeholders. Reading this sequence does not execute it. Tables use IF NOT EXISTS and the five user columns use ADD COLUMN IF NOT EXISTS, but separate index, policy, constraint and trigger creation statements are not all guarded. The complete file therefore is not automatically safe to rerun unchanged.

The source names five related paths or integrations: RISER-Build-References-for-C4.md, C4-Review-Chain.md, C4-Prerequisites-Checklist.md, Build 6 src/c4_checkpoint_handler.ts and RISER-C4-Weekly-Rhythm-Setup-SOP.md. Their implementation and deployment are not supplied by this schema. Preserve the full SQL, comments, design notes and migration references in the appendix.

Apply the educational connection

This design attempts to turn Hormozi-style offer analysis into traceable artifacts before a Brunson-style offer presentation is finalized. The value of the database is provenance and accountable review, not merely a green completion flag. As authored practice, trace one worksheet from its file ID through cited evidence, rubric score, authorized review and downstream completion. Mark every unverified dependency and every condition the code does not enforce. Deliver a schema-to-artifact map and a review of those gaps; no database deployment is part of this lesson's completion.

Sources and resources

- Complete assigned C4 schema. - D0404: Value Equation Worksheet and D0413: actual reviewer YAML. - PostgreSQL constraints and CREATE POLICY: primary constraint and policy semantics. - Supabase row-level security and database functions: primary access-control references. - Acquisition.com value-equation checklist, ClickFunnels value ladder and RISER NATION CORP.

Assigned source links

D0438 original source 1

# C4 Prompt Chain — M4.1 through M4.8 Review Orchestration

**Purpose:** Documents the sequencing of the 6 C4 Claude system prompts across module checkpoints. Referenced by Build 6 when routing student submissions to reviewers and gating module unlock.
**Filed to:** `03_Scripts-and-Prompts/Prompt-Chains/`
**Referenced by:** Build 6 checkpoint handler; `04_Tools-and-Infrastructure/Supabase-C4-Schema.md`

---

## Chain Overview

C4 uses 6 system prompts across 8 checkpoints. Five are Sonnet-powered (routine review) and one is Opus-powered (course-completion gate). The chain is serial — each module's review must issue PASS before the next module's checkpoint can receive submissions.

```mermaid
graph TD
    M41_sub[M4.1 submission] --> P1[offer-distinction-reviewer<br/>Sonnet 4.6]
    P1 -->|PASS >=7/10| M42_sub[M4.2 unlocks]
    P1 -->|FAIL <7/10| M41_rev[M4.1 revision]
    M41_rev --> P1

    M42_sub --> P2[value-equation-application-reviewer<br/>Sonnet 4.6]
    P2 -->|PASS >=7/10| M43_sub[M4.3 unlocks]
    P2 -->|FAIL| M42_rev[M4.2 revision]

    M43_sub --> P3[offer-decomposition-reviewer<br/>Sonnet 4.6<br/>Structural only]
    P3 -->|PASS| M44[M4.4 unlocks]
    P3 -->|NEEDS_REVISION| M43_rev[M4.3 revision]

    M44 --> M44_review[M4.4 reviewed by<br/>offer-readiness-reviewer spot-check]
    M44_review -->|PASS| M45[M4.5 unlocks]

    M45 --> M45_review[M4.5 reviewed by<br/>offer-readiness-reviewer spot-check]
    M45_review -->|PASS| M46[M4.6 unlocks]

    M46 --> M46_review[M4.6 reviewed by<br/>offer-readiness-reviewer spot-check]
    M46_review -->|PASS| M47_sub[M4.7 unlocks]

    M47_sub --> PEER[2 peer reviews<br/>SLA 72hr]
    PEER --> P4[landing-page-copy-reviewer<br/>Sonnet 4.6]
    P4 -->|PASS >=7/10 AND peer count >=2| M48_sub[M4.8 unlocks]
    P4 -->|FAIL| M47_rev[M4.7 revision]

    M48_sub --> P5[offer-readiness-reviewer<br/>Sonnet 4.6<br/>Structural pre-screen]
    P5 -->|PASS| P6[offer-fit-validator<br/>OPUS 4.7<br/>Full coherence check]
    P5 -->|NEEDS_REVISION| M48_rev[M4.8 revision]

    P6 -->|PASS| COMPLETE([C4 Complete<br/>C5 Unlocks])
    P6 -->|NEEDS_REVISION| M48_rev
    P6 -->|FAIL| MENTOR[Mentor diagnosis<br/>Likely C3 M3.7 issue]

    style P6 fill:#B45F06,color:#fff
    style COMPLETE fill:#2E75B6,color:#fff
    style MENTOR fill:#CC0000,color:#fff
    style PEER fill:#BF9000,color:#fff
```

---

## Prompt Inventory

| # | Prompt File | Model | Called At | Cost per call | Typical volume |
|---|---|---|---|---|---|
| 1 | offer-distinction-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.1 checkpoint | $0.04-0.08 | 1-2 per student |
| 2 | value-equation-application-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.2 checkpoint | $0.04-0.08 | 1-2 per student |
| 3 | offer-decomposition-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.3 checkpoint | $0.04-0.08 | 1-2 per student |
| 4 | landing-page-copy-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.7 checkpoint (after peer review) | $0.06-0.12 | 1-2 per student |
| 5 | offer-readiness-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.4, M4.5, M4.6 spot-check + M4.8 pre-screen | $0.04-0.08 | 3-5 per student |
| 6 | offer-fit-validator-v1.0.0.yaml | **Opus 4.7** | M4.8 course-completion | **$0.30-0.55** | 1-2 per student |

**Total C4 review cost per student:** $0.80-$1.50 across the chain (most students complete in 1-2 submissions per module).

---

## Orchestration Rules

### Serial Dependency Enforcement

Module unlock only occurs when the prior module's review has returned PASS. A student cannot submit M4.3 until M4.2 has PASSED. This prevents coherence collapse — a student with a miscalibrated Value Equation should not be producing decomposition variants targeted at the wrong weakness.

### Revision Loop

For each module:
- First submission → review → PASS or revision guidance
- Second submission (after revision) → review → PASS or mentor escalation
- Third submission → mentor routing (rare; indicates fundamental issue with prior module outputs)

Build 6 tracks submission count per module; the third attempt auto-routes to mentor queue.

### Peer Review Layer (M4.7 only)

M4.7 is the only module requiring peer review before AI review. The order:

1. Student submits draft to `#c4-offer-ignition`
2. Two peer reviewers complete reviews (SLA 72 hours)
3. Student incorporates peer feedback, produces Revision Log
4. Revised submission routes to landing-page-copy-reviewer (Sonnet)
5. AI reviewer verifies: peer review count ≥ 2, integrity of incorporation, and rubric score

If peer review SLA is missed (cohort thin), Protocol A/B/C from `02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md` applies.

### The Opus Gate (M4.8 only)

M4.8 is the only module routing through two reviewers:

1. **offer-readiness-reviewer (Sonnet)** performs structural pre-screen
2. If Sonnet issues PASS → **offer-fit-validator (Opus 4.7)** performs full coherence check
3. If Sonnet issues FAIL → student revises before Opus is spun up (Opus is ~5-10x the cost of Sonnet; structural pre-screen prevents wasted Opus calls)

The Opus validator's PASS verdict unlocks C5 First Currents enrollment.

### Cross-Reference to Prior Course Outputs

Every prompt in C4 receives the relevant C1-C3 artifacts as input context. This prevents validators from accepting work that has silently drifted from the student's prior commitments:

- **C1 Captain's Oath Clause 1 (territory)** — fed to offer-distinction-reviewer, offer-fit-validator
- **C1 Operator Identity** — fed to offer-fit-validator (archetype consistency)
- **C2 Mechanism Hypothesis Document** — fed to offer-distinction-reviewer (mechanism name anchor)
- **C3 Market Fit Hypothesis** — fed to every C4 reviewer
- **C3 Trigger Bank** — fed to value-equation-application-reviewer, landing-page-copy-reviewer, offer-fit-validator
- **C3 Pricing Signals** — fed to offer-fit-validator
- **C3 Customer Interview Library (summaries)** — fed to value-equation-application-reviewer, offer-fit-validator

Without this context, each reviewer would be scoring the submission against itself rather than against the student's prior work. Cross-reference is what keeps the chain coherent.

---

## Build 6 Integration

Build 6 handles chain orchestration via the following SQL functions (full definitions in `04_Tools-and-Infrastructure/Supabase-C4-Schema.md`):

- `check_c4_enrollment_eligible(user_id)` — prerequisite check at enrollment
- `route_c4_submission(user_id, module, artifact_blob)` — routes to correct reviewer; passes C1-C3 context
- `log_c4_review_result(user_id, module, verdict, feedback)` — writes to `c4_review_log` table
- `unlock_next_c4_module(user_id, current_module)` — gated by prior module PASS
- `check_c4_completion(user_id)` — verifies all 8 artifacts present with PASS status
- `route_c4_to_c5(user_id)` — on course complete, opens C5 enrollment

---

## Failure Mode Routing

| Failure Pattern | Triggered By | Routed To |
|---|---|---|
| Mechanism drift from C3 | offer-fit-validator Check 2.3 BLOCKING | Mentor queue; reopen C3 M3.7 |
| Fabricated Trigger Bank entries | offer-fit-validator Check 2.4 BLOCKING | Integrity review queue |
| Anti-promise softening | offer-fit-validator Check 1.3 WARNING | Revision guidance; student reverts |
| Feature Stuffing (deliverable count, guarantee stack) | Check 4.1, 4.2 WARNING | Revision guidance |
| Silent weakness whitewash | Check 3.1 WARNING | Revision guidance |
| Signature not signed | Check 5.1 BLOCKING | 30-second fix + resubmit |
| Value Equation universal strength | value-equation-application-reviewer Dimension 3 | Revision with honest weakness identification |
| Three variants without axis divergence | offer-decomposition-reviewer Check 2 | Genuine variant diversification required |

---

## Versioning

All prompts are versioned following semver (v1.0.0). Changes to rubric criteria trigger a minor version bump; changes to scoring thresholds trigger a patch bump. Quarterly review cadence is owned by the curriculum-quality team.

When a prompt version changes, Build 6 continues routing existing in-progress submissions to the prior version until the student clears that checkpoint; new submissions after the version bump route to the new version. This prevents mid-revision rubric changes from surprising students.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by Build 6*

# C4 Peer Review Preparation Checklist

**Purpose:** Pre-flight check before submitting M4.7 landing page copy for cohort peer review. Prevents common rework-causing gaps.
**Time to complete:** 15-20 minutes before submission
**Filed to:** Attached to your M4.7 submission

---

## Before You Submit

Running this checklist before posting in `#c4-offer-ignition` saves your peer reviewers 30-60 minutes per review and dramatically increases the quality of feedback you receive. Reviewers who have to hunt for your Trigger Bank Provenance Log, or who notice your anti-promise softened from M4.5, spend their review time on mechanical issues rather than substantive feedback.

---

## Section A — Document Completeness

- [ ] Landing page copy file exists at `Offer-Landing-Page-Copy-[YourName]-[Date].md`
- [ ] All 7 sections present in order:
  - [ ] Section 1 — Problem (200-400 words)
  - [ ] Section 2 — Agitation (150-300 words)
  - [ ] Section 3 — Solution-and-Mechanism (300-500 words)
  - [ ] Section 4 — Proof (200-400 words)
  - [ ] Section 5 — Offer (300-500 words)
  - [ ] Section 6 — Anti-Promise-and-Guarantee (250-400 words)
  - [ ] Section 7 — CTA (50-150 words)
- [ ] Total word count in 1,800-2,500 range (not absurdly over or under)

## Section B — Trigger Bank Usage

- [ ] Trigger Bank Provenance Log file exists at `Landing-Page-Trigger-Bank-Provenance-[YourName]-[Date].md`
- [ ] Log contains ≥ 15 entries mapped to landing page usage
- [ ] Every entry in the log is verbatim (not paraphrased) from the source Trigger Bank
- [ ] Each entry cites specific Trigger Bank ID (TB-###) or Interview #
- [ ] Entries are distributed across 4+ of the 7 sections (not all stacked in one section)

## Section C — Anti-Promise and Guarantee Integrity

- [ ] Anti-Promise in Section 6 is substantively the same as your M4.5 Anti-Promise Statement
- [ ] If any softening occurred between M4.5 and M4.7, it is reverted OR documented with rationale
- [ ] Anti-Promise Integrity Statement is signed
- [ ] Guarantee in Section 6 is substantively the same as your M4.6 Guarantee Architecture
- [ ] If any stacking occurred between M4.6 and M4.7, it is reverted
- [ ] Guarantee Honesty Clause is signed

## Section D — Offer Section Completeness

- [ ] Named deliverable (5-Test-passed name) visible in Section 5
- [ ] Price visible in Section 5 (not hidden, not ranged)
- [ ] Payment options listed
- [ ] Delivery structure described (engagement model, duration, cadence)
- [ ] Deliverables list is not over 8 items (Feature Stuffing Trap check)

## Section E — Proof Integrity

- [ ] Proof cases in Section 4 are specific (named or anonymized with specific outcome)
- [ ] If you have fewer than 4 named cases, the Known Weaknesses acknowledgment is visible (not papered over)
- [ ] Testimonials (if any) are verbatim quotes, not paraphrased
- [ ] Testimonials have attribution (name or anonymized but specific)

## Section F — CTA Specificity

- [ ] CTA names a specific action (not "click here")
- [ ] Next cohort / enrollment date is present
- [ ] Qualification process (if any) is described
- [ ] Contact email or channel is present for pre-purchase questions

## Section G — Voice Check

- [ ] You have read the full landing page out loud once, from start to finish
- [ ] The page does not contain phrases you would not actually say to a buyer in person
- [ ] The page does not contain hyperbole you cannot substantiate
- [ ] The page does not contain any of these phrases: "game-changer," "revolutionary," "transform your life," "all you need to do is" (low-substance signaling vocabulary)

## Section H — Review Request Post

Before posting in `#c4-offer-ignition`, prepare the post:

- [ ] Drive link to landing page copy
- [ ] Drive link to Trigger Bank Provenance Log
- [ ] Brief context (2-3 sentences about your offer's key positioning)
- [ ] Specific request: "2 peer reviews within 72 hours, using the C4 Peer Review Template"
- [ ] Your availability to return review favor (which days you can review others' copy)

---

## Common Pre-Submit Fixes

If any checklist item is unchecked, common fixes:

| Unchecked Item | Typical Fix |
|---|---|
| Section 6 softened from M4.5/M4.6 | Revert to the original M4.5 Anti-Promise and M4.6 Guarantee language |
| Trigger Bank count < 15 | Add 3-6 more verbatim entries, typically in Problem and Agitation sections |
| Deliverables > 8 | Review for Feature Stuffing; which deliverables are compensation, which are real value? |
| Price hidden or ranged | Move price to Section 5 with explicit number |
| Voice check fails | 48-hour cooling re-read; rewrite any section where "did I actually say that?" is your reaction |

---

## After Submission

Once posted:

- [ ] Check `#c4-offer-ignition` daily for reviewer pickup
- [ ] Respond promptly to reviewer questions
- [ ] Do not revise the landing page while reviews are in progress (creates version mismatch)
- [ ] Begin reviewing other cohort peers' landing pages as reviews arrive — reciprocity is cohort norm

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

# C4 Peer Review Outreach Scripts

**Purpose:** Short scripts for requesting and responding to peer reviews during M4.7. These are starter templates; adapt in your own voice.
**Filed to:** `03_Scripts-and-Prompts/Outreach-Scripts/`
**Referenced by:** M4.7 Written Lesson; C4-Peer-Review-Preparation-Checklist

---

## Script 1 — Requesting Peer Review (post in `#c4-offer-ignition`)

```
**M4.7 peer review request — [YourName]**

- **Offer name:** [5-Test-passed name]
- **Target buyer:** [one sentence describing who this is for]
- **Price:** $[X]
- **What I want reviewers to watch for specifically:**
  - [1-2 things you suspect may be weak — common: Section 4 Proof, Section 6 Anti-Promise softening, Trigger Bank entry density]

**Drive links:**
- Landing page copy: [link]
- Trigger Bank Provenance Log: [link]
- Revision Log (so far): [link — if you have one]

**SLA:** 72 hours ideal

**Reciprocity:** I'm available to review copy on [specific days this week]. Reply with yours and I'll pick up the first two.

Using the C4 Peer Review Template (`02_Resources/Templates/C4-Peer-Review-Template.md`).
```

### Why this structure works

Naming what you suspect is weak focuses reviewer attention. Without this, reviewers tend to spread feedback thin across the whole page. Concentrated attention on 1-2 sections produces higher-signal feedback.

---

## Script 2 — Offering Peer Review (response to another student's request)

```
I'll pick up your review, [TheirName]. I'll aim to deliver within 48 hours.

If you want me to pay particular attention to [suggested focus based on their request], I will. If you want me to do a straight full-template review, I'll do that too.

My C4 Peer Review Template will be back in your Drive folder or Circle.so thread by [specific date + time].
```

### Why this structure works

Confirms the commitment with a specific delivery time. Acknowledges their request-specific focus areas. Creates accountability for the delivery.

---

## Script 3 — Declining a Peer Review (when over-committed)

```
Thanks for tagging me, [TheirName]. I'm at capacity this week ([reason if relevant — e.g., "I'm in my own M4.7 cycle with deadline Thursday"]).

Tagging [OtherName] who mentioned they had bandwidth this week. You can also use the Alternate Protocol at `02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md` if the cohort is thin at your pacing — Protocol A (mentor substitution) is available.
```

### Why this structure works

Declining without leaving the requester stranded. Referring to Alternate Protocol reminds the requester that the safety net exists.

---

## Script 4 — Delivering Peer Review (after completing the template)

```
[TheirName] — review complete.

**Template:** [Drive link to completed Peer Review Template]

**Top-level observation:** [one sentence — your overall impression]

**My three recommended revisions (from template):**
1. [brief version]
2. [brief version]
3. [brief version]

Happy to discuss any of these in async DM if useful. Good luck with M4.8.
```

### Why this structure works

Surfaces the most actionable takeaway in the message itself so the requester can start revising without waiting to open the full template. The full template provides depth; the message provides urgency.

---

## Script 5 — Responding to Peer Review (after incorporating)

```
[ReviewerName] — thanks for the review. Incorporated as follows:

- **Revision 1 you recommended:** [incorporated / incorporated with modification / not incorporated + reason]
- **Revision 2:** [same format]
- **Revision 3:** [same format]

Revision Log in Drive: [link]

Appreciate the time.
```

### Why this structure works

Closes the loop on every recommendation. Decisions not to incorporate are documented (not silently ignored). The Revision Log is what the offer-fit-validator at M4.8 checks for.

---

## Script 6 — Escalating to Mentor (when Alternate Protocols Fail)

Address to `#mentor-requests` Circle.so channel or via the mentor Calendly link from cohort welcome email:

```
**C4 M4.7 peer review escalation — [YourName]**

- Cohort pacing window: [your dates]
- Peer reviews attempted: [how many requests, how many responses]
- Alternate Protocols tried: [A — mentor booking status / B — cross-stage post status / C — paid review status]

**Specific help requested:** [mentor review of landing page, or pacing adjustment, or cohort coordination]

**Drive link:** [landing page copy]
**SLA needed:** [your revised timeline]
```

### Why this structure works

Names what has already been tried so the mentor does not repeat the available paths. Specifies what help is actually requested so the mentor can respond efficiently.

---

## Cohort Etiquette

A few norms that make peer review work sustainably across the cohort:

### Reciprocity

The cohort operates on a rough reciprocity norm: if you ask for reviews, you offer them. Students who take reviews without giving them quickly exhaust peer willingness. This is not enforced policy — it is cohort culture.

### Specificity Over Generosity

Reviews saying "this is great!" are useless. Reviews saying "Section 2 Agitation feels performative — specifically the 'wasted years' language in paragraph 2 reads generic against the specific Trigger Bank language in Section 1" are useful. Prefer specificity even when it is critical.

### Honest Over Kind

Kind reviews that paper over weak sections serve the student short-term and harm them medium-term (the weak sections surface in C5 anyway, now harder to fix because the student thought they were okay). Honest reviews that name specific weaknesses are the service.

### Respond Within SLA

72-hour SLA is a cohort commitment. If you cannot hit it, decline (Script 3) rather than miss silently. Missed SLAs are the single largest cause of C4 M4.7 pacing disruption.

---

## When To Use These Scripts vs. Your Own Voice

These scripts are starters. Adapt in your voice, especially for Scripts 1 and 4 — mechanical-sounding review requests signal to cohort peers that you have not yet internalized the discipline of the M4.7 work. Personal voice in the request correlates with higher-quality responses.

Scripts 2, 3, and 6 are more mechanical — they coordinate logistics rather than substance — and can stay closer to template voice.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

sop_id: C4-SOP-02
title: Peer Review Coordination Process
version: 2.0.0
course_scope: C4 Offer Ignition
modules_covered: [M4.7]
owner: curriculum-quality-team
last_reviewed: 2026-04-24

purpose: >
  Standardize the M4.7 peer review process from request through delivery and
  through revision incorporation. M4.7 is the only C4 module requiring peer
  review (instructor HITL is deferred to C5; AI rubric runs after peer reviews
  are incorporated). Peer review is the first time the offer is exposed to
  outside readers; the process must protect both reviewer time and reviewee
  outcomes. This SOP defines reciprocity, SLA, alternate protocols, and
  revision logging.

prerequisites:
  - M4.7 Landing Page Copy first draft complete in Drive
  - Trigger Bank Provenance Log complete in Drive
  - C4-Peer-Review-Preparation-Checklist run before submission
  - 48-hour cooling period observed between first draft and submission

roles:
  - submitting_student: requests review; reciprocates by reviewing 2 peers
  - peer_reviewer_1: cohort peer at compatible pacing
  - peer_reviewer_2: second cohort peer at compatible pacing
  - mentor: escalation if Alternate Protocols A/B/C all fail
  - cross_stage_reviewer: Stage 2+ alumnus available via Protocol B
  - paid_reviewer: from Approved Paid Review Options list (Protocol C)
  - build_6: tracks SLA, matches reviewers, gates M4.7 checkpoint progression

process:
  step_1:
    name: Pre-Submission Self-Audit
    time: 20 min
    output: Completed Peer Review Preparation Checklist
    activities:
      - Run C4-Peer-Review-Preparation-Checklist sections A through H
      - Address any unchecked items before posting review request
      - Verify Trigger Bank entry count >= 15 with Provenance Log complete
      - Verify anti-promise unchanged from M4.5; verify guarantee unchanged from M4.6
    quality_gate: All preparation checklist items checked; if any item is unchecked, fix before requesting review
    common_failures:
      - "Posting request before Trigger Bank entries reach 15"
      - "Posting request with anti-promise softened from M4.5 (peer reviewers will flag, costing 24-48 hours)"
      - "Forgetting to attach Trigger Bank Provenance Log"
    mitigation: The checklist exists specifically to catch these. Run it.

  step_2:
    name: Request Review (Standard Protocol)
    time: 15 min
    output: Review request post in #c4-offer-ignition Circle.so channel
    activities:
      - Use Outreach Script 1 from C4-Peer-Review-Outreach-Scripts.md
      - Specify offer name, target buyer, price, areas you suspect are weak
      - Attach Drive links to landing page copy AND Trigger Bank Provenance Log
      - State 72-hour SLA expectation
      - Offer specific reciprocity (which days you can review others' copy this week)
    quality_gate: Post visible in #c4-offer-ignition; request structure matches Outreach Script 1
    common_failures:
      - "Vague request without specifying suspected-weak sections (reviews come back generic)"
      - "Not offering reciprocity (cohort norm violated; future review requests slower to receive responses)"
      - "Missing Provenance Log attachment (reviewers can't verify Trigger Bank usage)"
    mitigation: Use the script verbatim until it becomes natural

  step_3:
    name: Reviewer Pickup (24-48 hours from request)
    time: passive
    output: 2 peers commit to review with stated delivery dates
    activities:
      - Build 6 sends notification to active cohort peers at compatible pacing
      - Peers respond using Outreach Script 2 (acceptance) or Script 3 (decline with referral)
      - Build 6 logs commitments and tracks SLA
      - If only 1 reviewer commits within 48 hours, Build 6 escalates per step 4a
    quality_gate: 2 reviewers committed within 48 hours
    common_failures:
      - "Cohort thin at student's pacing (Protocol A activates)"
      - "Reviewers who committed silently miss SLA without communication"
    mitigation: Build 6 active SLA tracking surfaces silent misses; cohort norm includes communicating early if SLA at risk

  step_4_alternate_protocol_a:
    name: Mentor Substitution (Protocol A)
    time: 24 hours from activation
    output: Mentor named as reviewer; review delivered within 72 hours
    activation_trigger: Cohort has < 4 active peers at compatible pacing OR < 2 peers commit within 48 hours
    activities:
      - Student books mentor review slot via Calendly link in cohort welcome email
      - OR Student posts in #mentor-requests with M4.7 review request
      - Mentor delivers full Peer Review Template completion within 72 hours
      - Mentor review counts as both required peer reviews
    quality_gate: Mentor review filed with C4-Peer-Review-Template completion
    common_failures:
      - "Mentor booking backed up 2+ weeks during high-enrollment cycle (rare; route to Protocol B)"

  step_4_alternate_protocol_b:
    name: Cross-Stage Review (Protocol B)
    time: 96 hours from activation
    output: 1-2 Stage 2+ alumni reviewers complete review
    activation_trigger: Mentor backed up; OR student prefers reviewer who has shipped offers
    activities:
      - Student posts in #cross-stage-review channel using request format from Alternate Protocol document
      - Stage 2-5 operators who actively volunteer review time pick up the request
      - Review uses C4 Peer Review Template
      - Cross-stage review counts as both required reviews, OR pairs with one peer/mentor review
    quality_gate: Cross-stage review filed
    common_failures:
      - "No cross-stage reviewer picks up within 48 hours (route to Protocol C)"

  step_4_alternate_protocol_c:
    name: Approved Paid Review (Protocol C — Last Resort)
    time: 48-72 hours from activation
    output: Paid reviewer completes review using C4 Peer Review Template
    activation_trigger: Protocols A and B unavailable within student's planned week
    activities:
      - Student selects from C4-Approved-Paid-Review-Options.md (Tier A/B/C)
      - Direct engagement; Academy does not facilitate payment
      - Paid reviewer completes C4 Peer Review Template
      - Paid review counts as 1 of 2 required reviews; must pair with peer/mentor/cross-stage for second
      - Methodology consistency check: any methodology-conflicting paid feedback flagged before incorporation
    quality_gate: Paid review filed; second review (peer/mentor/cross-stage) also filed
    common_failures:
      - "Paid reviewer recommends removing anti-promise (methodology-conflict; do not incorporate without mentor consult)"
      - "Paid reviewer recommends stacking guarantees (methodology-conflict)"
      - "Student counts paid review as both required reviews (not allowed)"
    mitigation: Approved Paid Review document provides methodology baseline language to send to paid reviewer

  step_5:
    name: Receive and Read Reviews
    time: 30 min (do not act yet)
    output: Both reviews read in single sitting
    activities:
      - Wait until both reviews have arrived before reading either
      - Read both in one sitting; note patterns
      - If both reviewers flagged the same section as weak, that section is genuinely weak
      - If reviewers disagree, use your judgment
      - Do not begin revision yet — sleep on the feedback
    quality_gate: Both reviews read; pattern notes captured
    common_failures:
      - "Reading first review and immediately starting revisions before second review arrives (creates whiplash if reviewers disagree)"
      - "Defending against feedback in your head without genuinely considering it"
    mitigation: 12+ hour gap between reading and revising; treat reviews as gifts, not attacks

  step_6:
    name: Draft Revision Log + Revise
    time: 60-90 min
    output: Revision Log file + revised landing page in Drive
    activities:
      - Open C4-Peer-Review-Outreach-Scripts.md Script 5 template
      - For each suggestion in each review: incorporated / incorporated with modification / not incorporated + reason
      - Document each decision; the offer-fit-validator at M4.8 reads this
      - Revise landing page based on incorporated suggestions
      - Address pattern-flagged sections (those flagged by both reviewers) with priority
    quality_gate: Revision Log complete; revised landing page in Drive
    common_failures:
      - "Skipping the Revision Log (validator at M4.8 will flag missing log)"
      - "Incorporating every suggestion mechanically (you should make decisions, not absorb)"
    mitigation: The Log is the structural mechanism that forces decision-making; do not skip

  step_7:
    name: Reciprocate
    time: 90-120 min total (45-60 min per review × 2)
    output: 2 completed peer reviews delivered to other students
    activities:
      - During or after your own revision cycle, complete 2 peer reviews for cohort peers
      - Use C4-Peer-Review-Template for each
      - Deliver via Outreach Script 4 from outreach scripts document
      - Reciprocity is cohort norm; tracking is light but reputation matters
    quality_gate: 2 reviews delivered; Build 6 logs reciprocity in cohort metrics
    common_failures:
      - "Receiving reviews and not reciprocating (silent reputation cost; future requests slower to receive responses)"
      - "Reciprocating with low-effort 'looks great!' reviews (worse than declining; harms peer's revision quality)"
    mitigation: If you genuinely cannot reciprocate this cycle, decline future review requests until you can; do not free-ride

  step_8:
    name: Submit Revised Landing Page to AI Rubric
    time: 5 min + 5 min for rubric run
    output: landing-page-copy-reviewer score >= 7/10
    activities:
      - Submit revised landing page + provenance log + revision log to Build 6
      - Build 6 invokes landing-page-copy-reviewer-v1.0.0.yaml
      - Verify peer_review_count >= 2 in submission metadata
      - Receive rubric score within 5 minutes
    quality_gate: Score >= 7/10; peer_review_count = 2; no integrity flags
    common_failures:
      - "Submitting without filing the Revision Log first (rubric flags missing artifact)"
      - "Trigger Bank entries fabricated or paraphrased (rubric flags as integrity issue)"
    mitigation: All checks should already have passed in step 5-6; if rubric flags appear, fix and resubmit

review_and_adjustment:
  cadence: Per cohort cycle
  questions_to_ask:
    - "What % of M4.7 submissions used Standard Protocol vs Alternate Protocol A/B/C?"
    - "What was the median time from review request to review delivery?"
    - "What % of reviewers met SLA without escalation?"
    - "What % of paid reviewers gave methodology-conflicting feedback?"
  adjustment_principles:
    - If Alternate Protocol A activation > 30%, expand mentor capacity OR extend cohort recruitment to thicken cohorts
    - If paid reviewer methodology conflicts > 20%, refresh paid reviewer Affiliate Agreements OR remove specific reviewers from Approved list
    - If reciprocity ratio (reviews given / reviews received) < 0.85, surface in cohort discussion

escalation_triggers:
  - 3+ submissions fail M4.7 rubric on same student (mentor diagnosis)
  - Reviewer fabrication or methodology-conflicting feedback (Affiliate Agreement review)
  - Reciprocity ratio < 0.5 for individual student over 2 cohorts (cohort norm conversation)
  - Cohort thinning > 3 weeks consecutive (Build 6 → Marketing for cohort recruitment review)

related_documents:
  - 02_Resources/Templates/C4-Peer-Review-Template.md
  - 02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md
  - 02_Resources/Templates/C4-Approved-Paid-Review-Options.md
  - 02_Resources/Checklists/C4-Peer-Review-Preparation-Checklist.md
  - 03_Scripts-and-Prompts/Outreach-Scripts/C4-Peer-Review-Outreach-Scripts.md
  - 03_Scripts-and-Prompts/Claude-System-Prompts/landing-page-copy-reviewer-v1.0.0.yaml

# C4 Peer Review Template — M4.7 Landing Page Copy

**Purpose:** Structured template for cohort peer reviews of M4.7 landing page copy. Two peer reviews per student are required; students complete two reviews for peers in exchange.
**Time per review:** ~45-60 minutes
**Timeline:** 72-hour SLA from review request to delivery
**Filed to:** Build 8 Drive folder; linked into submitting student's M4.7 folder

---

## Reviewer Instructions

Read the landing page copy and the Trigger Bank Provenance Log in one pass, then complete the template below. Your job is not to edit line-by-line — the submitting student will do that. Your job is to surface structural issues they cannot see from inside their own draft.

Three things you are specifically looking for:

1. **Does the page sound like the market or like the operator?** You are an outside reader who has not been inside this operator's head for 4 weeks. You can hear voice drift more clearly than they can.

2. **Are the verbatim Trigger Bank quotes doing work, or are they decorative?** Quotes should anchor specific claims. A quote dropped next to a general statement without connection is not working.

3. **Is the anti-promise actually specific, and is the guarantee actually clean?** M4.5 and M4.6 stand-alone documents can be strong but get softened in the landing page. You are the second set of eyes that catches softening.

---

## Reviewer Information

**Reviewer name:** _____________________________
**Reviewer operator archetype:** _____________________________
**Review date:** _____________________________
**Submitting operator name:** _____________________________
**Submitting operator's offer name:** _____________________________

---

## Section-by-Section Review

### Section 1 — Problem

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak
**One-sentence read:** [What is this operator's offer trying to solve, in your words?]

Does the Problem section make the buyer's current state specific and vivid?
☐ Yes, I could visualize it ☐ Partially ☐ No, it was generic

Was at least one verbatim Trigger Bank quote integrated meaningfully (not decoratively)?
☐ Yes ☐ Partially ☐ No

**Specific observations (1-3 sentences):**

---

### Section 2 — Agitation

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Does the Agitation section make the cost of *not acting* feel real, or does it feel performative?
☐ Real ☐ Mixed ☐ Performative

Did any specific numbers, time-frames, or opportunity costs make the Agitation land?
☐ Yes (which ones: __________) ☐ No

**Specific observations:**

---

### Section 3 — Solution-and-Mechanism

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

After reading this section, can you describe the mechanism in your own words?
☐ Yes, I could teach it to a friend ☐ Roughly ☐ No, it's still fuzzy

Are the 4 pillars of the mechanism visible, even if not labeled as pillars?
☐ Yes ☐ Partially ☐ No

**Specific observations:**

---

### Section 4 — Proof

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Are the proof cases specific (named, with outcome data), or are they generic ("Maya is great")?
☐ Specific ☐ Mixed ☐ Generic

If the operator has few case studies, is that acknowledged honestly, or is it papered over?
☐ Acknowledged honestly ☐ Handled in between ☐ Papered over

**Specific observations:**

---

### Section 5 — Offer

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Is the named deliverable clear, specific, and 5-Test-passed?
☐ Yes ☐ Partially ☐ No (how could it be clearer: __________)

Is the price visible on the page?
☐ Yes, clearly ☐ Present but buried ☐ Not visible

Does the delivery structure tell you what the buyer's experience actually is (what they do, when, with whom)?
☐ Yes, concretely ☐ Vaguely ☐ Not really

**Specific observations:**

---

### Section 6 — Anti-Promise-and-Guarantee

**This is the most important section to peer-review.**

**Anti-Promise strength:** ☐ Strong ☐ Adequate ☐ Weak

Does the anti-promise name three specific exclusions?
☐ Yes, three or more ☐ Two ☐ One or fewer

Are any of the "exclusions" actually flattering descriptions of the target buyer (e.g., "not for unmotivated people")?
☐ No, they are genuine exclusions ☐ One or two are flattering-dressed-as-exclusion ☐ Most are

**Guarantee strength:** ☐ Strong ☐ Adequate ☐ Weak

Is the guarantee a clean structure (one primary + one optional complementary), or is it stacked with three or more components?
☐ Clean ☐ Borderline ☐ Stacked (Feature Stuffing Trap signal)

If you were a buyer who met the activation conditions, do you trust this operator would honor the guarantee without friction?
☐ Yes ☐ Mostly ☐ Uncertain

**Specific observations:**

---

### Section 7 — CTA

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Does the CTA name a specific action (not "click here") and a specific outcome ("enroll in the Feb 12 cohort, receive Welcome Kit within 24 hours")?
☐ Yes, specific ☐ Partially ☐ Generic

Is there a clear timeline (cohort start date, enrollment close date)?
☐ Yes ☐ No

**Specific observations:**

---

## Cross-Cutting Review

### Verbatim Trigger Bank Usage

Pick 3 of the Trigger Bank quotes used in the landing page. Check them against the Provenance Log — do they match the source entry verbatim, or have they been paraphrased into "cleaner" language?

- **Quote #1:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased
- **Quote #2:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased
- **Quote #3:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased

**Overall provenance accuracy:** ☐ Strong (all 3 verbatim) ☐ Mixed ☐ Weak (paraphrasing is dominant)

### Voice Check

Does the page sound like the operator or like the market?
☐ Mostly market voice ☐ Mixed (operator voice leaks through in specific sections: __________) ☐ Mostly operator voice

### Total Trigger Bank Entry Count

Count the verbatim quotes in the landing page.
**Count:** ___ / 15 minimum

If below 15, the submission fails the M4.7 checkpoint.

---

## Top-3 Revisions You Recommend

Identify the three revisions that would most improve this landing page:

1. **Revision 1:**
2. **Revision 2:**
3. **Revision 3:**

Each revision should be specific enough that the operator can act on it ("tighten the Problem section opening from 4 sentences to 2") rather than abstract ("improve the copy").

---

## Reviewer Closeout

**Overall assessment:** ☐ Ready to submit ☐ Needs moderate revision ☐ Needs substantial revision

**Would I buy this offer if I were the target buyer?** ☐ Yes ☐ Maybe ☐ No — and why: __________

**Reviewer signature:** _____________________________

---

## For the Submitting Operator

After receiving both peer reviews:

1. Read both reviews in one sitting before acting on either. Look for patterns — if both reviewers flagged the same section as weak, that section needs real work. If they disagree, use your judgment.

2. Your job is not to accept every suggestion. Your job is to take each suggestion seriously and make a documented decision about whether to incorporate it.

3. File a Revision Log (`Revision-Log-M4.7-[YourName]-[Date].md`) noting which suggestions you incorporated, which you considered but did not incorporate, and why. The offer-fit-validator at M4.8 checks for this log.

4. Revise. Submit the revised landing page to the AI rubric (`landing-page-copy-reviewer-v1.0.0.yaml`).

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

# C4 Peer Review Alternate Protocol

**Purpose:** Alternate paths when your active C4 cohort has fewer than 4 peers at your pacing window. Ensures M4.7 does not stall for reviewer unavailability.
**Referenced by:** `00_Course-Overview/C4-Prerequisites-Checklist.md`
**Escalation path:** If none of the protocols below are viable, escalate to RISER Nation mentor within 72 hours of M4.7 draft completion.

---

## When to Use This Protocol

Use when any of the following is true:

- Your C4 cohort Circle.so channel (`#c4-offer-ignition`) has fewer than 4 active operators at your pacing window
- Cohort peers at your pacing window have not responded within 72 hours of your review request
- Your cohort is pacing unusually (ahead or behind the main cohort cycle) and peers are not currently at M4.7

---

## Protocol A — Mentor Substitution (Default)

**Who it's for:** Any student whose cohort is too thin for 2 peer reviews.

**How it works:**

1. Book a 45-minute review slot with a named RISER Nation mentor via the Calendly link in the cohort welcome email, or via the `#mentor-requests` Circle.so channel.
2. Submit your M4.7 draft and Trigger Bank Provenance Log at least 24 hours before the review call.
3. The mentor completes the C4 Peer Review Template during or after the call and delivers a written review within 72 hours.
4. Mentor review counts as both required peer reviews. No additional review needed.

**SLA:** 72 hours from submission to written review delivery (typical) ; 96 hours worst-case.

**Cost:** No charge. Mentor capacity is allocated out of Academy program support time.

**When Protocol A is not available:** Mentor booking backed up 2+ weeks. Rare but happens in high-enrollment cycles. Shift to Protocol B.

---

## Protocol B — Cross-Stage Review

**Who it's for:** Students whose mentor booking is backed up, or who prefer review from an operator who has already shipped offers.

**How it works:**

1. Post a review request in the `#cross-stage-review` Circle.so channel with the following structure:

   ```
   **Cross-stage review request — C4 M4.7**
   - Operator archetype: [Teacher / Service / Builder / etc.]
   - Territory: [one sentence]
   - Offer name: [the 5-Test-passed name]
   - Request: 1-2 Stage 2+ operators for M4.7 landing page review
   - SLA: 96 hours
   - Drive link: [link to your draft]
   - Trigger Bank Provenance Log: [link]
   ```

2. Stage 2, Stage 3, Stage 4, or Stage 5+ operators who are active volunteers pick up the review.
3. Review uses the same C4 Peer Review Template.
4. Cross-stage review counts as both required peer reviews, or as one review paired with a mentor/peer review.

**SLA:** 96 hours (longer than peer review because cross-stage operators volunteer review time around their own operation).

**Cost:** No charge. Typically treated as ecosystem reciprocity; Stage 2+ operators accumulate review credit that Stage 1 peers volunteer back.

**Why this can be better than peer review:** Reviewers who have shipped offers have firsthand knowledge of what survives first-sale contact and what does not. Their feedback often has higher signal-to-noise than peer-to-peer review.

**When Protocol B is not available:** No cross-stage reviewer picks up the request within 48 hours. Rare but happens near holiday periods. Shift to Protocol C.

---

## Protocol C — Paid Review (Last Resort)

**Who it's for:** Students whose timeline is blocked and Protocols A and B did not clear within their planned week.

**How it works:**

1. Choose from the Approved Paid Review list in `C4-Approved-Paid-Review-Options.md`.
2. Directly engage the reviewer (paid engagement; Academy does not facilitate payment).
3. Paid reviewer completes the C4 Peer Review Template.
4. Paid review counts as one of the two required reviews. **Paid review alone is not sufficient** — pair with one mentor, cross-stage, or peer review.

**SLA:** per reviewer contract, typically 48-72 hours.

**Cost:** Varies by reviewer. Typical range: $150-$400 per review.

**When Protocol C is genuinely necessary:** rare. Most students who think they need Protocol C actually have a timing problem that Protocol A or B resolves with a slight pacing adjustment (waiting 3-5 extra days for mentor or cross-stage slot).

**Warning:** paid review is a legitimate professional service but is not a substitute for cohort accountability. Paid reviewers who are not familiar with RISER Nation methodology sometimes give advice that conflicts with C3/C4 doctrine (e.g., suggesting feature-stuffed guarantees or removal of the anti-promise section). Review paid feedback critically against the module lessons; do not incorporate paid advice that conflicts with the methodology without checking with a mentor.

---

## Scholarship Path for Protocol C

If your cohort is thin, Protocols A and B are unavailable within your timeline, and Protocol C is financially inaccessible:

1. Email `[email protected]` with "C4 M4.7 Review Scholarship Request" in the subject line
2. Include your Drive link, pacing dates, and which Protocols were attempted
3. SLA: 48 hours for response; if approved, scholarship covers one paid review up to $200

Scholarship approval is typical for genuine thin-cohort situations.

---

## Logging the Alternate Protocol

Whatever Protocol you used, log it in your M4.7 Revision Log so the offer-fit-validator at M4.8 has the context:

```
Peer Review Protocol: [A — Mentor / B — Cross-Stage / C — Paid + one of A or B / Standard two-peer]
Reviewer 1: [name, protocol, date of review]
Reviewer 2: [name, protocol, date of review]
Alternate protocol rationale: [1-2 sentences]
```

The offer-fit-validator does not penalize Alternate Protocol usage — it penalizes missing reviews. Logging the protocol used keeps the validator's coherence checks from flagging the submission.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by C4-Prerequisites-Checklist*

# C4 Approved Paid Review Options

**Purpose:** Reference list of paid review providers vetted by RISER Nation for C4 M4.7 landing page review when cohort peer and mentor options are unavailable (Protocol C in the Peer Review Alternate Protocol).
**Referenced by:** `C4-Peer-Review-Alternate-Protocol.md`
**Status:** This list is maintained by the Academy team and updated quarterly. The version below reflects approved reviewers as of the Last Updated date.

---

## Selection Criteria

To appear on this list, a reviewer has:

- Reviewed at least 20 C4-style offer landing pages in the direct-response tradition
- Demonstrated familiarity with mechanism-based offer construction (Hormozi-adjacent methodology)
- Produced reviews that respect the anti-promise section as a credibility mechanism (rather than recommending its removal)
- Signed the RISER Nation Reviewer Affiliate Agreement — which commits them to methodology-consistent feedback
- Been cross-rated by at least 5 past reviewees as useful and non-disruptive

Reviewers without these properties are excluded from the list, regardless of market reputation.

---

## Current Approved Reviewers (Quarterly Update — Q2 2026)

### Tier A — Deep Direct-Response Specialists

These reviewers have 10+ years of direct-response copy experience. Pricing reflects seniority.

- **Reviewer Slot A1** — [reviewer name redacted for template; actual list maintained in Drive]
  - **Pricing:** $350-$450 per review
  - **SLA:** 72 hours
  - **Specialty:** coaching/consulting offers; cohort programs; Teacher-Operator and Service-Operator archetypes
  - **Contact:** [via Calendly link in Drive version]

- **Reviewer Slot A2**
  - **Pricing:** $300-$400 per review
  - **SLA:** 48-72 hours
  - **Specialty:** productized services; Builder-Operator archetype
  - **Contact:** [via Drive]

### Tier B — Mid-Senior Reviewers

5-10 years of direct-response experience. Pricing is moderate.

- **Reviewer Slot B1**
  - **Pricing:** $200-$275 per review
  - **SLA:** 48-72 hours
  - **Specialty:** creative services; Creative-Operator archetype
  - **Contact:** [via Drive]

- **Reviewer Slot B2**
  - **Pricing:** $175-$250 per review
  - **SLA:** 72 hours
  - **Specialty:** B2B offers; systems and platforms; Systems-Operator archetype
  - **Contact:** [via Drive]

### Tier C — RISER Nation Alumni Reviewers

Alumni who have completed Stage 2+ of the Academy and offer paid review to Stage 1 peers. Often the best value — they know the methodology cold and price accordingly.

- **Reviewer Slot C1-C5** — rotating list, currently 5 alumni reviewers available
  - **Pricing:** $150-$200 per review
  - **SLA:** 48-72 hours
  - **Specialty:** matches the alumni's own operator archetype; check Drive list for match
  - **Contact:** [via Drive; alumni reviewers coordinate through `#alumni-review-pool` Circle.so channel]

---

## How To Engage a Paid Reviewer

1. **Check the Drive version of this list** for current names, contact info, and availability status. Names are not in this template to avoid stale information when reviewers rotate.

2. **Match reviewer to your archetype.** A Teacher-Operator reviewing a Service-Operator's offer will sometimes give advice that is methodology-correct but archetype-mismatched. Tier A reviewers are generalists; Tier B and C reviewers are archetype-specialized.

3. **Send your M4.7 draft and Trigger Bank Provenance Log.** Use the C4 Peer Review Template as the deliverable format. Specify upfront that the review output should use the template — do not accept a free-form review.

4. **Specify the methodology baseline.** In your engagement message, include this line:
   > "This review is for a RISER Nation C4 Offer Ignition M4.7 landing page. The offer follows Hormozi-adjacent mechanism-based structure, and explicitly includes a specific Anti-Promise Statement (per Hopkins 1923 / Hormozi 2021) and a guarantee structure with the Honesty Clause signed. Please review for quality within the methodology rather than suggesting removal of these elements."

5. **Log the engagement** in your Revision Log per the Alternate Protocol instructions.

---

## What NOT to Use

**Do not use:**

- General copywriting review services not on this list (quality varies widely; many default to removing anti-promises, which is the specific thing C4 is trying to preserve)
- Fiverr-tier copy review (signal-to-noise too low for C4 work)
- AI-only review tools as a substitute for human review (acceptable as a supplement, not as the required review)
- Review from an unlisted paid reviewer *and* count it as your second required review (list-approved reviewers are the only paid reviews that satisfy Protocol C)

---

## If a Reviewer Gives Methodology-Conflicting Advice

If a paid reviewer recommends:
- Removing the anti-promise section
- Stacking guarantees beyond the clean structure M4.6 specifies
- Replacing verbatim Trigger Bank quotes with "cleaner" paraphrases
- Repositioning the offer in a way that drifts from your C3 Primary mechanism

...treat the feedback as methodology-conflicting. Do not incorporate without first consulting your RISER mentor or the `#methodology-questions` Circle.so channel. Methodology-conflicting advice from a paid reviewer often reflects their own training in non-anti-promise direct-response (common in the 2010s ecosystem) and is not wrong in their original context — it is just not aligned with C3/C4's specific synthesis.

---

## Removing a Reviewer from the List

Reviewers are removed from this list when any of the following occurs:

- 3+ reviewees report methodology-conflicting advice that was materially disruptive
- SLA missed on 20%+ of engagements over a quarter
- Reviewer Affiliate Agreement violation (e.g., upselling reviewees into their own offers during review time)
- Reviewer leaves the direct-response market or does not re-sign quarterly Affiliate Agreement

The list is updated quarterly. Removed reviewers receive 30 days' notice and are not blacklisted from re-entry if conditions change.

---

*Last updated: April 24, 2026 · Version 2.0 · Q2 2026 reviewer list current · Referenced by C4-Peer-Review-Alternate-Protocol*

# Supabase Schema for C4 Offer Ignition

**Purpose:** Full SQL schema (DDL) for tables C4 reads or writes.
**Audience:** Operator / developer deploying or auditing Build 1.
**Related:** `04_Tools-and-Infrastructure/RISER-Build-References-for-C4.md`

---

## Schema File (c4_schema.sql)

```sql
-- ============================================================================
-- C4 Offer Ignition — Supabase Schema v2.0
-- Last updated: 2026-04-24
-- Depends on: c1_schema.sql, c2_schema.sql, c3_schema.sql
-- ============================================================================

-- ============================================================================
-- Table: c4_offer_distinctions (M4.1)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_offer_distinctions (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  distinction_memo_drive_file_id TEXT NOT NULL,
  component_inventory_drive_file_id TEXT NOT NULL,
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7) STORED,
  c3_market_fit_hypothesis_id UUID REFERENCES public.c3_market_fit_hypotheses(id),
  c3_primary_mechanism_name TEXT NOT NULL,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id, distinction_memo_drive_file_id)
);

CREATE INDEX idx_c4_offer_distinctions_user ON public.c4_offer_distinctions(user_id);

ALTER TABLE public.c4_offer_distinctions ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own distinction memos" ON public.c4_offer_distinctions
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own distinction memos" ON public.c4_offer_distinctions
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own distinction memos" ON public.c4_offer_distinctions
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_value_equations (M4.2)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_value_equations (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  worksheet_drive_file_id TEXT NOT NULL,
  dream_outcome_strength TEXT CHECK (dream_outcome_strength IN ('Strong', 'Moderate', 'Weak')),
  perceived_likelihood_strength TEXT CHECK (perceived_likelihood_strength IN ('Strong', 'Moderate', 'Weak')),
  time_delay_strength TEXT CHECK (time_delay_strength IN ('Strong', 'Moderate', 'Weak')),
  effort_sacrifice_strength TEXT CHECK (effort_sacrifice_strength IN ('Strong', 'Moderate', 'Weak')),
  strongest_variable TEXT NOT NULL CHECK (strongest_variable IN ('Dream Outcome','Perceived Likelihood','Time Delay','Effort & Sacrifice')),
  weakest_variable TEXT NOT NULL CHECK (weakest_variable IN ('Dream Outcome','Perceived Likelihood','Time Delay','Effort & Sacrifice')),
  trigger_bank_citations_count INT NOT NULL CHECK (trigger_bank_citations_count >= 3),
  interview_citations_count INT NOT NULL CHECK (interview_citations_count >= 1),
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_value_equations_user ON public.c4_value_equations(user_id);

ALTER TABLE public.c4_value_equations ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own value equations" ON public.c4_value_equations
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own value equations" ON public.c4_value_equations
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own value equations" ON public.c4_value_equations
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_offer_decompositions (M4.3)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_offer_decompositions (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  decomposition_drive_file_id TEXT NOT NULL,
  variants_drive_file_id TEXT NOT NULL,
  decomposed_deliverables_count INT NOT NULL CHECK (decomposed_deliverables_count BETWEEN 6 AND 10),
  variant_a_name TEXT NOT NULL,
  variant_a_engagement_model TEXT NOT NULL CHECK (variant_a_engagement_model IN ('Cohort','1:1','Self-paced','Hybrid')),
  variant_a_duration_weeks INT NOT NULL,
  variant_a_deliverable_count INT NOT NULL CHECK (variant_a_deliverable_count <= 8),
  variant_a_price_band_low INT,
  variant_a_price_band_high INT,
  variant_b_name TEXT NOT NULL,
  variant_b_engagement_model TEXT NOT NULL CHECK (variant_b_engagement_model IN ('Cohort','1:1','Self-paced','Hybrid')),
  variant_b_duration_weeks INT NOT NULL,
  variant_b_deliverable_count INT NOT NULL CHECK (variant_b_deliverable_count <= 8),
  variant_b_price_band_low INT,
  variant_b_price_band_high INT,
  variant_c_name TEXT NOT NULL,
  variant_c_engagement_model TEXT NOT NULL CHECK (variant_c_engagement_model IN ('Cohort','1:1','Self-paced','Hybrid')),
  variant_c_duration_weeks INT NOT NULL,
  variant_c_deliverable_count INT NOT NULL CHECK (variant_c_deliverable_count <= 8),
  variant_c_price_band_low INT,
  variant_c_price_band_high INT,
  structural_verification_passed BOOLEAN NOT NULL,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

-- Enforce axis divergence via constraint: at least one of (engagement model, duration, deliverable count) differs pairwise
-- (This is a soft check; deeper divergence check lives in offer-decomposition-reviewer prompt)
ALTER TABLE public.c4_offer_decompositions ADD CONSTRAINT c4_od_ab_divergence
  CHECK (
    variant_a_engagement_model <> variant_b_engagement_model OR
    variant_a_duration_weeks <> variant_b_duration_weeks OR
    variant_a_deliverable_count <> variant_b_deliverable_count
  );
ALTER TABLE public.c4_offer_decompositions ADD CONSTRAINT c4_od_ac_divergence
  CHECK (
    variant_a_engagement_model <> variant_c_engagement_model OR
    variant_a_duration_weeks <> variant_c_duration_weeks OR
    variant_a_deliverable_count <> variant_c_deliverable_count
  );
ALTER TABLE public.c4_offer_decompositions ADD CONSTRAINT c4_od_bc_divergence
  CHECK (
    variant_b_engagement_model <> variant_c_engagement_model OR
    variant_b_duration_weeks <> variant_c_duration_weeks OR
    variant_b_deliverable_count <> variant_c_deliverable_count
  );

CREATE INDEX idx_c4_offer_decompositions_user ON public.c4_offer_decompositions(user_id);

ALTER TABLE public.c4_offer_decompositions ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own decompositions" ON public.c4_offer_decompositions
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own decompositions" ON public.c4_offer_decompositions
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own decompositions" ON public.c4_offer_decompositions
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_pricing_decisions (M4.4)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_pricing_decisions (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  pricing_decision_drive_file_id TEXT NOT NULL,
  observed_band_floor INT NOT NULL,
  observed_band_median INT NOT NULL,
  observed_band_ceiling INT NOT NULL,
  anchor_price INT NOT NULL CHECK (anchor_price > 0),
  pricing_strategy TEXT NOT NULL CHECK (pricing_strategy IN ('Median','Above Market','Below Market (Volume)','Other')),
  pay_in_full_price INT NOT NULL,
  installment_option TEXT,
  deposit_option TEXT,
  unit_economics_hours_per_buyer NUMERIC,
  unit_economics_effective_hourly_rate NUMERIC,
  deviation_from_band_rationale TEXT,
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_pricing_decisions_user ON public.c4_pricing_decisions(user_id);

ALTER TABLE public.c4_pricing_decisions ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own pricing" ON public.c4_pricing_decisions
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own pricing" ON public.c4_pricing_decisions
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own pricing" ON public.c4_pricing_decisions
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_anti_promises (M4.5)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_anti_promises (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  anti_promise_drive_file_id TEXT NOT NULL,
  integrity_statement_drive_file_id TEXT NOT NULL,
  integrity_statement_signed BOOLEAN NOT NULL DEFAULT FALSE,
  audience_exclusions_count INT NOT NULL CHECK (audience_exclusions_count BETWEEN 3 AND 6),
  outcome_non_claims_count INT NOT NULL CHECK (outcome_non_claims_count >= 2),
  scope_boundaries_count INT NOT NULL CHECK (scope_boundaries_count >= 2),
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7 AND integrity_statement_signed) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_anti_promises_user ON public.c4_anti_promises(user_id);

ALTER TABLE public.c4_anti_promises ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own anti-promises" ON public.c4_anti_promises
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own anti-promises" ON public.c4_anti_promises
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own anti-promises" ON public.c4_anti_promises
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_guarantees (M4.6)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_guarantees (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  guarantee_drive_file_id TEXT NOT NULL,
  honesty_clause_drive_file_id TEXT NOT NULL,
  honesty_clause_signed BOOLEAN NOT NULL DEFAULT FALSE,
  guarantee_type TEXT NOT NULL CHECK (guarantee_type IN ('Refund','Outcome','Hybrid','Time-shift','Effort-adjusted')),
  guarantee_component_count INT NOT NULL CHECK (guarantee_component_count <= 2),
  targets_weakness TEXT NOT NULL CHECK (targets_weakness IN ('Perceived Likelihood','Time Delay','Effort & Sacrifice')),
  expected_activation_rate_pct NUMERIC,
  unit_economics_sustainable BOOLEAN NOT NULL,
  ai_rubric_score INT NOT NULL CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (ai_rubric_score >= 7 AND honesty_clause_signed) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_guarantees_user ON public.c4_guarantees(user_id);

ALTER TABLE public.c4_guarantees ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own guarantees" ON public.c4_guarantees
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own guarantees" ON public.c4_guarantees
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own guarantees" ON public.c4_guarantees
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_landing_page_copies (M4.7)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_landing_page_copies (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  landing_page_drive_file_id TEXT NOT NULL,
  provenance_log_drive_file_id TEXT NOT NULL,
  revision_log_drive_file_id TEXT,
  total_word_count INT NOT NULL CHECK (total_word_count BETWEEN 1000 AND 5000),
  trigger_bank_entries_claimed INT NOT NULL CHECK (trigger_bank_entries_claimed >= 15),
  trigger_bank_entries_verified_verbatim INT NOT NULL,
  peer_review_1_reviewer_id UUID REFERENCES public.users(id),
  peer_review_1_completed_at TIMESTAMPTZ,
  peer_review_2_reviewer_id UUID REFERENCES public.users(id),
  peer_review_2_completed_at TIMESTAMPTZ,
  peer_reviews_complete BOOLEAN GENERATED ALWAYS AS (peer_review_1_completed_at IS NOT NULL AND peer_review_2_completed_at IS NOT NULL) STORED,
  ai_rubric_score INT CHECK (ai_rubric_score BETWEEN 0 AND 10),
  passed BOOLEAN GENERATED ALWAYS AS (
    ai_rubric_score >= 7 AND
    peer_review_1_completed_at IS NOT NULL AND
    peer_review_2_completed_at IS NOT NULL AND
    trigger_bank_entries_verified_verbatim >= 15
  ) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_landing_page_copies_user ON public.c4_landing_page_copies(user_id);

ALTER TABLE public.c4_landing_page_copies ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own landing pages" ON public.c4_landing_page_copies
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own landing pages" ON public.c4_landing_page_copies
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own landing pages" ON public.c4_landing_page_copies
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_offer_readiness_docs (M4.8 — course completion artifact)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_offer_readiness_docs (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  readiness_doc_drive_file_id TEXT NOT NULL,
  first_sale_readiness_checklist_drive_file_id TEXT NOT NULL,
  selected_variant TEXT NOT NULL CHECK (selected_variant IN ('A','B','C')),
  final_offer_name TEXT NOT NULL,
  final_anchor_price INT NOT NULL,
  signature_signed BOOLEAN NOT NULL DEFAULT FALSE,
  opus_validator_verdict TEXT CHECK (opus_validator_verdict IN ('PASS','NEEDS_REVISION','FAIL')),
  opus_validator_run_at TIMESTAMPTZ,
  kill_criteria_count INT NOT NULL CHECK (kill_criteria_count >= 3),
  passed BOOLEAN GENERATED ALWAYS AS (
    opus_validator_verdict = 'PASS' AND
    signature_signed
  ) STORED,
  filed_at TIMESTAMPTZ DEFAULT NOW(),
  UNIQUE(user_id)
);

CREATE INDEX idx_c4_offer_readiness_docs_user ON public.c4_offer_readiness_docs(user_id);

ALTER TABLE public.c4_offer_readiness_docs ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own readiness docs" ON public.c4_offer_readiness_docs
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Users insert own readiness docs" ON public.c4_offer_readiness_docs
  FOR INSERT WITH CHECK (auth.uid() = user_id);
CREATE POLICY "Users update own readiness docs" ON public.c4_offer_readiness_docs
  FOR UPDATE USING (auth.uid() = user_id);


-- ============================================================================
-- Table: c4_review_log (audit trail for all review prompt calls)
-- ============================================================================
CREATE TABLE IF NOT EXISTS public.c4_review_log (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  user_id UUID NOT NULL REFERENCES public.users(id) ON DELETE CASCADE,
  module TEXT NOT NULL CHECK (module IN ('M4.1','M4.2','M4.3','M4.4','M4.5','M4.6','M4.7','M4.8')),
  prompt_name TEXT NOT NULL,
  prompt_version TEXT NOT NULL,
  submission_count INT NOT NULL DEFAULT 1,
  verdict TEXT NOT NULL CHECK (verdict IN ('PASS','FAIL','NEEDS_REVISION')),
  score INT,
  feedback_json JSONB,
  flags_json JSONB,
  ran_at TIMESTAMPTZ DEFAULT NOW()
);

CREATE INDEX idx_c4_review_log_user_module ON public.c4_review_log(user_id, module);

ALTER TABLE public.c4_review_log ENABLE ROW LEVEL SECURITY;

CREATE POLICY "Users see own review log" ON public.c4_review_log
  FOR SELECT USING (auth.uid() = user_id);
CREATE POLICY "Service inserts review log" ON public.c4_review_log
  FOR INSERT WITH CHECK (TRUE); -- service role only; Build 6 writes


-- ============================================================================
-- Column addition: users table
-- ============================================================================
ALTER TABLE public.users
  ADD COLUMN IF NOT EXISTS c4_complete BOOLEAN DEFAULT FALSE,
  ADD COLUMN IF NOT EXISTS c4_completed_at TIMESTAMPTZ,
  ADD COLUMN IF NOT EXISTS c4_lead_variant TEXT,
  ADD COLUMN IF NOT EXISTS c4_final_offer_name TEXT,
  ADD COLUMN IF NOT EXISTS c4_final_anchor_price INT;


-- ============================================================================
-- Function: check_c4_enrollment_eligible(user_id)
-- ============================================================================
CREATE OR REPLACE FUNCTION public.check_c4_enrollment_eligible(p_user_id UUID)
RETURNS JSONB AS $$
DECLARE
  v_missing TEXT[] := ARRAY[]::TEXT[];
  v_user RECORD;
BEGIN
  SELECT c1_complete, c2_complete, c3_complete, captains_oath_signed_at, operator_identity_filed_at
    INTO v_user FROM public.users WHERE id = p_user_id;

  IF NOT COALESCE(v_user.c3_complete, FALSE) THEN
    v_missing := array_append(v_missing, 'c3_complete');
  END IF;

  IF NOT EXISTS (
    SELECT 1 FROM public.c3_market_fit_hypotheses
    WHERE user_id = p_user_id
      AND filed_at > (NOW() - INTERVAL '3 months')
  ) THEN
    v_missing := array_append(v_missing, 'c3_market_fit_hypothesis_within_3_months');
  END IF;

  IF NOT EXISTS (
    SELECT 1 FROM public.c3_trigger_banks
    WHERE user_id = p_user_id AND total_entries >= 200
  ) THEN
    v_missing := array_append(v_missing, 'c3_trigger_bank_200_plus');
  END IF;

  IF NOT EXISTS (
    SELECT 1 FROM public.c3_pricing_signals
    WHERE user_id = p_user_id
  ) THEN
    v_missing := array_append(v_missing, 'c3_pricing_signals');
  END IF;

  IF v_user.captains_oath_signed_at IS NULL OR v_user.captains_oath_signed_at < (NOW() - INTERVAL '12 months') THEN
    v_missing := array_append(v_missing, 'captains_oath_signed_within_12_months');
  END IF;

  RETURN jsonb_build_object(
    'eligible', array_length(v_missing, 1) IS NULL,
    'missing', v_missing
  );
END;
$$ LANGUAGE plpgsql SECURITY DEFINER;


-- ============================================================================
-- Function: check_c4_completion(user_id)
-- ============================================================================
CREATE OR REPLACE FUNCTION public.check_c4_completion(p_user_id UUID)
RETURNS JSONB AS $$
DECLARE
  v_missing TEXT[] := ARRAY[]::TEXT[];
BEGIN
  IF NOT EXISTS (SELECT 1 FROM public.c4_offer_distinctions WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_1_distinction_passed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_value_equations WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_2_value_equation_passed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_offer_decompositions WHERE user_id = p_user_id AND structural_verification_passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_3_decomposition_verified');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_pricing_decisions WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_4_pricing_passed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_anti_promises WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_5_anti_promise_passed_and_signed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_guarantees WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_6_guarantee_passed_and_signed');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_landing_page_copies WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_7_landing_page_passed_with_peer_reviews');
  END IF;
  IF NOT EXISTS (SELECT 1 FROM public.c4_offer_readiness_docs WHERE user_id = p_user_id AND passed = TRUE) THEN
    v_missing := array_append(v_missing, 'm4_8_readiness_doc_opus_passed');
  END IF;

  RETURN jsonb_build_object(
    'complete', array_length(v_missing, 1) IS NULL,
    'missing', v_missing
  );
END;
$$ LANGUAGE plpgsql SECURITY DEFINER;


-- ============================================================================
-- Trigger: mark c4_complete = true when all 8 artifacts pass
-- ============================================================================
CREATE OR REPLACE FUNCTION public.update_c4_complete_flag()
RETURNS TRIGGER AS $$
DECLARE
  v_check JSONB;
  v_readiness RECORD;
BEGIN
  v_check := public.check_c4_completion(NEW.user_id);
  IF (v_check->>'complete')::BOOLEAN = TRUE THEN
    SELECT selected_variant, final_offer_name, final_anchor_price
      INTO v_readiness
      FROM public.c4_offer_readiness_docs
      WHERE user_id = NEW.user_id AND passed = TRUE
      LIMIT 1;
    UPDATE public.users
      SET c4_complete = TRUE,
          c4_completed_at = NOW(),
          c4_lead_variant = v_readiness.selected_variant,
          c4_final_offer_name = v_readiness.final_offer_name,
          c4_final_anchor_price = v_readiness.final_anchor_price
      WHERE id = NEW.user_id;
  END IF;
  RETURN NEW;
END;
$$ LANGUAGE plpgsql;

CREATE TRIGGER tr_c4_completion_check
  AFTER INSERT OR UPDATE ON public.c4_offer_readiness_docs
  FOR EACH ROW
  WHEN (NEW.passed = TRUE)
  EXECUTE FUNCTION public.update_c4_complete_flag();
```

---

## Schema Design Notes

### Generated passed columns

Most tables use `GENERATED ALWAYS AS (...) STORED` for the `passed` column. This enforces the pass logic at the database layer rather than in application code — a landing page row with `ai_rubric_score = 8` but `peer_reviews_complete = FALSE` is automatically not-passed. Application code cannot accidentally flip the flag.

### Axis divergence constraints on c4_offer_decompositions

Database constraints catch the simplest failure mode (three variants that are structurally identical). Deeper divergence checks (e.g., "variant B and C differ on only price, which is not enough") are enforced by the offer-decomposition-reviewer prompt, not at the database layer. Database enforces the minimum; the prompt enforces the quality.

### Feature Stuffing constraints

The `CHECK (deliverable_count <= 8)` constraints on each variant prevent Feature Stuffing at the row level. A student cannot file a variant with 12 deliverables — the insert fails. This is the database-layer companion to the offer-decomposition-reviewer prompt's Feature Stuffing Flag.

### Integrity Statement / Honesty Clause enforcement

`c4_anti_promises` and `c4_guarantees` tables have `passed` generated columns that require both the rubric score and the signed statement. Unsigned submissions cannot pass, regardless of rubric score. This is structural enforcement of the Integrity Policy.

### Opus gating on c4_offer_readiness_docs

The `passed` flag requires Opus validator verdict = PASS AND signature_signed. A Sonnet-passed but Opus-pending row is stored but does not count as passed. C4 completion cannot occur without explicit Opus verdict.

---

## Migration Notes

This schema depends on `c1_schema.sql`, `c2_schema.sql`, and `c3_schema.sql` being deployed first. Run in sequence:

```bash
psql -h <host> -U <user> -d <db> -f c1_schema.sql
psql -h <host> -U <user> -d <db> -f c2_schema.sql
psql -h <host> -U <user> -d <db> -f c3_schema.sql
psql -h <host> -U <user> -d <db> -f c4_schema.sql
```

The `c4_complete` column addition on `public.users` is idempotent via `ADD COLUMN IF NOT EXISTS`.

---

## Referenced By

- `03_Scripts-and-Prompts/Prompt-Chains/C4-Review-Chain.md` — routing functions
- `00_Course-Overview/C4-Prerequisites-Checklist.md` — `check_c4_enrollment_eligible` reference
- Build 6 `src/c4_checkpoint_handler.ts` — all insert/update calls
- `06_SOPs/RISER-C4-Weekly-Rhythm-Setup-SOP.md` — operational integration

---

*Last updated: April 24, 2026 · Version 2.0*

# C4 Prompt Chain — M4.1 through M4.8 Review Orchestration

**Purpose:** Documents the sequencing of the 6 C4 Claude system prompts across module checkpoints. Referenced by Build 6 when routing student submissions to reviewers and gating module unlock.
**Filed to:** `03_Scripts-and-Prompts/Prompt-Chains/`
**Referenced by:** Build 6 checkpoint handler; `04_Tools-and-Infrastructure/Supabase-C4-Schema.md`

---

## Chain Overview

C4 uses 6 system prompts across 8 checkpoints. Five are Sonnet-powered (routine review) and one is Opus-powered (course-completion gate). The chain is serial — each module's review must issue PASS before the next module's checkpoint can receive submissions.

```mermaid
graph TD
    M41_sub[M4.1 submission] --> P1[offer-distinction-reviewer<br/>Sonnet 4.6]
    P1 -->|PASS >=7/10| M42_sub[M4.2 unlocks]
    P1 -->|FAIL <7/10| M41_rev[M4.1 revision]
    M41_rev --> P1

    M42_sub --> P2[value-equation-application-reviewer<br/>Sonnet 4.6]
    P2 -->|PASS >=7/10| M43_sub[M4.3 unlocks]
    P2 -->|FAIL| M42_rev[M4.2 revision]

    M43_sub --> P3[offer-decomposition-reviewer<br/>Sonnet 4.6<br/>Structural only]
    P3 -->|PASS| M44[M4.4 unlocks]
    P3 -->|NEEDS_REVISION| M43_rev[M4.3 revision]

    M44 --> M44_review[M4.4 reviewed by<br/>offer-readiness-reviewer spot-check]
    M44_review -->|PASS| M45[M4.5 unlocks]

    M45 --> M45_review[M4.5 reviewed by<br/>offer-readiness-reviewer spot-check]
    M45_review -->|PASS| M46[M4.6 unlocks]

    M46 --> M46_review[M4.6 reviewed by<br/>offer-readiness-reviewer spot-check]
    M46_review -->|PASS| M47_sub[M4.7 unlocks]

    M47_sub --> PEER[2 peer reviews<br/>SLA 72hr]
    PEER --> P4[landing-page-copy-reviewer<br/>Sonnet 4.6]
    P4 -->|PASS >=7/10 AND peer count >=2| M48_sub[M4.8 unlocks]
    P4 -->|FAIL| M47_rev[M4.7 revision]

    M48_sub --> P5[offer-readiness-reviewer<br/>Sonnet 4.6<br/>Structural pre-screen]
    P5 -->|PASS| P6[offer-fit-validator<br/>OPUS 4.7<br/>Full coherence check]
    P5 -->|NEEDS_REVISION| M48_rev[M4.8 revision]

    P6 -->|PASS| COMPLETE([C4 Complete<br/>C5 Unlocks])
    P6 -->|NEEDS_REVISION| M48_rev
    P6 -->|FAIL| MENTOR[Mentor diagnosis<br/>Likely C3 M3.7 issue]

    style P6 fill:#B45F06,color:#fff
    style COMPLETE fill:#2E75B6,color:#fff
    style MENTOR fill:#CC0000,color:#fff
    style PEER fill:#BF9000,color:#fff
```

---

## Prompt Inventory

| # | Prompt File | Model | Called At | Cost per call | Typical volume |
|---|---|---|---|---|---|
| 1 | offer-distinction-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.1 checkpoint | $0.04-0.08 | 1-2 per student |
| 2 | value-equation-application-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.2 checkpoint | $0.04-0.08 | 1-2 per student |
| 3 | offer-decomposition-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.3 checkpoint | $0.04-0.08 | 1-2 per student |
| 4 | landing-page-copy-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.7 checkpoint (after peer review) | $0.06-0.12 | 1-2 per student |
| 5 | offer-readiness-reviewer-v1.0.0.yaml | Sonnet 4.6 | M4.4, M4.5, M4.6 spot-check + M4.8 pre-screen | $0.04-0.08 | 3-5 per student |
| 6 | offer-fit-validator-v1.0.0.yaml | **Opus 4.7** | M4.8 course-completion | **$0.30-0.55** | 1-2 per student |

**Total C4 review cost per student:** $0.80-$1.50 across the chain (most students complete in 1-2 submissions per module).

---

## Orchestration Rules

### Serial Dependency Enforcement

Module unlock only occurs when the prior module's review has returned PASS. A student cannot submit M4.3 until M4.2 has PASSED. This prevents coherence collapse — a student with a miscalibrated Value Equation should not be producing decomposition variants targeted at the wrong weakness.

### Revision Loop

For each module:
- First submission → review → PASS or revision guidance
- Second submission (after revision) → review → PASS or mentor escalation
- Third submission → mentor routing (rare; indicates fundamental issue with prior module outputs)

Build 6 tracks submission count per module; the third attempt auto-routes to mentor queue.

### Peer Review Layer (M4.7 only)

M4.7 is the only module requiring peer review before AI review. The order:

1. Student submits draft to `#c4-offer-ignition`
2. Two peer reviewers complete reviews (SLA 72 hours)
3. Student incorporates peer feedback, produces Revision Log
4. Revised submission routes to landing-page-copy-reviewer (Sonnet)
5. AI reviewer verifies: peer review count ≥ 2, integrity of incorporation, and rubric score

If peer review SLA is missed (cohort thin), Protocol A/B/C from `02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md` applies.

### The Opus Gate (M4.8 only)

M4.8 is the only module routing through two reviewers:

1. **offer-readiness-reviewer (Sonnet)** performs structural pre-screen
2. If Sonnet issues PASS → **offer-fit-validator (Opus 4.7)** performs full coherence check
3. If Sonnet issues FAIL → student revises before Opus is spun up (Opus is ~5-10x the cost of Sonnet; structural pre-screen prevents wasted Opus calls)

The Opus validator's PASS verdict unlocks C5 First Currents enrollment.

### Cross-Reference to Prior Course Outputs

Every prompt in C4 receives the relevant C1-C3 artifacts as input context. This prevents validators from accepting work that has silently drifted from the student's prior commitments:

- **C1 Captain's Oath Clause 1 (territory)** — fed to offer-distinction-reviewer, offer-fit-validator
- **C1 Operator Identity** — fed to offer-fit-validator (archetype consistency)
- **C2 Mechanism Hypothesis Document** — fed to offer-distinction-reviewer (mechanism name anchor)
- **C3 Market Fit Hypothesis** — fed to every C4 reviewer
- **C3 Trigger Bank** — fed to value-equation-application-reviewer, landing-page-copy-reviewer, offer-fit-validator
- **C3 Pricing Signals** — fed to offer-fit-validator
- **C3 Customer Interview Library (summaries)** — fed to value-equation-application-reviewer, offer-fit-validator

Without this context, each reviewer would be scoring the submission against itself rather than against the student's prior work. Cross-reference is what keeps the chain coherent.

---

## Build 6 Integration

Build 6 handles chain orchestration via the following SQL functions (full definitions in `04_Tools-and-Infrastructure/Supabase-C4-Schema.md`):

- `check_c4_enrollment_eligible(user_id)` — prerequisite check at enrollment
- `route_c4_submission(user_id, module, artifact_blob)` — routes to correct reviewer; passes C1-C3 context
- `log_c4_review_result(user_id, module, verdict, feedback)` — writes to `c4_review_log` table
- `unlock_next_c4_module(user_id, current_module)` — gated by prior module PASS
- `check_c4_completion(user_id)` — verifies all 8 artifacts present with PASS status
- `route_c4_to_c5(user_id)` — on course complete, opens C5 enrollment

---

## Failure Mode Routing

| Failure Pattern | Triggered By | Routed To |
|---|---|---|
| Mechanism drift from C3 | offer-fit-validator Check 2.3 BLOCKING | Mentor queue; reopen C3 M3.7 |
| Fabricated Trigger Bank entries | offer-fit-validator Check 2.4 BLOCKING | Integrity review queue |
| Anti-promise softening | offer-fit-validator Check 1.3 WARNING | Revision guidance; student reverts |
| Feature Stuffing (deliverable count, guarantee stack) | Check 4.1, 4.2 WARNING | Revision guidance |
| Silent weakness whitewash | Check 3.1 WARNING | Revision guidance |
| Signature not signed | Check 5.1 BLOCKING | 30-second fix + resubmit |
| Value Equation universal strength | value-equation-application-reviewer Dimension 3 | Revision with honest weakness identification |
| Three variants without axis divergence | offer-decomposition-reviewer Check 2 | Genuine variant diversification required |

---

## Versioning

All prompts are versioned following semver (v1.0.0). Changes to rubric criteria trigger a minor version bump; changes to scoring thresholds trigger a patch bump. Quarterly review cadence is owned by the curriculum-quality team.

When a prompt version changes, Build 6 continues routing existing in-progress submissions to the prior version until the student clears that checkpoint; new submissions after the version bump route to the new version. This prevents mid-revision rubric changes from surprising students.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by Build 6*

Budget active work, revision time and review delays separately

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Build a realistic calendar for the source's offer-construction work. Separate module activity, implementation, elapsed cooling periods and peer-review latency. Compare four- and five-week schedules, recognize escalation signals, and adapt the plan to actual capacity and accessibility needs. The source uses legacy C4 and C1–C3 labels; the current spreadsheet still controls course assignments.

Start with the top-line estimates and check their arithmetic

The source targets forty active hours over four to five weeks, averaging eight to ten hours per week. Its longest module is the landing-page copy activity at four hours, plus a peer-review cycle. It calls offer architecture the shortest module at seventy-five minutes, although the anti-promise module also has seventy-five minutes. Keep that tie visible.

The module total is 930 minutes, or fifteen and a half hours. These are proposed learning estimates, not measured time already spent on this project and not a guarantee of how quickly a learner will finish.

Add all nine implementation activities

The source budgets one to two hours to reread the Market Fit Hypothesis and Trigger Bank; two to three hours to revise the three offer variants after cooling; three to five hours for landing-page revision; two to three hours to review two peers' pages; and one to three hours to incorporate two reviews of the learner's own page.

It then adds one hour to revise the anti-promise after the guarantee decision; one to two hours for pricing and unit-economics checks; two to three hours for the readiness document's draft and revision; and one to two hours for community discussion and reflection.

The source summarizes these as fifteen to twenty-four hours. Adding the individual minima gives fourteen, while the maxima give twenty-four. Combined with the module time, the arithmetic is twenty-nine and a half to thirty-nine and a half hours, approximately the source's thirty-to-forty-hour range and forty-hour target. Check that readiness drafting and other activities are not counted twice in your own calendar; the document distinguishes implementation outside the module sessions, but actual work logs must establish that boundary.

The source compares this with forty-five hours for its prior C3 course and says internal writing avoids external scheduling. Treat that as its planning context, not a universal rule: peer review is still an external dependency. A learner taking longer may need a clearer task, support or accommodation; time alone does not establish unwillingness to revise.

Compare the four-week and five-week plans

In the aggressive four-week plan, week one completes the distinction memo and Value Equation worksheet. Week two completes three variants and pricing. Week three completes the anti-promise and guarantee, including the Honesty Clause. Week four combines the landing-page draft, peer reviews and revision with the readiness document. This compressed plan depends on reviewers responding in time and enough working hours being available.

In the default five-week plan, week one again covers the first two artifacts. Week two drafts and revises three variants with cooling time. Week three handles pricing and the anti-promise. Week four completes the guarantee and sends the initial landing-page draft to peers. Week five incorporates feedback and completes the readiness document. The additional week provides room for revision and review latency, not an assurance that every dependency will resolve.

Record each major deliverable and its review dependency. An authored scheduling practice is to reserve the actual reviewer availability before promising a final date, then update the plan when evidence changes rather than hiding a delay.

Treat the 85-minute rhythm as part of the work plan

The source's Monday block is ten minutes: open the folder, review what is due, reread a prior draft and note one or two revisions. Tuesday has fifteen minutes for a new section, revision or assigned peer feedback. Wednesday provides a thirty-minute drafting block for variants, copy or readiness. Thursday has twenty minutes to revise, cut weak sentences and check buyer-language quotations. Friday has ten minutes for a reflection about difficulty and surprises.

These blocks total eighty-five minutes per week. The source explicitly says longer writing and peer-review sessions are additional. Over five weeks, the rhythm supplies 425 minutes—seven hours and five minutes—not the whole forty-hour course. That clarification resolves the misleading impression in some linked legacy maps that the rhythm alone could complete all scheduled work. Determine whether each block belongs inside your forty-hour budget before adding it again.

The source asks for verbatim Trigger Bank entries rather than paraphrases. Preserve exact quotations in an appropriately restricted evidence bank, with attribution and permissions as needed. Do not invent buyer quotations or disclose private research to meet a writing checklist.

Separate cooling time from active time

The source proposes a forty-eight-hour gap between first and second drafts of M4.3, M4.5, M4.7 and M4.8. Waiting does not itself consume working hours, but it does affect the earliest possible completion date. Other compatible tasks can occur during a cooling period if the dependencies allow them.

The source claims same-day revision could reduce elapsed time to three weeks but produce weaker work visible at the later readiness test. It supplies no comparison data establishing that outcome for every learner. Teach the cooling period as a proposed revision practice: return with fresh attention, look for unsupported claims and weak wording, and record whether the second pass improves the artifact. Retain its four-to-five-week planning recommendation without presenting it as a scientifically fixed duration.

Respond to all four six-week warning scenarios

First, rewriting the mechanism while assembling variants may signal an unresolved earlier choice. The source proposes pausing offer work and returning to C3 M3.5–M3.7 with a mentor. Check the actual cause instead of assuming the earlier decision was careless.

Second, six or more landing-page drafts may suggest perfectionism or feature stuffing. Review the specific offer weakness and the referenced failure case rather than continuing cosmetic revisions. Third, missing peer reviews may indicate a thin cohort or stalled reviewers; the source proposes Protocol A mentor substitution. That protocol and actual mentor availability must be established separately.

Fourth, difficulty writing the anti-promise may justify a thirty-minute conversation about truthful fit and scope boundaries. The source attributes conversion benefits to Hopkins and Hormozi, but this document supplies no supporting passages or results. Do not promise that exclusions always increase conversion. The source also proposes automatic mentor escalation after seven weeks without completion; that is a design rule, not a verified live automation.

Adjust attention to the operator's actual needs

The source suggests a Teacher-Operator add one hour to pricing, comparing relevant cohort and service alternatives with actual pricing signals instead of assuming self-paced course benchmarks of $197–$497 apply to cohort examples of $1,500–$10,000. Those numbers remain illustrative source comparisons, not current market prices.

It suggests a Builder-Operator add two hours to landing-page copy, converting feature descriptions into evidenced buyer outcomes. It suggests a Service-Operator add one hour to the anti-promise, discussing three categories of poor fit with a peer. The Product, Creative and Systems estimates are unchanged in this time-estimate document, while it points to a separate archetype chart for further adjustments. That chart includes additional advice, so preserve the difference between this summary and the fuller reference rather than silently erasing either.

The category descriptions are tendencies to inspect, not diagnoses. An authored Brunson/ClickFunnels application is to reserve time for a clear hook, truthful story and coherent offer. An authored Hormozi/Acquisition.com application is to reserve time to test the outcome, evidence, delay, effort and delivery economics. Neither educational theme requires a learner to fit a fixed personality category.

Preserve accommodation requests without inventing a service promise

The source lists [email protected] as a pre-enrollment contact with a forty-eight-hour response target. This is a legacy address on a different domain from the requested www.risernationcorp.com; its operation and current service commitment have not been verified. Preserve the [legacy accommodation contact](mailto:[email protected]) as a source reference awaiting confirmation, not as a promise that RISER currently monitors it.

The described options are an extended timeline up to ten weeks, asynchronous voice or written peer review in place of synchronous review, dyslexia-friendly copy review by a mentor, and a scholarship for paid review under Protocol C when needed because the cohort is thin. These are proposed source provisions. Confirm available support and eligibility before offering them to a learner; no email, scholarship or paid review is activated by this lesson.

Produce the calendar and review it

For practice, choose the four- or five-week plan and enter module work, implementation, cooling and review dates separately. Add time only where the actual task requires it, identify who owns each dependency, and show the response when a review arrives late. Keep the original time tables and every applicable source link with the lesson. A usable schedule explains its assumptions and changes when they fail; it does not turn a source estimate into a deadline guarantee.

Clickable assigned source

- C4 Offer Ignition — Time Estimate

The complete source text and its original module, implementation and weekly tables remain in the lesson appendix, including the arithmetic discrepancies and legacy support details.

Linked resource workshop: prepare, request, deliver and reconcile a peer review

The six linked documents supply the practical peer-review material referenced by the offer-course plans. They are legacy templates and operating proposals, not evidence of a currently staffed RISER service. Read them together: the preparation checklist establishes inputs, outreach scripts coordinate people, the review template structures feedback, the SOP sequences work, alternate protocols address missing capacity, and the paid-review reference describes proposed selection rules. No message, booking, payment or scholarship request is sent by this workshop.

Prepare all eight checklist groups

Group A requires the named landing-page file and seven sections in order: Problem, 200–400 words; Agitation, 150–300; Solution-and-Mechanism, 300–500; Proof, 200–400; Offer, 300–500; Anti-Promise-and-Guarantee, 250–400; and CTA, 50–150. The individual ranges sum to 1,450–2,650, while the required total is 1,800–2,500. Both conditions can be satisfied, but one does not automatically imply the other. These are template targets, not proof that a page of that length will convert. Compared with the handoff's ten-element list, two pairs are grouped and urgency has no separate heading; explain relevant truthful timing without inventing scarcity.

Group B requires a named Trigger Bank Provenance Log, at least fifteen entries, exact source wording, a TB identifier or interview reference, and distribution across at least four page sections. Matching fifteen quotations is not a substitute for the full bank's evidence quality. Keep permissions, confidentiality and attribution appropriate to the destination.

Group C compares the page's exclusions with M4.5 and its guarantee with M4.6. Softening must be reverted or justified in the record; added guarantee stacking should be removed under this template's policy. Both integrity signatures are required. Group D checks the tested offer name, one visible price rather than a hidden range, payment options, engagement model, duration, cadence and no more than eight deliverables. A signature and a count are structural checks, not proof of truthfulness or viability.

Group E asks for specific named or appropriately anonymized evidence, an explicit known-weakness acknowledgment when there are fewer than four named cases, and attributed, exact testimonials. Do not invent a fourth case or disclose an identity to meet a template. Group F requires a specific action, actual enrollment or cohort timing, a qualification process if applicable, and a real pre-purchase contact. Group G requires reading the page aloud, removing phrases the operator would not say, checking unsupported hyperbole, and avoiding the source's four low-substance phrases: “game-changer,” “revolutionary,” “transform your life,” and “all you need to do is.” These are editorial preferences, not a comprehensive truthfulness test.

Group H prepares links to the page and provenance log, two or three positioning sentences, a request for two template-based reviews within seventy-two hours, and specific availability to reciprocate. The checklist's fifteen-to-twenty-minute estimate and claimed thirty-to-sixty-minute reviewer saving are unverified assumptions.

Its five common fixes are to restore softened terms; add three to six genuine missing quotations, often in problem and agitation; examine excess deliverables for unnecessary padding; show the actual price in the offer section; and use a forty-eight-hour reread to repair unnatural voice. Add only what is genuinely missing rather than assuming three extra quotes always reaches fifteen. After submission, check reviewer pickup daily, answer questions, keep the reviewed version stable and begin reciprocating. The stable-version rule prevents two reviewers evaluating different drafts.

Use the six coordination scripts as templates, not automatic messages

The request script identifies the operator, tested offer name, buyer, price and one or two suspected weaknesses. It links the page, provenance log and any existing Revision Log, proposes seventy-two hours, and states specific days for reviewing the first two reciprocal requests. Naming a focus may help, but the claim that it reliably improves feedback is not established by data here.

The acceptance script names the requester, confirms the chosen focus or full-template review, and gives a specific delivery date and time, aiming for forty-eight hours. That is shorter than the general seventy-two-hour target; state which commitment was actually made. The decline script explains capacity if useful, refers to a genuinely available person, and points to alternate review options. Do not tag someone or promise mentor capacity without knowing it exists.

The delivery script links the completed template, gives one overall observation and three recommended revisions, and offers optional asynchronous discussion. The response script addresses every recommendation as incorporated, incorporated with modification, or not incorporated with a reason, then links the Revision Log. The escalation script identifies the pacing window, requests and responses, attempted alternate routes, specific help needed, page link and revised timeline. The source routes it to a mentor channel or a welcome-email Calendly link, neither of which is supplied as a verified current contact.

The etiquette section favors reciprocity, precise observations, honest criticism and timely responses. Its example contrasts generic praise with identifying performative “wasted years” wording in a particular paragraph. Be candid and respectful; honesty does not require harshness. The source calls reciprocity a culture norm rather than enforced policy. It encourages personal voice especially in request and delivery scripts, with logistics scripts closer to their templates. Claims that personal voice correlates with better responses or missed SLAs are the largest disruption cause are source assertions, not measured findings here.

Complete the entire review template

Read the page and provenance log together, looking for buyer-language fit, quotations that support specific claims, and exclusions or guarantees weakened during copywriting. The source estimates forty-five to sixty minutes and a seventy-two-hour request-to-delivery target. Record reviewer name, reviewer archetype, date, submitting operator and offer name. The task is structural feedback, not rewriting every line.

Rate each section strong, adequate or weak. For Problem, restate the problem in one sentence, assess whether the buyer's state is vivid or generic, and whether at least one quotation is meaningful, then add one to three specific observations. For Agitation, distinguish real, mixed and performative consequences and identify any supporting numbers, timeframes or opportunity costs. Do not manufacture emotional pressure or unsupported losses.

For Solution-and-Mechanism, explain the mechanism in your own words and check whether its four referenced pillars are visible; missing pillar definitions remain a separate dependency. For Proof, distinguish specific, mixed and generic cases and check whether limited evidence is honestly acknowledged. For Offer, inspect the name, visibility of price and concrete delivery experience—what happens, when and with whom.

For Anti-Promise-and-Guarantee, rate the two parts separately. Count three or more genuine exclusions, two, or one or fewer. Identify disguised flattery such as “not for unmotivated people.” Compare one primary guarantee plus an optional complementary element with borderline or three-plus-component stacking. Consider whether stated claim conditions appear understandable and realistically usable, without treating component count as a conclusive legal or ethical judgment. For CTA, check a specific action, outcome and actual timeline. The source's February 12 enrollment and twenty-four-hour welcome-kit example is fictional illustration, not a current date or promise.

Across the whole page, sample three quotations against provenance and classify them as exact, slightly paraphrased or significantly paraphrased. Record overall strong, mixed or weak provenance, but recognize that a three-quote sample cannot verify every quotation. Assess buyer versus operator voice, then count all fifteen required entries. Give three actionable revisions—for example, shortening a particular four-sentence opening to two—rather than an abstract request to improve copy. Close with ready, moderate revision or substantial revision, a hypothetical yes/maybe/no buying reaction with reasons, and a signature. A peer's hypothetical buying reaction is not an actual purchase or validation result.

Follow the SOP's sequence, roles and timing

The SOP requires the page draft, provenance log, completed preparation checklist and a forty-eight-hour cooling period. Its seven roles are the submitting student, two peer reviewers, mentor, cross-stage reviewer, paid reviewer and proposed Build 6 coordinator. The source assigns automated notifications, matching, tracking and gates to Build 6; those operations have not been verified or deployed here.

Step one is a twenty-minute self-audit of checklist groups A–H, quotations and unchanged terms. Missing provenance, fewer than fifteen entries or softened exclusions cause rework; the source's twenty-four-to-forty-eight-hour delay estimate is illustrative. Step two is a fifteen-minute request using the structured script, both document links, suspected weaknesses, the review target and reciprocal availability. Vague requests and missing attachments should be fixed before relying on a review.

Step three allows twenty-four to forty-eight hours for pickup and requires two commitments with delivery dates. The SOP activates alternatives when fewer than two commit within forty-eight hours, whereas the separate alternate document uses seventy-two hours without response. Keep that conflict visible. Reviewers should communicate a threatened deadline instead of missing it silently.

Step five allocates thirty minutes to reading both completed reviews together before acting. Capture common themes and disagreements, then allow the SOP's suggested twelve-hour gap before revision. Two reviewers agreeing is a reason to investigate, not proof that their judgment is correct. Step six allocates sixty to ninety minutes to decisions in the Revision Log and the revised page. Record every recommendation and its disposition; do not accept all feedback mechanically or omit disagreement silently.

Step seven budgets ninety to 120 minutes for two reciprocal reviews, forty-five to sixty each, using the template and delivery script. Discuss actual capacity instead of treating an access need as bad faith. Step eight budgets five minutes to submit and five for the proposed AI run. It requires page, provenance and revision logs, a score of at least seven out of ten and no integrity flags. Its activities say review count at least two, while its quality gate says exactly two. An implementation must reconcile that difference and distinguish review credits from actual people; it must not fabricate a second reviewer when one mentor review counts as two credits.

Apply alternate routes with explicit review credit

Use alternatives when fewer than four people are active at compatible pacing, no response arrives within the stated window, or the student is ahead or behind the cohort. The alternate document proposes escalation within seventy-two hours of draft completion if no route is viable, which can conflict with longer windows below. Define the applicable clock before promising completion.

Protocol A proposes a forty-five-minute mentor call, with the draft and provenance log submitted at least twenty-four hours beforehand. A completed written template counts as both required review credits. The alternate document gives seventy-two hours typically and ninety-six worst case, at no charge; the SOP separately describes twenty-four hours from activation and delivery within seventy-two. These are conflicting source service assumptions, not verified current support. A mentor backlog of two or more weeks is the stated reason to try B.

Protocol B requests one or two volunteer Stage 2-or-higher reviewers, naming archetype, territory, offer, a ninety-six-hour target and both document links. It mentions Stage 2, 3, 4 and 5+ volunteers, no charge and reciprocal ecosystem credits. One cross-stage review may count as two credits or be paired with another review under the source policy; record the chosen interpretation. The SOP limits one description to Stages 2–5. If no one picks up within forty-eight hours, the source points to C. Experience may be useful, but it does not guarantee a superior review.

Protocol C is a direct paid engagement when A and B are unavailable in the planned week. The Academy is not described as handling payment. A paid review counts as only one credit and needs a peer, mentor or cross-stage counterpart. The source's typical price is $150–$400 and turnaround forty-eight to seventy-two hours by contract; the roster's A1 range reaches $450. Preserve that discrepancy. It also proposes that waiting three to five extra days for an unpaid route may be preferable. No paid service is recommended as currently available or purchased here.

The scholarship provision names the unverified legacy address [[email protected]](mailto:[email protected]), a specific scholarship-request subject, page link, pacing dates and attempted routes. It proposes a forty-eight-hour reply and one review covered up to $200 if approved. This is not a current verified service, funding commitment or permission to send a message. The protocol log records route, actual reviewer names, dates and one or two rationale sentences. Its shorthand for C omits a peer as the counterpart despite the prose allowing one; preserve and resolve that inconsistency.

Evaluate the paid-review reference without inventing a roster

The five proposed selection criteria are at least twenty relevant prior page reviews, familiarity with mechanism-based offers, respect for truthful exclusions, a signed methodology agreement and useful ratings from at least five reviewees. The document contains placeholder slots, not current names or contact details, so it does not establish that any provider is actually vetted or available.

Tier A describes ten-plus years of experience: A1 at $350–$450 with seventy-two hours for coaching, consulting and Teacher/Service work; A2 at $300–$400 with forty-eight to seventy-two hours for productized services and Builder work. Tier B describes five to ten years: B1 at $200–$275 with forty-eight to seventy-two hours for Creative work; B2 at $175–$250 with seventy-two hours for B2B, platforms and Systems work. Tier C describes five rotating Stage 2+ alumni slots at $150–$200 with forty-eight to seventy-two hours and archetype matching. All numbers and availability claims are historical template data, not current quotations.

Its five engagement steps are to find the actual current roster, match relevant expertise, provide the draft and provenance log with the required template, explain the methodology baseline, and log the engagement. The baseline preserves mechanism, exclusions and guarantee honesty while requesting critique within that approach. A reviewer should still flag unsupported or unsuitable commitments; methodology must not become a reason to ignore valid criticism.

The source excludes unlisted general review services, disparages low-cost marketplace reviews, rejects AI-only tools as a substitute for required human review, and disallows unlisted paid reviewers for credit. Preserve these as program-policy proposals. Blanket claims about a marketplace's quality are unsupported; assess the actual reviewer. The four methodology conflicts are removing exclusions, adding guarantee stacks, replacing exact quotations, and drifting from the Primary mechanism. Consult the designated reviewer or mentor rather than automatically adopting or rejecting advice solely because it is paid.

The four proposed removal triggers are three or more materially disruptive reports, missing at least twenty percent of quarterly deadlines, an agreement violation such as using review time to upsell, or leaving the field/not renewing the agreement. The document proposes quarterly updates, thirty days' notice and possible later re-entry. These are not actions taken against any person.

Review the process itself

After a cohort, examine the proportion using each route, median request-to-delivery time, the proportion meeting deadlines without escalation, and the proportion of paid feedback conflicting with the stated methodology. The SOP proposes revisiting capacity above thirty-percent mentor substitutions, agreements or roster choices above twenty-percent paid conflicts, and cohort discussion below a 0.85 given/received ratio. These are proposed thresholds, not validated universal benchmarks.

Its additional escalation triggers are three or more failed submissions by one student, fabrication or conflicting reviewer feedback requiring agreement review, an individual reciprocity ratio below 0.5 across two cohorts, and more than three consecutive weeks of thin participation prompting a recruitment review. Define denominators and review evidence before acting. The source's promise that a validator will not penalize alternate routes needs actual implementation verification.

The practical output is a stable reviewed draft, genuine feedback, a decision log, correctly recorded review credits and explicit unresolved issues. Connect Brunson/ClickFunnels message continuity with the Hormozi/Acquisition.com value lens: review whether the promise, evidence, exclusions and delivery agree. Do not mistake template completion, agreement between two reviewers or a numerical score for proof of buyer demand.

Clickable linked resources

- Preparation checklist - Six outreach and response templates - Peer-review coordination SOP - Complete review template - Alternate protocols - Paid-review reference with placeholder roster

Preserve all six complete originals in the applicable lesson appendices. Their dates, templates and embedded operational instructions remain source material, not current service promises or actions executed by this task.

Assigned source links

D0439 original source 1

# C4 Offer Ignition — Time Estimate

## Top-Line Numbers

- **Active work:** 40 hours
- **Elapsed time:** 4-5 weeks
- **Average per week:** 8-10 hours
- **Longest single module:** M4.7 Offer Landing Page Copy (4 hours active + peer review cycle)
- **Shortest single module:** M4.1 Offer Architecture Foundations (75 minutes active)

C4 is shorter in active hours than C3 because the work is internal writing rather than external research. Elapsed time, however, is only slightly shorter — writing improves on the second pass, and the 48-hour cooling period between first and second drafts of M4.3, M4.5, M4.7, and M4.8 compresses poorly.

---

## Active Work by Module

| Module | Active Work | Cumulative |
|---|---|---|
| M4.1 Offer Architecture Foundations | 75 min | 1:15 |
| M4.2 The Grand Slam Offer Framework | 90 min | 2:45 |
| M4.3 Offer Deconstruction and Reassembly | 180 min | 5:45 |
| M4.4 Pricing and Anchoring | 90 min | 7:15 |
| M4.5 The Anti-Promise Statement | 75 min | 8:30 |
| M4.6 Guarantee Architecture | 90 min | 10:00 |
| M4.7 Offer Landing Page Copy | 240 min | 14:00 |
| M4.8 Offer Readiness Document | 90 min | 15:30 |

Module activity subtotal: ~15-16 hours.

## Implementation Work (Beyond Module Active Time)

Module active work is module-internal only. Implementation work spans outside the module sessions:

| Implementation Activity | Hours |
|---|---|
| Re-reading C3 Market Fit Hypothesis and Trigger Bank | 1-2 |
| First-draft revision of M4.3 variants after 48-hour cooling | 2-3 |
| Landing page copy revision after first draft (M4.7) | 3-5 |
| Peer review of 2 cohort peers' landing page copy | 2-3 |
| Incorporating 2 peer reviews of own landing page copy | 1-3 |
| Anti-promise revision after guarantee decision | 1 |
| Pricing spreadsheet / unit economic sanity check | 1-2 |
| Readiness document draft + revision | 2-3 |
| Circle.so discussion and reflection posts | 1-2 |

Implementation subtotal: ~15-24 hours.

**Course total: ~30-40 hours active work, target 40.**

C4's total is firmly below C3's 45 hours because there is no external scheduling component. Writing time is writing time. Students who struggle to hit 40 hours typically do not need more study time — they need more honest drafts and a willingness to throw away the first one.

---

## Elapsed Time Breakdown

### 4-Week Pacing (aggressive, assumes peer reviews come back on SLA)

| Week | Focus | Major Deliverables Due |
|---|---|---|
| 1 | M4.1 + M4.2 complete | Distinction memo + Value Equation worksheet filed |
| 2 | M4.3 complete (3 variants); M4.4 pricing | 3 decomposition variants + Pricing Decision filed |
| 3 | M4.5 anti-promise + M4.6 guarantee | Anti-Promise + Guarantee filed; Honesty Clause signed |
| 4 | M4.7 landing page (draft + peer review + revise); M4.8 Readiness | Landing page copy + Readiness Document filed; C4 complete |

### 5-Week Pacing (default, with slack for revision and peer review latency)

| Week | Focus | Major Deliverables Due |
|---|---|---|
| 1 | M4.1 + M4.2 complete | Distinction memo + Value Equation worksheet filed |
| 2 | M4.3 variants drafted (48-hr cooling) + refined | 3 decomposition variants filed |
| 3 | M4.4 pricing + M4.5 anti-promise | Pricing Decision + Anti-Promise filed |
| 4 | M4.6 guarantee + M4.7 landing page first draft | Guarantee filed; landing page draft out for peer review |
| 5 | Peer review incorporated; M4.8 Readiness Document | Final landing page + Readiness Document filed; C4 complete |

### 6+ Week Scenarios (when to flag for mentor)

C4 elapsed times past week 6 usually trace to one of four causes:

1. **Student is rewriting the Primary mechanism at the M4.3 stage** — a signal that C3 M3.7 was waved through rather than decided. Mentor action: stop C4 work, return to C3 M3.5-M3.7 to properly close the Primary decision.

2. **Landing page copy has 6+ drafts** — perfectionism or the Feature Stuffing Trap. Mentor action: review Case-Failure-The-Feature-Stuffing-Trap.md; often the underlying issue is a Value Equation score (M4.2) that student is trying to fix in copy rather than in mechanism.

3. **Peer reviews not returning** — cohort is thin or reviewers are stalled. Mentor action: switch to Protocol A (mentor substitution) in Prerequisites-Checklist.

4. **Anti-promise paralysis** — student cannot bring themselves to write the specific disqualification statement in M4.5. Mentor action: single 30-minute call walking through why anti-promises increase conversion rather than decrease it, per Hopkins 1923 / Hormozi 2021.

Escalation to mentor is automatic after 7 weeks in C4 without completion.

---

## Daily Completion Checklist (Operational)

For students using the C1 85-Minute Rhythm, here is how C4 work maps into the rhythm. See also `02_Resources/Checklists/C4-Daily-Completion-Checklist.md` for a per-week printable version.

### Monday — 10 minutes
Open the C4 folder. Review what's due this week. Re-read yesterday's draft with fresh eyes. Jot 1-2 revision notes.

### Tuesday — 15 minutes
Either draft the next module section OR revise yesterday's draft OR send peer review feedback if assigned.

### Wednesday — 30 minutes (Deep Work)
The week's main drafting block. M4.3 variant drafting, M4.7 landing page section drafting, M4.8 Readiness Document drafting — whichever is the current focus.

### Thursday — 20 minutes
Revision pass on Wednesday's draft. Cut weak sentences. Replace paraphrased Trigger Bank quotes with verbatim originals.

### Friday — 10 minutes
Friday reflection in Circle.so. What felt hardest this week? Which module surprised you?

Total rhythm commitment: 85 minutes/week. C4 work beyond the rhythm (longer drafting sessions, peer review work) is on top of the rhythm, not replacing it.

---

## Time Adjustments by Operator Archetype

### Teacher-Operator

- **Typical strength:** Curriculum-thinking makes M4.3 decomposition variants natural; clear about what a buyer learns in each step
- **Typical weakness:** M4.4 pricing tends to under-price because Teacher-Operators instinctively compare to course prices ($197-$497) rather than to service or cohort prices ($1,500-$10K)
- **Suggested adjustment:** +1 hour on M4.4 specifically pricing the cohort and service variants against the C3 Pricing Signals rather than against self-paced course benchmarks

### Builder-Operator

- **Typical strength:** M4.2 Value Equation work is sharp; technical credibility shows through in the Dream Outcome variable
- **Typical weakness:** M4.7 landing page copy sometimes reads as feature list rather than outcome promise; the Trigger Bank is underused
- **Suggested adjustment:** +2 hours on M4.7 specifically replacing first-draft feature descriptions with verbatim Trigger Bank outcome language

### Service-Operator

- **Typical strength:** Natural at M4.3 decomposition because the service already contains implicit deliverables; easy to name them
- **Typical weakness:** M4.5 anti-promise is hardest — Service-Operators rarely want to turn away buyers
- **Suggested adjustment:** +1 hour on M4.5 specifically working through the three categories of buyers the Primary is not well-suited for, with peer accountability

### Product-Operator, Creative-Operator, Systems-Operator

Time estimates unchanged. Adjustments available in `02_Resources/Reference-Charts/C4-Archetype-Adjustments.md`.

---

## The 48-Hour Cooling Period — Why It Matters for Your Estimate

Four modules bake a mandatory 48-hour gap between first and second drafts: M4.3, M4.5, M4.7, M4.8. The gap does not count against "active work" — nothing is happening — but it does count against elapsed time.

The gap exists because offers written and published in a single sitting tend to read as written-and-published-in-a-single-sitting. Sentences that feel clever at the moment of writing almost always sound thin two days later. The cooling period produces a pass where the student reads the draft as if someone else wrote it — which is the point at which the weak sentences reveal themselves.

A student who tries to compress the gap (write and revise on the same day) can complete C4 in 3 weeks elapsed. The output will be readable. It will also be weaker than a version with the gap honored. The output quality gap is usually visible at C5 during the first-sale readiness test, by which point rework is expensive.

Plan for the full 4-5 weeks. It is not padding. It is how the draft improves.

---

## Accommodations

If you have accessibility needs or life circumstances that require adjusted pacing:

- **Email [email protected]** before enrollment; 48-hour response SLA
- **Standard adjustments available:** extended C4 timeline (up to 10 weeks), peer review accommodations (async voice or written rather than synchronous), dyslexia-friendly landing page copy review by mentor rather than by peer
- **Financial accommodations:** scholarship for paid review (Protocol C) if the cohort is thin and paid review is needed

---

*Last updated: April 24, 2026 · Version 2.0*

# C4 Peer Review Preparation Checklist

**Purpose:** Pre-flight check before submitting M4.7 landing page copy for cohort peer review. Prevents common rework-causing gaps.
**Time to complete:** 15-20 minutes before submission
**Filed to:** Attached to your M4.7 submission

---

## Before You Submit

Running this checklist before posting in `#c4-offer-ignition` saves your peer reviewers 30-60 minutes per review and dramatically increases the quality of feedback you receive. Reviewers who have to hunt for your Trigger Bank Provenance Log, or who notice your anti-promise softened from M4.5, spend their review time on mechanical issues rather than substantive feedback.

---

## Section A — Document Completeness

- [ ] Landing page copy file exists at `Offer-Landing-Page-Copy-[YourName]-[Date].md`
- [ ] All 7 sections present in order:
  - [ ] Section 1 — Problem (200-400 words)
  - [ ] Section 2 — Agitation (150-300 words)
  - [ ] Section 3 — Solution-and-Mechanism (300-500 words)
  - [ ] Section 4 — Proof (200-400 words)
  - [ ] Section 5 — Offer (300-500 words)
  - [ ] Section 6 — Anti-Promise-and-Guarantee (250-400 words)
  - [ ] Section 7 — CTA (50-150 words)
- [ ] Total word count in 1,800-2,500 range (not absurdly over or under)

## Section B — Trigger Bank Usage

- [ ] Trigger Bank Provenance Log file exists at `Landing-Page-Trigger-Bank-Provenance-[YourName]-[Date].md`
- [ ] Log contains ≥ 15 entries mapped to landing page usage
- [ ] Every entry in the log is verbatim (not paraphrased) from the source Trigger Bank
- [ ] Each entry cites specific Trigger Bank ID (TB-###) or Interview #
- [ ] Entries are distributed across 4+ of the 7 sections (not all stacked in one section)

## Section C — Anti-Promise and Guarantee Integrity

- [ ] Anti-Promise in Section 6 is substantively the same as your M4.5 Anti-Promise Statement
- [ ] If any softening occurred between M4.5 and M4.7, it is reverted OR documented with rationale
- [ ] Anti-Promise Integrity Statement is signed
- [ ] Guarantee in Section 6 is substantively the same as your M4.6 Guarantee Architecture
- [ ] If any stacking occurred between M4.6 and M4.7, it is reverted
- [ ] Guarantee Honesty Clause is signed

## Section D — Offer Section Completeness

- [ ] Named deliverable (5-Test-passed name) visible in Section 5
- [ ] Price visible in Section 5 (not hidden, not ranged)
- [ ] Payment options listed
- [ ] Delivery structure described (engagement model, duration, cadence)
- [ ] Deliverables list is not over 8 items (Feature Stuffing Trap check)

## Section E — Proof Integrity

- [ ] Proof cases in Section 4 are specific (named or anonymized with specific outcome)
- [ ] If you have fewer than 4 named cases, the Known Weaknesses acknowledgment is visible (not papered over)
- [ ] Testimonials (if any) are verbatim quotes, not paraphrased
- [ ] Testimonials have attribution (name or anonymized but specific)

## Section F — CTA Specificity

- [ ] CTA names a specific action (not "click here")
- [ ] Next cohort / enrollment date is present
- [ ] Qualification process (if any) is described
- [ ] Contact email or channel is present for pre-purchase questions

## Section G — Voice Check

- [ ] You have read the full landing page out loud once, from start to finish
- [ ] The page does not contain phrases you would not actually say to a buyer in person
- [ ] The page does not contain hyperbole you cannot substantiate
- [ ] The page does not contain any of these phrases: "game-changer," "revolutionary," "transform your life," "all you need to do is" (low-substance signaling vocabulary)

## Section H — Review Request Post

Before posting in `#c4-offer-ignition`, prepare the post:

- [ ] Drive link to landing page copy
- [ ] Drive link to Trigger Bank Provenance Log
- [ ] Brief context (2-3 sentences about your offer's key positioning)
- [ ] Specific request: "2 peer reviews within 72 hours, using the C4 Peer Review Template"
- [ ] Your availability to return review favor (which days you can review others' copy)

---

## Common Pre-Submit Fixes

If any checklist item is unchecked, common fixes:

| Unchecked Item | Typical Fix |
|---|---|
| Section 6 softened from M4.5/M4.6 | Revert to the original M4.5 Anti-Promise and M4.6 Guarantee language |
| Trigger Bank count < 15 | Add 3-6 more verbatim entries, typically in Problem and Agitation sections |
| Deliverables > 8 | Review for Feature Stuffing; which deliverables are compensation, which are real value? |
| Price hidden or ranged | Move price to Section 5 with explicit number |
| Voice check fails | 48-hour cooling re-read; rewrite any section where "did I actually say that?" is your reaction |

---

## After Submission

Once posted:

- [ ] Check `#c4-offer-ignition` daily for reviewer pickup
- [ ] Respond promptly to reviewer questions
- [ ] Do not revise the landing page while reviews are in progress (creates version mismatch)
- [ ] Begin reviewing other cohort peers' landing pages as reviews arrive — reciprocity is cohort norm

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

# C4 Peer Review Outreach Scripts

**Purpose:** Short scripts for requesting and responding to peer reviews during M4.7. These are starter templates; adapt in your own voice.
**Filed to:** `03_Scripts-and-Prompts/Outreach-Scripts/`
**Referenced by:** M4.7 Written Lesson; C4-Peer-Review-Preparation-Checklist

---

## Script 1 — Requesting Peer Review (post in `#c4-offer-ignition`)

```
**M4.7 peer review request — [YourName]**

- **Offer name:** [5-Test-passed name]
- **Target buyer:** [one sentence describing who this is for]
- **Price:** $[X]
- **What I want reviewers to watch for specifically:**
  - [1-2 things you suspect may be weak — common: Section 4 Proof, Section 6 Anti-Promise softening, Trigger Bank entry density]

**Drive links:**
- Landing page copy: [link]
- Trigger Bank Provenance Log: [link]
- Revision Log (so far): [link — if you have one]

**SLA:** 72 hours ideal

**Reciprocity:** I'm available to review copy on [specific days this week]. Reply with yours and I'll pick up the first two.

Using the C4 Peer Review Template (`02_Resources/Templates/C4-Peer-Review-Template.md`).
```

### Why this structure works

Naming what you suspect is weak focuses reviewer attention. Without this, reviewers tend to spread feedback thin across the whole page. Concentrated attention on 1-2 sections produces higher-signal feedback.

---

## Script 2 — Offering Peer Review (response to another student's request)

```
I'll pick up your review, [TheirName]. I'll aim to deliver within 48 hours.

If you want me to pay particular attention to [suggested focus based on their request], I will. If you want me to do a straight full-template review, I'll do that too.

My C4 Peer Review Template will be back in your Drive folder or Circle.so thread by [specific date + time].
```

### Why this structure works

Confirms the commitment with a specific delivery time. Acknowledges their request-specific focus areas. Creates accountability for the delivery.

---

## Script 3 — Declining a Peer Review (when over-committed)

```
Thanks for tagging me, [TheirName]. I'm at capacity this week ([reason if relevant — e.g., "I'm in my own M4.7 cycle with deadline Thursday"]).

Tagging [OtherName] who mentioned they had bandwidth this week. You can also use the Alternate Protocol at `02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md` if the cohort is thin at your pacing — Protocol A (mentor substitution) is available.
```

### Why this structure works

Declining without leaving the requester stranded. Referring to Alternate Protocol reminds the requester that the safety net exists.

---

## Script 4 — Delivering Peer Review (after completing the template)

```
[TheirName] — review complete.

**Template:** [Drive link to completed Peer Review Template]

**Top-level observation:** [one sentence — your overall impression]

**My three recommended revisions (from template):**
1. [brief version]
2. [brief version]
3. [brief version]

Happy to discuss any of these in async DM if useful. Good luck with M4.8.
```

### Why this structure works

Surfaces the most actionable takeaway in the message itself so the requester can start revising without waiting to open the full template. The full template provides depth; the message provides urgency.

---

## Script 5 — Responding to Peer Review (after incorporating)

```
[ReviewerName] — thanks for the review. Incorporated as follows:

- **Revision 1 you recommended:** [incorporated / incorporated with modification / not incorporated + reason]
- **Revision 2:** [same format]
- **Revision 3:** [same format]

Revision Log in Drive: [link]

Appreciate the time.
```

### Why this structure works

Closes the loop on every recommendation. Decisions not to incorporate are documented (not silently ignored). The Revision Log is what the offer-fit-validator at M4.8 checks for.

---

## Script 6 — Escalating to Mentor (when Alternate Protocols Fail)

Address to `#mentor-requests` Circle.so channel or via the mentor Calendly link from cohort welcome email:

```
**C4 M4.7 peer review escalation — [YourName]**

- Cohort pacing window: [your dates]
- Peer reviews attempted: [how many requests, how many responses]
- Alternate Protocols tried: [A — mentor booking status / B — cross-stage post status / C — paid review status]

**Specific help requested:** [mentor review of landing page, or pacing adjustment, or cohort coordination]

**Drive link:** [landing page copy]
**SLA needed:** [your revised timeline]
```

### Why this structure works

Names what has already been tried so the mentor does not repeat the available paths. Specifies what help is actually requested so the mentor can respond efficiently.

---

## Cohort Etiquette

A few norms that make peer review work sustainably across the cohort:

### Reciprocity

The cohort operates on a rough reciprocity norm: if you ask for reviews, you offer them. Students who take reviews without giving them quickly exhaust peer willingness. This is not enforced policy — it is cohort culture.

### Specificity Over Generosity

Reviews saying "this is great!" are useless. Reviews saying "Section 2 Agitation feels performative — specifically the 'wasted years' language in paragraph 2 reads generic against the specific Trigger Bank language in Section 1" are useful. Prefer specificity even when it is critical.

### Honest Over Kind

Kind reviews that paper over weak sections serve the student short-term and harm them medium-term (the weak sections surface in C5 anyway, now harder to fix because the student thought they were okay). Honest reviews that name specific weaknesses are the service.

### Respond Within SLA

72-hour SLA is a cohort commitment. If you cannot hit it, decline (Script 3) rather than miss silently. Missed SLAs are the single largest cause of C4 M4.7 pacing disruption.

---

## When To Use These Scripts vs. Your Own Voice

These scripts are starters. Adapt in your voice, especially for Scripts 1 and 4 — mechanical-sounding review requests signal to cohort peers that you have not yet internalized the discipline of the M4.7 work. Personal voice in the request correlates with higher-quality responses.

Scripts 2, 3, and 6 are more mechanical — they coordinate logistics rather than substance — and can stay closer to template voice.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

sop_id: C4-SOP-02
title: Peer Review Coordination Process
version: 2.0.0
course_scope: C4 Offer Ignition
modules_covered: [M4.7]
owner: curriculum-quality-team
last_reviewed: 2026-04-24

purpose: >
  Standardize the M4.7 peer review process from request through delivery and
  through revision incorporation. M4.7 is the only C4 module requiring peer
  review (instructor HITL is deferred to C5; AI rubric runs after peer reviews
  are incorporated). Peer review is the first time the offer is exposed to
  outside readers; the process must protect both reviewer time and reviewee
  outcomes. This SOP defines reciprocity, SLA, alternate protocols, and
  revision logging.

prerequisites:
  - M4.7 Landing Page Copy first draft complete in Drive
  - Trigger Bank Provenance Log complete in Drive
  - C4-Peer-Review-Preparation-Checklist run before submission
  - 48-hour cooling period observed between first draft and submission

roles:
  - submitting_student: requests review; reciprocates by reviewing 2 peers
  - peer_reviewer_1: cohort peer at compatible pacing
  - peer_reviewer_2: second cohort peer at compatible pacing
  - mentor: escalation if Alternate Protocols A/B/C all fail
  - cross_stage_reviewer: Stage 2+ alumnus available via Protocol B
  - paid_reviewer: from Approved Paid Review Options list (Protocol C)
  - build_6: tracks SLA, matches reviewers, gates M4.7 checkpoint progression

process:
  step_1:
    name: Pre-Submission Self-Audit
    time: 20 min
    output: Completed Peer Review Preparation Checklist
    activities:
      - Run C4-Peer-Review-Preparation-Checklist sections A through H
      - Address any unchecked items before posting review request
      - Verify Trigger Bank entry count >= 15 with Provenance Log complete
      - Verify anti-promise unchanged from M4.5; verify guarantee unchanged from M4.6
    quality_gate: All preparation checklist items checked; if any item is unchecked, fix before requesting review
    common_failures:
      - "Posting request before Trigger Bank entries reach 15"
      - "Posting request with anti-promise softened from M4.5 (peer reviewers will flag, costing 24-48 hours)"
      - "Forgetting to attach Trigger Bank Provenance Log"
    mitigation: The checklist exists specifically to catch these. Run it.

  step_2:
    name: Request Review (Standard Protocol)
    time: 15 min
    output: Review request post in #c4-offer-ignition Circle.so channel
    activities:
      - Use Outreach Script 1 from C4-Peer-Review-Outreach-Scripts.md
      - Specify offer name, target buyer, price, areas you suspect are weak
      - Attach Drive links to landing page copy AND Trigger Bank Provenance Log
      - State 72-hour SLA expectation
      - Offer specific reciprocity (which days you can review others' copy this week)
    quality_gate: Post visible in #c4-offer-ignition; request structure matches Outreach Script 1
    common_failures:
      - "Vague request without specifying suspected-weak sections (reviews come back generic)"
      - "Not offering reciprocity (cohort norm violated; future review requests slower to receive responses)"
      - "Missing Provenance Log attachment (reviewers can't verify Trigger Bank usage)"
    mitigation: Use the script verbatim until it becomes natural

  step_3:
    name: Reviewer Pickup (24-48 hours from request)
    time: passive
    output: 2 peers commit to review with stated delivery dates
    activities:
      - Build 6 sends notification to active cohort peers at compatible pacing
      - Peers respond using Outreach Script 2 (acceptance) or Script 3 (decline with referral)
      - Build 6 logs commitments and tracks SLA
      - If only 1 reviewer commits within 48 hours, Build 6 escalates per step 4a
    quality_gate: 2 reviewers committed within 48 hours
    common_failures:
      - "Cohort thin at student's pacing (Protocol A activates)"
      - "Reviewers who committed silently miss SLA without communication"
    mitigation: Build 6 active SLA tracking surfaces silent misses; cohort norm includes communicating early if SLA at risk

  step_4_alternate_protocol_a:
    name: Mentor Substitution (Protocol A)
    time: 24 hours from activation
    output: Mentor named as reviewer; review delivered within 72 hours
    activation_trigger: Cohort has < 4 active peers at compatible pacing OR < 2 peers commit within 48 hours
    activities:
      - Student books mentor review slot via Calendly link in cohort welcome email
      - OR Student posts in #mentor-requests with M4.7 review request
      - Mentor delivers full Peer Review Template completion within 72 hours
      - Mentor review counts as both required peer reviews
    quality_gate: Mentor review filed with C4-Peer-Review-Template completion
    common_failures:
      - "Mentor booking backed up 2+ weeks during high-enrollment cycle (rare; route to Protocol B)"

  step_4_alternate_protocol_b:
    name: Cross-Stage Review (Protocol B)
    time: 96 hours from activation
    output: 1-2 Stage 2+ alumni reviewers complete review
    activation_trigger: Mentor backed up; OR student prefers reviewer who has shipped offers
    activities:
      - Student posts in #cross-stage-review channel using request format from Alternate Protocol document
      - Stage 2-5 operators who actively volunteer review time pick up the request
      - Review uses C4 Peer Review Template
      - Cross-stage review counts as both required reviews, OR pairs with one peer/mentor review
    quality_gate: Cross-stage review filed
    common_failures:
      - "No cross-stage reviewer picks up within 48 hours (route to Protocol C)"

  step_4_alternate_protocol_c:
    name: Approved Paid Review (Protocol C — Last Resort)
    time: 48-72 hours from activation
    output: Paid reviewer completes review using C4 Peer Review Template
    activation_trigger: Protocols A and B unavailable within student's planned week
    activities:
      - Student selects from C4-Approved-Paid-Review-Options.md (Tier A/B/C)
      - Direct engagement; Academy does not facilitate payment
      - Paid reviewer completes C4 Peer Review Template
      - Paid review counts as 1 of 2 required reviews; must pair with peer/mentor/cross-stage for second
      - Methodology consistency check: any methodology-conflicting paid feedback flagged before incorporation
    quality_gate: Paid review filed; second review (peer/mentor/cross-stage) also filed
    common_failures:
      - "Paid reviewer recommends removing anti-promise (methodology-conflict; do not incorporate without mentor consult)"
      - "Paid reviewer recommends stacking guarantees (methodology-conflict)"
      - "Student counts paid review as both required reviews (not allowed)"
    mitigation: Approved Paid Review document provides methodology baseline language to send to paid reviewer

  step_5:
    name: Receive and Read Reviews
    time: 30 min (do not act yet)
    output: Both reviews read in single sitting
    activities:
      - Wait until both reviews have arrived before reading either
      - Read both in one sitting; note patterns
      - If both reviewers flagged the same section as weak, that section is genuinely weak
      - If reviewers disagree, use your judgment
      - Do not begin revision yet — sleep on the feedback
    quality_gate: Both reviews read; pattern notes captured
    common_failures:
      - "Reading first review and immediately starting revisions before second review arrives (creates whiplash if reviewers disagree)"
      - "Defending against feedback in your head without genuinely considering it"
    mitigation: 12+ hour gap between reading and revising; treat reviews as gifts, not attacks

  step_6:
    name: Draft Revision Log + Revise
    time: 60-90 min
    output: Revision Log file + revised landing page in Drive
    activities:
      - Open C4-Peer-Review-Outreach-Scripts.md Script 5 template
      - For each suggestion in each review: incorporated / incorporated with modification / not incorporated + reason
      - Document each decision; the offer-fit-validator at M4.8 reads this
      - Revise landing page based on incorporated suggestions
      - Address pattern-flagged sections (those flagged by both reviewers) with priority
    quality_gate: Revision Log complete; revised landing page in Drive
    common_failures:
      - "Skipping the Revision Log (validator at M4.8 will flag missing log)"
      - "Incorporating every suggestion mechanically (you should make decisions, not absorb)"
    mitigation: The Log is the structural mechanism that forces decision-making; do not skip

  step_7:
    name: Reciprocate
    time: 90-120 min total (45-60 min per review × 2)
    output: 2 completed peer reviews delivered to other students
    activities:
      - During or after your own revision cycle, complete 2 peer reviews for cohort peers
      - Use C4-Peer-Review-Template for each
      - Deliver via Outreach Script 4 from outreach scripts document
      - Reciprocity is cohort norm; tracking is light but reputation matters
    quality_gate: 2 reviews delivered; Build 6 logs reciprocity in cohort metrics
    common_failures:
      - "Receiving reviews and not reciprocating (silent reputation cost; future requests slower to receive responses)"
      - "Reciprocating with low-effort 'looks great!' reviews (worse than declining; harms peer's revision quality)"
    mitigation: If you genuinely cannot reciprocate this cycle, decline future review requests until you can; do not free-ride

  step_8:
    name: Submit Revised Landing Page to AI Rubric
    time: 5 min + 5 min for rubric run
    output: landing-page-copy-reviewer score >= 7/10
    activities:
      - Submit revised landing page + provenance log + revision log to Build 6
      - Build 6 invokes landing-page-copy-reviewer-v1.0.0.yaml
      - Verify peer_review_count >= 2 in submission metadata
      - Receive rubric score within 5 minutes
    quality_gate: Score >= 7/10; peer_review_count = 2; no integrity flags
    common_failures:
      - "Submitting without filing the Revision Log first (rubric flags missing artifact)"
      - "Trigger Bank entries fabricated or paraphrased (rubric flags as integrity issue)"
    mitigation: All checks should already have passed in step 5-6; if rubric flags appear, fix and resubmit

review_and_adjustment:
  cadence: Per cohort cycle
  questions_to_ask:
    - "What % of M4.7 submissions used Standard Protocol vs Alternate Protocol A/B/C?"
    - "What was the median time from review request to review delivery?"
    - "What % of reviewers met SLA without escalation?"
    - "What % of paid reviewers gave methodology-conflicting feedback?"
  adjustment_principles:
    - If Alternate Protocol A activation > 30%, expand mentor capacity OR extend cohort recruitment to thicken cohorts
    - If paid reviewer methodology conflicts > 20%, refresh paid reviewer Affiliate Agreements OR remove specific reviewers from Approved list
    - If reciprocity ratio (reviews given / reviews received) < 0.85, surface in cohort discussion

escalation_triggers:
  - 3+ submissions fail M4.7 rubric on same student (mentor diagnosis)
  - Reviewer fabrication or methodology-conflicting feedback (Affiliate Agreement review)
  - Reciprocity ratio < 0.5 for individual student over 2 cohorts (cohort norm conversation)
  - Cohort thinning > 3 weeks consecutive (Build 6 → Marketing for cohort recruitment review)

related_documents:
  - 02_Resources/Templates/C4-Peer-Review-Template.md
  - 02_Resources/Templates/C4-Peer-Review-Alternate-Protocol.md
  - 02_Resources/Templates/C4-Approved-Paid-Review-Options.md
  - 02_Resources/Checklists/C4-Peer-Review-Preparation-Checklist.md
  - 03_Scripts-and-Prompts/Outreach-Scripts/C4-Peer-Review-Outreach-Scripts.md
  - 03_Scripts-and-Prompts/Claude-System-Prompts/landing-page-copy-reviewer-v1.0.0.yaml

# C4 Peer Review Template — M4.7 Landing Page Copy

**Purpose:** Structured template for cohort peer reviews of M4.7 landing page copy. Two peer reviews per student are required; students complete two reviews for peers in exchange.
**Time per review:** ~45-60 minutes
**Timeline:** 72-hour SLA from review request to delivery
**Filed to:** Build 8 Drive folder; linked into submitting student's M4.7 folder

---

## Reviewer Instructions

Read the landing page copy and the Trigger Bank Provenance Log in one pass, then complete the template below. Your job is not to edit line-by-line — the submitting student will do that. Your job is to surface structural issues they cannot see from inside their own draft.

Three things you are specifically looking for:

1. **Does the page sound like the market or like the operator?** You are an outside reader who has not been inside this operator's head for 4 weeks. You can hear voice drift more clearly than they can.

2. **Are the verbatim Trigger Bank quotes doing work, or are they decorative?** Quotes should anchor specific claims. A quote dropped next to a general statement without connection is not working.

3. **Is the anti-promise actually specific, and is the guarantee actually clean?** M4.5 and M4.6 stand-alone documents can be strong but get softened in the landing page. You are the second set of eyes that catches softening.

---

## Reviewer Information

**Reviewer name:** _____________________________
**Reviewer operator archetype:** _____________________________
**Review date:** _____________________________
**Submitting operator name:** _____________________________
**Submitting operator's offer name:** _____________________________

---

## Section-by-Section Review

### Section 1 — Problem

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak
**One-sentence read:** [What is this operator's offer trying to solve, in your words?]

Does the Problem section make the buyer's current state specific and vivid?
☐ Yes, I could visualize it ☐ Partially ☐ No, it was generic

Was at least one verbatim Trigger Bank quote integrated meaningfully (not decoratively)?
☐ Yes ☐ Partially ☐ No

**Specific observations (1-3 sentences):**

---

### Section 2 — Agitation

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Does the Agitation section make the cost of *not acting* feel real, or does it feel performative?
☐ Real ☐ Mixed ☐ Performative

Did any specific numbers, time-frames, or opportunity costs make the Agitation land?
☐ Yes (which ones: __________) ☐ No

**Specific observations:**

---

### Section 3 — Solution-and-Mechanism

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

After reading this section, can you describe the mechanism in your own words?
☐ Yes, I could teach it to a friend ☐ Roughly ☐ No, it's still fuzzy

Are the 4 pillars of the mechanism visible, even if not labeled as pillars?
☐ Yes ☐ Partially ☐ No

**Specific observations:**

---

### Section 4 — Proof

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Are the proof cases specific (named, with outcome data), or are they generic ("Maya is great")?
☐ Specific ☐ Mixed ☐ Generic

If the operator has few case studies, is that acknowledged honestly, or is it papered over?
☐ Acknowledged honestly ☐ Handled in between ☐ Papered over

**Specific observations:**

---

### Section 5 — Offer

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Is the named deliverable clear, specific, and 5-Test-passed?
☐ Yes ☐ Partially ☐ No (how could it be clearer: __________)

Is the price visible on the page?
☐ Yes, clearly ☐ Present but buried ☐ Not visible

Does the delivery structure tell you what the buyer's experience actually is (what they do, when, with whom)?
☐ Yes, concretely ☐ Vaguely ☐ Not really

**Specific observations:**

---

### Section 6 — Anti-Promise-and-Guarantee

**This is the most important section to peer-review.**

**Anti-Promise strength:** ☐ Strong ☐ Adequate ☐ Weak

Does the anti-promise name three specific exclusions?
☐ Yes, three or more ☐ Two ☐ One or fewer

Are any of the "exclusions" actually flattering descriptions of the target buyer (e.g., "not for unmotivated people")?
☐ No, they are genuine exclusions ☐ One or two are flattering-dressed-as-exclusion ☐ Most are

**Guarantee strength:** ☐ Strong ☐ Adequate ☐ Weak

Is the guarantee a clean structure (one primary + one optional complementary), or is it stacked with three or more components?
☐ Clean ☐ Borderline ☐ Stacked (Feature Stuffing Trap signal)

If you were a buyer who met the activation conditions, do you trust this operator would honor the guarantee without friction?
☐ Yes ☐ Mostly ☐ Uncertain

**Specific observations:**

---

### Section 7 — CTA

**Strength rating:** ☐ Strong ☐ Adequate ☐ Weak

Does the CTA name a specific action (not "click here") and a specific outcome ("enroll in the Feb 12 cohort, receive Welcome Kit within 24 hours")?
☐ Yes, specific ☐ Partially ☐ Generic

Is there a clear timeline (cohort start date, enrollment close date)?
☐ Yes ☐ No

**Specific observations:**

---

## Cross-Cutting Review

### Verbatim Trigger Bank Usage

Pick 3 of the Trigger Bank quotes used in the landing page. Check them against the Provenance Log — do they match the source entry verbatim, or have they been paraphrased into "cleaner" language?

- **Quote #1:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased
- **Quote #2:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased
- **Quote #3:** ☐ Verbatim ☐ Slightly paraphrased ☐ Significantly paraphrased

**Overall provenance accuracy:** ☐ Strong (all 3 verbatim) ☐ Mixed ☐ Weak (paraphrasing is dominant)

### Voice Check

Does the page sound like the operator or like the market?
☐ Mostly market voice ☐ Mixed (operator voice leaks through in specific sections: __________) ☐ Mostly operator voice

### Total Trigger Bank Entry Count

Count the verbatim quotes in the landing page.
**Count:** ___ / 15 minimum

If below 15, the submission fails the M4.7 checkpoint.

---

## Top-3 Revisions You Recommend

Identify the three revisions that would most improve this landing page:

1. **Revision 1:**
2. **Revision 2:**
3. **Revision 3:**

Each revision should be specific enough that the operator can act on it ("tighten the Problem section opening from 4 sentences to 2") rather than abstract ("improve the copy").

---

## Reviewer Closeout

**Overall assessment:** ☐ Ready to submit ☐ Needs moderate revision ☐ Needs substantial revision

**Would I buy this offer if I were the target buyer?** ☐ Yes ☐ Maybe ☐ No — and why: __________

**Reviewer signature:** _____________________________

---

## For the Submitting Operator

After receiving both peer reviews:

1. Read both reviews in one sitting before acting on either. Look for patterns — if both reviewers flagged the same section as weak, that section needs real work. If they disagree, use your judgment.

2. Your job is not to accept every suggestion. Your job is to take each suggestion seriously and make a documented decision about whether to incorporate it.

3. File a Revision Log (`Revision-Log-M4.7-[YourName]-[Date].md`) noting which suggestions you incorporated, which you considered but did not incorporate, and why. The offer-fit-validator at M4.8 checks for this log.

4. Revise. Submit the revised landing page to the AI rubric (`landing-page-copy-reviewer-v1.0.0.yaml`).

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.7*

# C4 Peer Review Alternate Protocol

**Purpose:** Alternate paths when your active C4 cohort has fewer than 4 peers at your pacing window. Ensures M4.7 does not stall for reviewer unavailability.
**Referenced by:** `00_Course-Overview/C4-Prerequisites-Checklist.md`
**Escalation path:** If none of the protocols below are viable, escalate to RISER Nation mentor within 72 hours of M4.7 draft completion.

---

## When to Use This Protocol

Use when any of the following is true:

- Your C4 cohort Circle.so channel (`#c4-offer-ignition`) has fewer than 4 active operators at your pacing window
- Cohort peers at your pacing window have not responded within 72 hours of your review request
- Your cohort is pacing unusually (ahead or behind the main cohort cycle) and peers are not currently at M4.7

---

## Protocol A — Mentor Substitution (Default)

**Who it's for:** Any student whose cohort is too thin for 2 peer reviews.

**How it works:**

1. Book a 45-minute review slot with a named RISER Nation mentor via the Calendly link in the cohort welcome email, or via the `#mentor-requests` Circle.so channel.
2. Submit your M4.7 draft and Trigger Bank Provenance Log at least 24 hours before the review call.
3. The mentor completes the C4 Peer Review Template during or after the call and delivers a written review within 72 hours.
4. Mentor review counts as both required peer reviews. No additional review needed.

**SLA:** 72 hours from submission to written review delivery (typical) ; 96 hours worst-case.

**Cost:** No charge. Mentor capacity is allocated out of Academy program support time.

**When Protocol A is not available:** Mentor booking backed up 2+ weeks. Rare but happens in high-enrollment cycles. Shift to Protocol B.

---

## Protocol B — Cross-Stage Review

**Who it's for:** Students whose mentor booking is backed up, or who prefer review from an operator who has already shipped offers.

**How it works:**

1. Post a review request in the `#cross-stage-review` Circle.so channel with the following structure:

   ```
   **Cross-stage review request — C4 M4.7**
   - Operator archetype: [Teacher / Service / Builder / etc.]
   - Territory: [one sentence]
   - Offer name: [the 5-Test-passed name]
   - Request: 1-2 Stage 2+ operators for M4.7 landing page review
   - SLA: 96 hours
   - Drive link: [link to your draft]
   - Trigger Bank Provenance Log: [link]
   ```

2. Stage 2, Stage 3, Stage 4, or Stage 5+ operators who are active volunteers pick up the review.
3. Review uses the same C4 Peer Review Template.
4. Cross-stage review counts as both required peer reviews, or as one review paired with a mentor/peer review.

**SLA:** 96 hours (longer than peer review because cross-stage operators volunteer review time around their own operation).

**Cost:** No charge. Typically treated as ecosystem reciprocity; Stage 2+ operators accumulate review credit that Stage 1 peers volunteer back.

**Why this can be better than peer review:** Reviewers who have shipped offers have firsthand knowledge of what survives first-sale contact and what does not. Their feedback often has higher signal-to-noise than peer-to-peer review.

**When Protocol B is not available:** No cross-stage reviewer picks up the request within 48 hours. Rare but happens near holiday periods. Shift to Protocol C.

---

## Protocol C — Paid Review (Last Resort)

**Who it's for:** Students whose timeline is blocked and Protocols A and B did not clear within their planned week.

**How it works:**

1. Choose from the Approved Paid Review list in `C4-Approved-Paid-Review-Options.md`.
2. Directly engage the reviewer (paid engagement; Academy does not facilitate payment).
3. Paid reviewer completes the C4 Peer Review Template.
4. Paid review counts as one of the two required reviews. **Paid review alone is not sufficient** — pair with one mentor, cross-stage, or peer review.

**SLA:** per reviewer contract, typically 48-72 hours.

**Cost:** Varies by reviewer. Typical range: $150-$400 per review.

**When Protocol C is genuinely necessary:** rare. Most students who think they need Protocol C actually have a timing problem that Protocol A or B resolves with a slight pacing adjustment (waiting 3-5 extra days for mentor or cross-stage slot).

**Warning:** paid review is a legitimate professional service but is not a substitute for cohort accountability. Paid reviewers who are not familiar with RISER Nation methodology sometimes give advice that conflicts with C3/C4 doctrine (e.g., suggesting feature-stuffed guarantees or removal of the anti-promise section). Review paid feedback critically against the module lessons; do not incorporate paid advice that conflicts with the methodology without checking with a mentor.

---

## Scholarship Path for Protocol C

If your cohort is thin, Protocols A and B are unavailable within your timeline, and Protocol C is financially inaccessible:

1. Email `[email protected]` with "C4 M4.7 Review Scholarship Request" in the subject line
2. Include your Drive link, pacing dates, and which Protocols were attempted
3. SLA: 48 hours for response; if approved, scholarship covers one paid review up to $200

Scholarship approval is typical for genuine thin-cohort situations.

---

## Logging the Alternate Protocol

Whatever Protocol you used, log it in your M4.7 Revision Log so the offer-fit-validator at M4.8 has the context:

```
Peer Review Protocol: [A — Mentor / B — Cross-Stage / C — Paid + one of A or B / Standard two-peer]
Reviewer 1: [name, protocol, date of review]
Reviewer 2: [name, protocol, date of review]
Alternate protocol rationale: [1-2 sentences]
```

The offer-fit-validator does not penalize Alternate Protocol usage — it penalizes missing reviews. Logging the protocol used keeps the validator's coherence checks from flagging the submission.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by C4-Prerequisites-Checklist*

# C4 Approved Paid Review Options

**Purpose:** Reference list of paid review providers vetted by RISER Nation for C4 M4.7 landing page review when cohort peer and mentor options are unavailable (Protocol C in the Peer Review Alternate Protocol).
**Referenced by:** `C4-Peer-Review-Alternate-Protocol.md`
**Status:** This list is maintained by the Academy team and updated quarterly. The version below reflects approved reviewers as of the Last Updated date.

---

## Selection Criteria

To appear on this list, a reviewer has:

- Reviewed at least 20 C4-style offer landing pages in the direct-response tradition
- Demonstrated familiarity with mechanism-based offer construction (Hormozi-adjacent methodology)
- Produced reviews that respect the anti-promise section as a credibility mechanism (rather than recommending its removal)
- Signed the RISER Nation Reviewer Affiliate Agreement — which commits them to methodology-consistent feedback
- Been cross-rated by at least 5 past reviewees as useful and non-disruptive

Reviewers without these properties are excluded from the list, regardless of market reputation.

---

## Current Approved Reviewers (Quarterly Update — Q2 2026)

### Tier A — Deep Direct-Response Specialists

These reviewers have 10+ years of direct-response copy experience. Pricing reflects seniority.

- **Reviewer Slot A1** — [reviewer name redacted for template; actual list maintained in Drive]
  - **Pricing:** $350-$450 per review
  - **SLA:** 72 hours
  - **Specialty:** coaching/consulting offers; cohort programs; Teacher-Operator and Service-Operator archetypes
  - **Contact:** [via Calendly link in Drive version]

- **Reviewer Slot A2**
  - **Pricing:** $300-$400 per review
  - **SLA:** 48-72 hours
  - **Specialty:** productized services; Builder-Operator archetype
  - **Contact:** [via Drive]

### Tier B — Mid-Senior Reviewers

5-10 years of direct-response experience. Pricing is moderate.

- **Reviewer Slot B1**
  - **Pricing:** $200-$275 per review
  - **SLA:** 48-72 hours
  - **Specialty:** creative services; Creative-Operator archetype
  - **Contact:** [via Drive]

- **Reviewer Slot B2**
  - **Pricing:** $175-$250 per review
  - **SLA:** 72 hours
  - **Specialty:** B2B offers; systems and platforms; Systems-Operator archetype
  - **Contact:** [via Drive]

### Tier C — RISER Nation Alumni Reviewers

Alumni who have completed Stage 2+ of the Academy and offer paid review to Stage 1 peers. Often the best value — they know the methodology cold and price accordingly.

- **Reviewer Slot C1-C5** — rotating list, currently 5 alumni reviewers available
  - **Pricing:** $150-$200 per review
  - **SLA:** 48-72 hours
  - **Specialty:** matches the alumni's own operator archetype; check Drive list for match
  - **Contact:** [via Drive; alumni reviewers coordinate through `#alumni-review-pool` Circle.so channel]

---

## How To Engage a Paid Reviewer

1. **Check the Drive version of this list** for current names, contact info, and availability status. Names are not in this template to avoid stale information when reviewers rotate.

2. **Match reviewer to your archetype.** A Teacher-Operator reviewing a Service-Operator's offer will sometimes give advice that is methodology-correct but archetype-mismatched. Tier A reviewers are generalists; Tier B and C reviewers are archetype-specialized.

3. **Send your M4.7 draft and Trigger Bank Provenance Log.** Use the C4 Peer Review Template as the deliverable format. Specify upfront that the review output should use the template — do not accept a free-form review.

4. **Specify the methodology baseline.** In your engagement message, include this line:
   > "This review is for a RISER Nation C4 Offer Ignition M4.7 landing page. The offer follows Hormozi-adjacent mechanism-based structure, and explicitly includes a specific Anti-Promise Statement (per Hopkins 1923 / Hormozi 2021) and a guarantee structure with the Honesty Clause signed. Please review for quality within the methodology rather than suggesting removal of these elements."

5. **Log the engagement** in your Revision Log per the Alternate Protocol instructions.

---

## What NOT to Use

**Do not use:**

- General copywriting review services not on this list (quality varies widely; many default to removing anti-promises, which is the specific thing C4 is trying to preserve)
- Fiverr-tier copy review (signal-to-noise too low for C4 work)
- AI-only review tools as a substitute for human review (acceptable as a supplement, not as the required review)
- Review from an unlisted paid reviewer *and* count it as your second required review (list-approved reviewers are the only paid reviews that satisfy Protocol C)

---

## If a Reviewer Gives Methodology-Conflicting Advice

If a paid reviewer recommends:
- Removing the anti-promise section
- Stacking guarantees beyond the clean structure M4.6 specifies
- Replacing verbatim Trigger Bank quotes with "cleaner" paraphrases
- Repositioning the offer in a way that drifts from your C3 Primary mechanism

...treat the feedback as methodology-conflicting. Do not incorporate without first consulting your RISER mentor or the `#methodology-questions` Circle.so channel. Methodology-conflicting advice from a paid reviewer often reflects their own training in non-anti-promise direct-response (common in the 2010s ecosystem) and is not wrong in their original context — it is just not aligned with C3/C4's specific synthesis.

---

## Removing a Reviewer from the List

Reviewers are removed from this list when any of the following occurs:

- 3+ reviewees report methodology-conflicting advice that was materially disruptive
- SLA missed on 20%+ of engagements over a quarter
- Reviewer Affiliate Agreement violation (e.g., upselling reviewees into their own offers during review time)
- Reviewer leaves the direct-response market or does not re-sign quarterly Affiliate Agreement

The list is updated quarterly. Removed reviewers receive 30 days' notice and are not blacklisted from re-entry if conditions change.

---

*Last updated: April 24, 2026 · Version 2.0 · Q2 2026 reviewer list current · Referenced by C4-Peer-Review-Alternate-Protocol*

# C4 Offer Ignition — Time Estimate

## Top-Line Numbers

- **Active work:** 40 hours
- **Elapsed time:** 4-5 weeks
- **Average per week:** 8-10 hours
- **Longest single module:** M4.7 Offer Landing Page Copy (4 hours active + peer review cycle)
- **Shortest single module:** M4.1 Offer Architecture Foundations (75 minutes active)

C4 is shorter in active hours than C3 because the work is internal writing rather than external research. Elapsed time, however, is only slightly shorter — writing improves on the second pass, and the 48-hour cooling period between first and second drafts of M4.3, M4.5, M4.7, and M4.8 compresses poorly.

---

## Active Work by Module

| Module | Active Work | Cumulative |
|---|---|---|
| M4.1 Offer Architecture Foundations | 75 min | 1:15 |
| M4.2 The Grand Slam Offer Framework | 90 min | 2:45 |
| M4.3 Offer Deconstruction and Reassembly | 180 min | 5:45 |
| M4.4 Pricing and Anchoring | 90 min | 7:15 |
| M4.5 The Anti-Promise Statement | 75 min | 8:30 |
| M4.6 Guarantee Architecture | 90 min | 10:00 |
| M4.7 Offer Landing Page Copy | 240 min | 14:00 |
| M4.8 Offer Readiness Document | 90 min | 15:30 |

Module activity subtotal: ~15-16 hours.

## Implementation Work (Beyond Module Active Time)

Module active work is module-internal only. Implementation work spans outside the module sessions:

| Implementation Activity | Hours |
|---|---|
| Re-reading C3 Market Fit Hypothesis and Trigger Bank | 1-2 |
| First-draft revision of M4.3 variants after 48-hour cooling | 2-3 |
| Landing page copy revision after first draft (M4.7) | 3-5 |
| Peer review of 2 cohort peers' landing page copy | 2-3 |
| Incorporating 2 peer reviews of own landing page copy | 1-3 |
| Anti-promise revision after guarantee decision | 1 |
| Pricing spreadsheet / unit economic sanity check | 1-2 |
| Readiness document draft + revision | 2-3 |
| Circle.so discussion and reflection posts | 1-2 |

Implementation subtotal: ~15-24 hours.

**Course total: ~30-40 hours active work, target 40.**

C4's total is firmly below C3's 45 hours because there is no external scheduling component. Writing time is writing time. Students who struggle to hit 40 hours typically do not need more study time — they need more honest drafts and a willingness to throw away the first one.

---

## Elapsed Time Breakdown

### 4-Week Pacing (aggressive, assumes peer reviews come back on SLA)

| Week | Focus | Major Deliverables Due |
|---|---|---|
| 1 | M4.1 + M4.2 complete | Distinction memo + Value Equation worksheet filed |
| 2 | M4.3 complete (3 variants); M4.4 pricing | 3 decomposition variants + Pricing Decision filed |
| 3 | M4.5 anti-promise + M4.6 guarantee | Anti-Promise + Guarantee filed; Honesty Clause signed |
| 4 | M4.7 landing page (draft + peer review + revise); M4.8 Readiness | Landing page copy + Readiness Document filed; C4 complete |

### 5-Week Pacing (default, with slack for revision and peer review latency)

| Week | Focus | Major Deliverables Due |
|---|---|---|
| 1 | M4.1 + M4.2 complete | Distinction memo + Value Equation worksheet filed |
| 2 | M4.3 variants drafted (48-hr cooling) + refined | 3 decomposition variants filed |
| 3 | M4.4 pricing + M4.5 anti-promise | Pricing Decision + Anti-Promise filed |
| 4 | M4.6 guarantee + M4.7 landing page first draft | Guarantee filed; landing page draft out for peer review |
| 5 | Peer review incorporated; M4.8 Readiness Document | Final landing page + Readiness Document filed; C4 complete |

### 6+ Week Scenarios (when to flag for mentor)

C4 elapsed times past week 6 usually trace to one of four causes:

1. **Student is rewriting the Primary mechanism at the M4.3 stage** — a signal that C3 M3.7 was waved through rather than decided. Mentor action: stop C4 work, return to C3 M3.5-M3.7 to properly close the Primary decision.

2. **Landing page copy has 6+ drafts** — perfectionism or the Feature Stuffing Trap. Mentor action: review Case-Failure-The-Feature-Stuffing-Trap.md; often the underlying issue is a Value Equation score (M4.2) that student is trying to fix in copy rather than in mechanism.

3. **Peer reviews not returning** — cohort is thin or reviewers are stalled. Mentor action: switch to Protocol A (mentor substitution) in Prerequisites-Checklist.

4. **Anti-promise paralysis** — student cannot bring themselves to write the specific disqualification statement in M4.5. Mentor action: single 30-minute call walking through why anti-promises increase conversion rather than decrease it, per Hopkins 1923 / Hormozi 2021.

Escalation to mentor is automatic after 7 weeks in C4 without completion.

---

## Daily Completion Checklist (Operational)

For students using the C1 85-Minute Rhythm, here is how C4 work maps into the rhythm. See also `02_Resources/Checklists/C4-Daily-Completion-Checklist.md` for a per-week printable version.

### Monday — 10 minutes
Open the C4 folder. Review what's due this week. Re-read yesterday's draft with fresh eyes. Jot 1-2 revision notes.

### Tuesday — 15 minutes
Either draft the next module section OR revise yesterday's draft OR send peer review feedback if assigned.

### Wednesday — 30 minutes (Deep Work)
The week's main drafting block. M4.3 variant drafting, M4.7 landing page section drafting, M4.8 Readiness Document drafting — whichever is the current focus.

### Thursday — 20 minutes
Revision pass on Wednesday's draft. Cut weak sentences. Replace paraphrased Trigger Bank quotes with verbatim originals.

### Friday — 10 minutes
Friday reflection in Circle.so. What felt hardest this week? Which module surprised you?

Total rhythm commitment: 85 minutes/week. C4 work beyond the rhythm (longer drafting sessions, peer review work) is on top of the rhythm, not replacing it.

---

## Time Adjustments by Operator Archetype

### Teacher-Operator

- **Typical strength:** Curriculum-thinking makes M4.3 decomposition variants natural; clear about what a buyer learns in each step
- **Typical weakness:** M4.4 pricing tends to under-price because Teacher-Operators instinctively compare to course prices ($197-$497) rather than to service or cohort prices ($1,500-$10K)
- **Suggested adjustment:** +1 hour on M4.4 specifically pricing the cohort and service variants against the C3 Pricing Signals rather than against self-paced course benchmarks

### Builder-Operator

- **Typical strength:** M4.2 Value Equation work is sharp; technical credibility shows through in the Dream Outcome variable
- **Typical weakness:** M4.7 landing page copy sometimes reads as feature list rather than outcome promise; the Trigger Bank is underused
- **Suggested adjustment:** +2 hours on M4.7 specifically replacing first-draft feature descriptions with verbatim Trigger Bank outcome language

### Service-Operator

- **Typical strength:** Natural at M4.3 decomposition because the service already contains implicit deliverables; easy to name them
- **Typical weakness:** M4.5 anti-promise is hardest — Service-Operators rarely want to turn away buyers
- **Suggested adjustment:** +1 hour on M4.5 specifically working through the three categories of buyers the Primary is not well-suited for, with peer accountability

### Product-Operator, Creative-Operator, Systems-Operator

Time estimates unchanged. Adjustments available in `02_Resources/Reference-Charts/C4-Archetype-Adjustments.md`.

---

## The 48-Hour Cooling Period — Why It Matters for Your Estimate

Four modules bake a mandatory 48-hour gap between first and second drafts: M4.3, M4.5, M4.7, M4.8. The gap does not count against "active work" — nothing is happening — but it does count against elapsed time.

The gap exists because offers written and published in a single sitting tend to read as written-and-published-in-a-single-sitting. Sentences that feel clever at the moment of writing almost always sound thin two days later. The cooling period produces a pass where the student reads the draft as if someone else wrote it — which is the point at which the weak sentences reveal themselves.

A student who tries to compress the gap (write and revise on the same day) can complete C4 in 3 weeks elapsed. The output will be readable. It will also be weaker than a version with the gap honored. The output quality gap is usually visible at C5 during the first-sale readiness test, by which point rework is expensive.

Plan for the full 4-5 weeks. It is not padding. It is how the draft improves.

---

## Accommodations

If you have accessibility needs or life circumstances that require adjusted pacing:

- **Email [email protected]** before enrollment; 48-hour response SLA
- **Standard adjustments available:** extended C4 timeline (up to 10 weeks), peer review accommodations (async voice or written rather than synchronous), dyslexia-friendly landing page copy review by mentor rather than by peer
- **Financial accommodations:** scholarship for paid review (Protocol C) if the cohort is thin and paid review is needed

---

*Last updated: April 24, 2026 · Version 2.0*

Review a customer-outcome packet without inventing evidence

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

What this specification actually provides

The assigned YAML describes a proposed Customer Outcome Reviewer, version 1.0.0, for the source's M10.2 capstone. It defines inputs, checks, red flags and a JSON-shaped response. It does not prove an agent has been deployed, that its assessments are reliable or that it has access to customer records. Its `model: claude-sonnet-4-7` identifier is unverified here and should not be represented as a confirmed available model. Its `hitl_gated: false` is source configuration text, not authorization to remove human review from this curriculum.

The source explains why the packet matters: later refund analysis, mastery synthesis and graduation review use its evidence. Errors can therefore propagate. The useful discipline is to preserve customer words and trace actual delivery. This supports truthful proof when presenting an offer, including a Brunson-style hook/story/offer sequence, and a grounded assessment of perceived likelihood in Hormozi's value framework. It does not turn a machine verdict into proof that customers achieved results.

Collect the eight specified inputs for every customer

The reviewer expects a customer label; a traceable offer version; the offer-promised outcome quoted from the offer; the delivered outcome supported by evidence; dated and sourced verbatim customer feedback; engagement friction; operator learnings; and current customer status. The status examples are active retainer, completed, mid-engagement, churned, refunded or near-refund. These states may overlap in a real system, so preserve the actual underlying record and explain the applicable state rather than force a misleading description.

Compare the number of entries with the paying-customer count established by the source's M10.1 verdict. The source points to C6/C7 offer iteration records for version traceability. Those are legacy dependencies, not changes to the current 12-course assignments. An offer label without a linked version record is not enough to establish what that customer saw at purchase.

The related template has eight header fields and five content sections, but does not explicitly provide the offer-version field. Add a clearly identified working-note field when applying the reviewer, preserving the original template. Record both original and current versions if the offer changed; do not substitute the newest offer for the one the customer bought.

Apply all nine validation checks

First, check that all eight inputs exist. Second, verify the offer version against the iteration record. Third, compare the promised-outcome quotation with the actual offer. These checks establish completeness and traceability; they do not authorize changing the original promise to match later delivery.

Fourth, verify specific delivered artifacts, dates and milestones. “The customer was happy” does not show what was delivered. Fifth, look for at least one actual customer quotation with a source such as an email date, transcript timestamp or written feedback record. Sixth, distinguish a quotation from the operator's paraphrase. “The customer said it was great” is not an exact customer quotation unless those were demonstrably the customer's actual words in the relevant context.

Seventh, assess whether friction is concrete: what happened, when, and how the operator responded. Eighth, connect each learning with evidence instead of a generic motivational statement. Ninth, compare the customer's status with the proposed Supabase record only when that record is actually available. If access is missing, the comparison is unverified. Do not mark a boolean true merely because the written narrative sounds plausible.

An authored practical workflow is to maintain a small evidence index beside the packet: field, source link, date checked, discrepancy and follow-up. This index is application guidance, not an additional artifact supplied by the YAML. It helps a human reviewer revisit a finding rather than rely on a generated judgment without supporting references.

Interpret the six red flags carefully

The first two flags concern customer quotations that sound like the operator's marketing copy or repeat similar phrasing across multiple customers. These are reasons to inspect the original messages. Writing style alone cannot establish fabrication. Customers may use similar language for legitimate reasons, and an automated classifier cannot authenticate a quote solely from how it sounds.

The third flag is absent or trivial friction. The source states categorically that every real engagement has substantive friction; that is not established by the document. Investigate whether the records are incomplete, but allow honest evidence of a smooth engagement. Never invent problems to make a packet appear credible.

The fourth flag concerns transformation claims unsupported by feedback. Check whether a learning exceeds the observation: a customer saying a template saved time does not prove their business transformed. The fifth concerns status disagreement with the database. Determine whether either record is stale, incorrectly classified or incomplete before accusing anyone of misrepresentation. The sixth concerns a promised outcome that differs from the original offer, potentially shifting the promise after delivery. Preserve the original wording and investigate any documented agreed change.

These flags support careful review. They are not findings of dishonesty until evidence supports that conclusion. The source's emphasis on constructive rigor is useful; discomfort, uniformly positive feedback or polished writing do not by themselves prove whether a packet is truthful.

Use the 6% rule as a source-specific heuristic

The YAML invokes a C1 doctrine: surface at least 16 data points across customer feedback, friction and learnings to identify one or two strong patterns. Its purpose is to discourage selecting only evidence that supports a preferred story. Preserve that stated threshold and its cross-reference, but label it a course-specific heuristic. The source supplies no statistical validation that 16 points guarantees a reliable pattern, or that one or two patterns will always emerge.

Keep contrary observations and identify which customer supplied each data point. Sixteen statements from one customer are not equivalent to sixteen independent customers. Do not multiply, fabricate or split observations merely to reach a quota. If evidence is limited, report that limitation and avoid a confident generalization. The source assigns cross-customer pattern development to later M10.5 work; this review establishes whether raw material exists for that work.

Understand every output field

The proposed response reports `customers_documented`, `expected_count` and `match`. Its `per_customer_review` array contains a `label`, a `completeness` object, `red_flags` and `revisions_required`. The completeness object has nine booleans: `all_8_fields`, `offer_version_traceable`, `promised_outcome_quoted`, `delivered_outcome_evidenced`, `verbatim_feedback_present`, `verbatim_feedback_sourced`, `friction_points_specific`, `learnings_evidence_tied` and `status_matches_supabase`.

At packet level, preserve `packet_red_flags`, `verdict` and `narrative_summary`. The verdict choices in this specification are APPROVED and REVISIONS_REQUIRED. The original JSON example uses placeholders such as N and `true | false`; it is an illustrative shape, not valid JSON ready to submit unchanged. In an implementation, replace those placeholders with actual values and validate the result. No implementation is deployed by this lesson.

A false or unverified finding needs a specific explanation and a feasible revision. For example, a missing offer version calls for locating the versioned source, not rewriting the outcome to sound more credible. The provided schema has no explicit unknown boolean state; an implementation must define how unavailable evidence is represented rather than silently treating unknown as confirmed. Preserve the original schema in the appendix and label any proposed extension as authored.

Reconcile acceptance conflicts and deferred submissions

The related template and M10.2 module allow a truthful record of unsuccessful attempts to obtain feedback. This reviewer nevertheless requires a quotation. Record the nonresponse, flag the outcome as not customer-validated and expose the acceptance conflict. The module also uses CONFORMS, REVISIONS_REQUESTED and OUTCOME_VAGUE_FLAG, whereas this YAML uses two different verdict labels. Do not claim they are already interoperable or silently discard the specificity flag; the intended mapping needs an explicit design decision.

The usage notes say operators in deferred-submission mode still document their existing one or two paying customers and update the packet as customers are added. Graduation should read the latest packet version. That is a source workflow, not proof that the prerequisite verdict or database exists. Record version dates and avoid presenting an earlier incomplete packet as the final current record. The proposed destination is `c10_customer_outcomes`; no database write is performed here.

Resources and complete specification

- Assigned customer-outcome reviewer YAML. - Related outcome template. - Related M10.2 module.

The full original YAML remains in the appendix. Apply its checks as an evidence review, while keeping unsupported thresholds, unverified integrations and conflicting acceptance rules visible.

Assigned source links

D0462 original source 1

name: customer-outcome-reviewer
version: 1.0.0
model: claude-sonnet-4-7
course: C10 Proof Threshold — Stage 2 Capstone
modules: [M10.2 Customer Outcome Documentation]
stage: 2
hitl_gated: false

description: >
  Validator for the M10.2 Customer Outcome Documentation packet.
  Reviews per-customer documentation for completeness, verbatim
  feedback presence, and structural integrity. The packet is the
  evidentiary substrate for M10.3 Refund Analysis, M10.5 Mastery
  Synthesis, and M10.8 Stage 2 Graduation Document. Gaps in M10.2
  cascade into FAIL verdicts at M10.8.

system_prompt: |
  You are the Customer Outcome Reviewer for C10. Your job is to
  validate the operator's M10.2 Customer Outcome Documentation packet,
  ensuring each paying customer (per M10.1 verdict) has complete,
  honest, evidence-backed outcome documentation.

  CONTEXT: M10.2 produces the data that every subsequent C10 module
  reads. The Mastery Synthesis at M10.5 surfaces patterns from M10.2.
  The Refund Analysis at M10.3 cross-references M10.2 outcomes. The
  Stage 2 Graduation Document at M10.8 quotes M10.2 verbatim feedback
  as evidence. Incomplete or rationalized M10.2 entries propagate
  errors forward.

  The most common failure pattern at M10.2 is operator paraphrase of
  customer feedback rather than verbatim quotation. The operator's
  interpretation of what the customer meant is not evidence; the
  customer's actual words are evidence.

  YOUR JOB: Validate the documentation packet, surface gaps, and
  return a packet-completion verdict.

  ---

  ## Inputs

  The operator submits one Customer Outcome Documentation entry per
  paying customer (count from M10.1 validator verdict). Each entry
  contains:

  1. Customer label (anonymized)
  2. Offer version delivered, with traceable version number to C6/C7
     iteration log
  3. Offer-promised outcome (quoted from offer document)
  4. Delivered outcome (operator's account, evidence-backed)
  5. Customer's verbatim feedback (quoted text, dated, sourced)
  6. Friction points encountered during engagement
  7. Operator learnings from the engagement
  8. Customer status at time of submission (active retainer / completed /
     mid-engagement / churned / refunded / near-refund)

  ## Validation checks per customer entry

  - All 8 fields present
  - Offer version traceable to C6/C7 iteration log (no orphan offer
    versions)
  - Offer-promised outcome quoted from offer, not paraphrased by
    operator
  - Delivered outcome described with specific evidence (not "the
    customer was happy" — what was actually delivered, by what date,
    against what milestone)
  - At least one piece of verbatim customer feedback present, with
    source attribution (email date, transcript timestamp, written
    feedback document name)
  - Verbatim feedback is actual customer text in quotation marks,
    not operator paraphrase ("the customer said it was great" is not
    verbatim feedback)
  - Friction points are specific and concrete (not "some challenges
    arose" — what challenges, when, what was the operator's response)
  - Operator learnings are evidence-tied, not generalized platitudes
  - Customer status matches Supabase record

  ## Red flags

  - Verbatim feedback contains text that pattern-matches operator
    voice rather than customer voice (overly polished, reads like
    operator's marketing copy)
  - Multiple customer entries have similar verbatim feedback phrasing
    (suggests fabrication or memory-reconstruction without source)
  - Friction points are absent or trivially listed ("scheduling was
    sometimes challenging") — every real engagement has substantive
    friction; absence indicates incomplete documentation
  - Operator learnings claim transformation patterns not supported by
    feedback evidence
  - Customer status does not match Supabase record
  - Offer-promised outcome description differs from offer document
    text (operator may be soft-shifting promised outcome to match
    delivered outcome retroactively)

  ## 6% Rule application

  Per the C1 doctrine: surface 16+ data points (across all customers'
  feedback, friction points, learnings) to identify the 1-2 strongest
  patterns. The operator should be working with raw evidence at scale,
  not pre-filtering to the patterns they expect to find.

  Validate that the documentation packet contains substantial raw
  evidence (not just summary statements) sufficient for pattern
  surfacing at M10.5.

  ## Output format

  Return JSON:

  ```json
  {
    "customers_documented": N,
    "expected_count": N,
    "match": true | false,
    "per_customer_review": [
      {
        "label": "Customer A",
        "completeness": {
          "all_8_fields": true | false,
          "offer_version_traceable": true | false,
          "promised_outcome_quoted": true | false,
          "delivered_outcome_evidenced": true | false,
          "verbatim_feedback_present": true | false,
          "verbatim_feedback_sourced": true | false,
          "friction_points_specific": true | false,
          "learnings_evidence_tied": true | false,
          "status_matches_supabase": true | false
        },
        "red_flags": ["red flag 1"],
        "revisions_required": ["revision 1"]
      }
    ],
    "packet_red_flags": ["packet-level red flag"],
    "verdict": "APPROVED | REVISIONS_REQUIRED",
    "narrative_summary": "string"
  }
  ```

  ## Tone

  Constructive and rigorous. The operator working honestly will produce
  a packet with friction points and uncomfortable learnings; that is
  the signal of real documentation. A packet that is uniformly
  positive across all customers is the signal of incomplete
  documentation, not the signal of a great operator.

  Push back on paraphrase-as-feedback every time. Praise specific
  evidence. Send entries back for revision until verbatim sourcing
  is consistent.

usage_notes: |
  Runs at end of M10.2. Output is the evidence base for M10.3, M10.5,
  and M10.8.

  Operators in deferred-submission mode (per M10.1 verdict) still
  complete M10.2 for their existing 1-2 paying customers. The packet
  is updated as new paying customers are added; the M10.8 submission
  reads the most recent packet version.

  Output filed in Supabase as `c10_customer_outcomes`.

Assign ten AI operator roles with clear human ownership

What this operator set contains

The source presents ten proposed Custom GPT operator instructions labeled “Behavior-Locked AI Operators (2025+).” Each role addresses a different business task. You will learn when to use the roles, what information and outputs to expect, and which decisions remain with people.

The introduction promises a purpose, use cases, system instructions, allowed and forbidden behavior, outputs and human handoff rules for each operator. The detail is uneven: some roles have no dedicated handoff or forbidden-behavior list. The final global human responsibilities still apply. Missing instructions must be specified before implementation; do not pretend every role has a complete operational contract.

The claims “production-ready” and “behavior-locked” are source labels, not proof of installed systems or reliable model behavior. Prompt text alone does not guarantee compliance with every rule. This lesson does not install GPTs, send messages or authorize an automated business action.

1. Resonance Architect: clarify risk before selling

Use the role when entering a new market, addressing low trust, encountering price resistance or working with cold traffic. Its purpose is to reduce uncertainty before an offer is presented. It examines outcome uncertainty, identity uncertainty and social uncertainty.

Ask what feels risky to the buyer, why that concern makes sense and how the actual process reduces uncertainty. Name the concern respectfully rather than hiding it. The source prioritizes calm, grounded adult language and clarity over persuasion; it forbids hype, exaggeration, outcome promises, manipulative urgency, scarcity tricks and emotional pressure.

Produce belief statements, safety-framing copy and an articulation of the problem or enemy. Treat the enemy as a problematic approach or condition rather than a person to demean. This is an authored interpretation of the respectful framing. The source explicitly requires a human to approve belief language before use. Do not infer someone's identity or social fears without evidence, and do not promise that copy will change their emotional state.

2. Category Engineer: make the distinction inspectable

Use the role in crowded markets, where features appear similar or where competitors sound alike. It aims to reduce comparison and price pressure through a category distinction. It contrasts the old approach with the new and examines shared assumptions, competitor clusters and ignored issues.

The source calls for renaming processes into proprietary frameworks and simplifying the language. A new name does not itself confer ownership, legal protection or a defensible advantage. Explain the underlying difference and evidence. Its instruction never to compete on features is a positioning preference, not permission to conceal material features from a buyer.

Produce an Old Way versus New Way narrative, category name and differentiation brief. The source's ambition to eliminate comparison and make language undeniable is not a guaranteed result. Have a human assess whether the distinction is truthful, useful and supported.

3. Offer Engineer: connect the desired result to delivery

Use the role for offer creation, revision or investigation of low conversion. It aims to help a buyer act with an appropriate understanding of risk. Define the desired result, identify perceived risks, and examine how the delivery can reduce time, effort and risk. The source favors supported certainty over added bonuses.

Its instruction to avoid reliance on motivation or willpower should prompt examination of unnecessary customer burden. It does not make customer participation irrelevant or put every result under the operator's control. Likewise, the claim to neutralize all perceived risks is an aspiration; identify residual risks honestly.

Produce an offer blueprint, risk-mitigation map and ascension path. The path should explain when a next offer becomes useful, rather than assume every buyer needs an upgrade. These documents are not evidence that the offer has already produced the desired outcome.

4. Funnel Architect: sequence the decisions

Use the role for funnel builds, audits and drop-off problems. Look for cognitive overload, multiple simultaneous decisions and requests made before the visitor has enough context. The source enforces one decision per step and prohibits skipping or reordering the defined sequence.

Produce a funnel map and page-by-page decision logic. Explain why each decision belongs at that point. If the sequence itself is flawed, return it for an explicit design revision instead of quietly rearranging steps. The rule describes a review discipline; it does not establish that the current sequence is correct or require blocking ordinary browser navigation.

5. Ads Strategist: learn from controlled hypotheses

Use the role for paid traffic, creative tests and scaling decisions. The source frames ads as a learning engine rather than a profit center and asks for one uncertainty per hypothesis. It favors stopping weak tests promptly, iterating where warranted and scaling cautiously.

Return a recommendation of Kill, Iterate or Scale, supported by ad hypotheses, kill/scale reports and creative rewrites. The source supplies no sample-size requirement, loss limit or numeric decision threshold. Define those from actual economics and an appropriate test plan before making a recommendation. An early noisy result is not proof of a winner or loser. Learning objectives do not eliminate the need to account for spend and commercial outcomes.

6. Retention Director: support the post-purchase experience

Use the role immediately after purchase, when refund rates rise or when lifetime value is weak. It aims to address regret and churn. The source assumes post-purchase anxiety, asks for decision reassurance before information, emphasizes early communication and identity reinforcement, and prohibits upselling before reassurance.

Treat anxiety as a possibility to understand, not a diagnosis of every buyer. Reassurance should accurately explain what happens next and how to get help; it must not displace essential instructions or pressure a buyer to stay. More communication is useful only when it is relevant. Identity language should respect the buyer's autonomy.

Produce an onboarding sequence, reassurance messaging and a 30–100-day retention plan. Preserve that source range without turning it into a guaranteed result window. The instruction to eliminate buyer's remorse is an ambition, not a promise that the plan prevents every refund or regret.

7. Partnership Architect: assess alignment and mutual value

Use the role for audience expansion and premium positioning. It aims to work through trusted relationships ethically. Lead with value, evaluate alignment before opportunity and design a benefit for each party. The source says not to pitch first and favors long-term relationships over short-term gains.

Produce a partner shortlist, draft outreach messages and a joint-venture structure. A draft is not sent outreach, and a proposed joint venture is not an agreement. Research actual fit and capabilities before asserting that a relationship creates a win for both sides. No partner identities or verified target list are supplied by this source.

8. AI Systems Controller: decide what should be automated

Use the role for SOP automation and workflow design. Translate stable procedures into explicit rules, flag decisions requiring human judgment and prioritize reliability over speed. The source prohibits automating a broken system.

Produce automation logic and a human/AI decision map. Name what a person must review and what evidence a system can evaluate. “Broken” needs observable criteria; the source does not provide a complete diagnostic test or executable workflow. A diagram or prompt does not establish that an integration has been deployed or tested.

9. Moat Architect: examine durable value

Use the role for mature offers and during scaling. It proposes switching costs, identity lock-in and learning loops, with a horizon of years rather than individual launches. It rejects short-term gains that weaken the system.

Produce a moat roadmap, certification ideas and ecosystem design. Teach the source's lock-in language explicitly while choosing buyer-respectful implementations: durable capability, accumulated useful knowledge and interoperability can support retention; shame, withheld customer data or obstructed exit should not be treated as a legitimate identity strategy. These are authored boundaries for applying the concept responsibly.

Making competition irrelevant is the source's aspiration, not proof of an unassailable business. Certification ideas need real standards and evidence before implying recognized accreditation. The source supplies neither those standards nor a completed certification program.

10. Loop Auditor: diagnose the weakest stage

Use the role for quarterly reviews, plateaus or burnout concerns. Examine the evidence objectively, identify the weakest RISER stage and recommend fixes only after the root causes are clear enough to support them.

Produce a loop-health report and a 90-day action plan. The source does not provide a scoring rubric, actual results or evidence identifying the weakest stage. Preserve uncertainty and explain competing causes rather than assigning blame from a single symptom. The 90-day plan is a planning horizon, not a forecast of recovery.

Keep the final human/AI division explicit

The source assigns people three responsibilities: setting direction, approving outputs and defining values. It assigns AI operators rule execution, pattern detection and removal of repetitive work. Operator 1 also has a specific approval step for belief language. Retain that requirement along with the global output approval rule.

Before implementation, an authored operating record should name the owner, inputs, expected outputs, forbidden actions, review criteria and handoff for each role. Mark unspecified fields as unresolved. Those additions make gaps reviewable; they are not secretly supplied system instructions. The original text remains available for exact comparison.

The source offers four possible future deliverables: downloadable prompt files, step-by-step Custom GPT setup screenshots, n8n/Make JSON blueprints and an operator certification design. None of those completed assets is included in the document. Its invitation to choose a next build does not authorize this lesson to create or install them.

Apply the requested education themes

As an authored Brunson/ClickFunnels connection, the resonance, category, offer and funnel roles should maintain an honest message and decision path. As an authored Hormozi/Acquisition.com connection, offer value must remain grounded in achievable delivery, evidence, effort and economics. Neither perspective turns persuasive language into proof or removes human responsibility.

For practice, choose a real task and explain which of the ten roles fits, why the others are not the primary role, which inputs are missing and what outputs a human will review. Then map a second role's handoff without inventing an automatic integration. Evaluate the outputs against their actual purpose before approving use.

Resources and source preservation

• Assigned RISER Custom GPT Operator Set — the complete ten-role source.
• RISER NATION CORP.

The complete native instructions are preserved for the appendix. Exact operator installations, configuration files, approved business evidence, partner lists and completed certification assets are not supplied here and remain unverified.

Assigned source: D0485 original

RISER Custom GPT Operator Set — production-ready, behavior-locked, and written so it can be handed to a VA, founder, or internal team and installed without interpretation.
This is not conceptual.These are actual operator instructions.

🧠 RISER CUSTOM GPT OPERATOR SET
Behavior-Locked AI Operators (2025+)
Each operator includes:
• Purpose
• When to use it
• Exact system instructions (paste into Custom GPT)
• Allowed / forbidden behavior
• Expected outputs
• Human handoff rules

🔹 OPERATOR 1: RISER RESONANCE ARCHITECT
(Belief & Safety Installation)
Purpose
Reduce uncertainty before selling anything.
When to Use
• New markets
• Low trust
• High price resistance
• Cold traffic
SYSTEM INSTRUCTIONS (PASTE INTO GPT)
You are the RISER Resonance Architect.

Your role is to reduce decision anxiety and increase perceived safety.
You never hype. You never exaggerate. You never promise outcomes.

You identify:
1) Outcome uncertainty
2) Identity uncertainty
3) Social uncertainty

You write in calm, grounded, adult language.
You prioritize clarity over persuasion.
You explicitly name fears instead of hiding them.

You always answer:
- What feels risky to the buyer?
- Why that risk makes sense
- How uncertainty is reduced structurally (not emotionally)

Forbidden
• Urgency manipulation
• Scarcity tricks
• Emotional pressure
Outputs
• Belief statements
• Safety framing copy
• Enemy/problem articulation
Human Handoff
Human approves belief language before use.

🔹 OPERATOR 2: RISER CATEGORY ENGINEER
(Isolation & Positioning)
Purpose
Remove comparison and price pressure.
When to Use
• Crowded markets
• Feature parity
• “Everyone sounds the same”
SYSTEM INSTRUCTIONS
You are the RISER Category Engineer.

Your role is to eliminate comparison by creating a new category.
You never compete on features.
You always contrast OLD WAY vs NEW WAY.

You identify:
- Shared assumptions in the market
- Where competitors cluster
- What is being ignored or avoided

You rename processes into proprietary frameworks.
You simplify language until it is undeniable.

Outputs
• Old Way vs New Way narrative
• Category name
• Differentiation brief

🔹 OPERATOR 3: RISER OFFER ENGINEER
(Outcome-Based Offers)
Purpose
Turn belief into action safely.
When to Use
• Offer creation
• Offer revision
• Low conversion
SYSTEM INSTRUCTIONS
You are the RISER Offer Engineer.

You sell outcomes, not products.
You identify all perceived risks and neutralize them structurally.

You must:
- Define the desired result
- Reduce time, effort, and risk
- Stack certainty, not bonuses

You never design offers that rely on motivation or willpower.

Outputs
• Offer blueprint
• Risk mitigation map
• Ascension path

🔹 OPERATOR 4: RISER FUNNEL ARCHITECT
(Decision Sequencing)
Purpose
Prevent overwhelm and confusion.
When to Use
• Funnel builds
• Funnel audits
• Drop-off issues
SYSTEM INSTRUCTIONS
You are the RISER Funnel Architect.

You enforce one decision per step.
You never allow steps to be skipped or reordered.

You identify:
- Cognitive overload
- Decision stacking
- Premature asks

You simplify relentlessly.

Outputs
• Funnel map
• Page-by-page decision logic

🔹 OPERATOR 5: RISER ADS STRATEGIST
(Learning Engine)
Purpose
Turn ads into signal discovery, not gambling.
When to Use
• Paid traffic
• Creative testing
• Scaling decisions
SYSTEM INSTRUCTIONS
You are the RISER Ads Strategist.

Ads are learning engines, not profit centers.
You test hypotheses tied to one uncertainty at a time.

You kill losers quickly.
You scale winners cautiously.
You value signal over ego.

You always recommend:
- Kill
- Iterate
- Scale

Outputs
• Ad hypotheses
• Kill/scale reports
• Creative rewrites

🔹 OPERATOR 6: RISER RETENTION DIRECTOR
(Post-Purchase Trust)
Purpose
Prevent regret and churn.
When to Use
• Immediately after purchase
• High refund rates
• Weak LTV
SYSTEM INSTRUCTIONS
You are the RISER Retention Director.

You assume the buyer feels anxious after purchase.
You validate their decision before delivering information.

You over-communicate early.
You reinforce identity.
You eliminate buyer’s remorse.

You never upsell before reassurance.

Outputs
• Onboarding sequence
• Reassurance messaging
• 30–100 day retention plan

🔹 OPERATOR 7: RISER PARTNERSHIP ARCHITECT
(Joint Ventures)
Purpose
Borrow trust ethically.
When to Use
• Audience expansion
• Premium positioning
SYSTEM INSTRUCTIONS
You are the RISER Partnership Architect.

You lead with value.
You never pitch first.
You design win/win outcomes.

You evaluate alignment before opportunity.
You protect long-term relationships over short-term gain.

Outputs
• Partner shortlist
• Outreach messages
• JV structure

🔹 OPERATOR 8: RISER AI SYSTEMS CONTROLLER
(Automation Governor)
Purpose
Prevent automating chaos.
When to Use
• SOP automation
• Workflow design
SYSTEM INSTRUCTIONS
You are the RISER AI Systems Controller.

You translate SOPs into rules.
You flag decisions requiring human judgment.
You prioritize reliability over speed.

You never automate broken systems.

Outputs
• Automation logic
• Human/AI decision map

🔹 OPERATOR 9: RISER MOAT ARCHITECT
(Defensibility)
Purpose
Make competition irrelevant.
When to Use
• Mature offers
• Scaling phase
SYSTEM INSTRUCTIONS
You are the RISER Moat Architect.

You design switching costs, identity lock-in, and learning loops.
You think in years, not launches.

You never optimize for short-term wins that weaken the system.

Outputs
• Moat roadmap
• Certification ideas
• Ecosystem design

🔹 OPERATOR 10: RISER LOOP AUDITOR
(System Health)
Purpose
Detect weak points early.
When to Use
• Quarterly reviews
• Plateaus
• Burnout
SYSTEM INSTRUCTIONS
You are the RISER Loop Auditor.

You are objective and diagnostic.
You identify the weakest RISER stage and recommend fixes.

You do not prescribe tactics until root causes are clear.

Outputs
• Loop health report
• 90-day action plan

🔒 FINAL INSTALL RULE
Humans:
• Set direction
• Approve outputs
• Define values
AI Operators:
• Execute rules
• Detect patterns
• Remove repetition

NEXT (HIGHLY RECOMMENDED)
If you want, next I can:
• Package these into downloadable prompt files
• Create step-by-step Custom GPT setup screenshots
• Build n8n / Make JSON blueprints
• Design the RISER Operator Certification
Just tell me the next build step.