Capstone 13: End-to-End Reddit Automation System (Human-in-the-Loop)
Goal: Integrate Capstones 8, 10, 11, and 12 into one governed pipeline, monitoring, drafting, humanizing, citation-tracking, culminating in a single human-review queue, run live for at least two full weeks.
Prerequisite stages: all of 01-stage1-foundations.md through 06-stage6-claude-operating-system.md, plus Capstones 8, 10, 11, and 12 completed.
Weekly milestones: Week 1 integrate the components and produce a full architecture diagram; Week 2 dry run; Weeks 3-4 live run with weekly post-mortems, closing with a governance memo.
Deliverables: the full architecture diagram (built on Stage 6's monitoring-to-human-gate loop); the integrated repo; a two-week live-run log; a governance memo naming the specific human who holds the review gate; an honest incident/near-miss log.
| Criterion | Points |
|---|---|
| Integration completeness (all four component systems wired together) | 20 |
| Live-run evidence (two full weeks, not a single day) | 25 |
| Governance memo quality (named human, cadence, restated red-lines) | 20 |
| Incident handling and honesty (at least one documented near-miss) | 15 |
| Zero-automation-of-publishing compliance, pass/fail gate: any evidence of auto-posting, auto-replying, auto-voting, or auto-DMing zeroes this capstone regardless of other scores | 20 |
| Total | 100 |
Claude workflows: the complete Stage 6 pipeline, scheduled trigger, research subagents, intent scoring, drafting skill, humanization pass, competitor and citation monitoring, weekly digest, human review gate, manual posting, KPI feedback loop.
Tools: Claude Code, Reddit MCP server, Skills, Stage 5 KPI dashboard, and every tool from the prior twelve capstones.
The 90-Day Execution Roadmap
This is the schedule a serious operator actually runs, weaving all thirteen capstones together instead of doing them in isolation. Weeks 1-12 map to roughly the first 90 days; Capstone 13's two-week live run is deliberately allowed to extend a few days past day 90 rather than be rushed, a compliance-graded live run is not something to compress for a deadline.
| Week | Days | Active capstones | Key milestone this week | Gate check |
|---|---|---|---|---|
| 1 | 1-7 | 1, 2, 3 | Account audited, karma baseline set, ICP subreddit seed list (10) drafted | Ethics line restated in writing before any posting begins |
| 2 | 8-14 | 1, 2, 3, 9 | 20 comments logged; subreddit map expanded to 20-25; profile rewrite drafted | Disclosure language finalized |
| 3 | 15-21 | 3, 4, 5 | Subreddit map validated via 5 test posts/comments; post portfolio drafts 1-2 written | 80/20 reply structure applied to first logged comments |
| 4 | 22-28 | 4, 5, 11 | First post batch published; content calendar built | Karma checkpoint ~250 (Capstone 2) |
| 5 | 29-35 | 6, 7 | Launch venue and post drafted; citation-target queries selected | AMA request drafted (not yet sent) |
| 6 | 36-42 | 6, 8 | Launch week executed; lead-funnel monitoring routine built | Launch-week reply-speed log complete |
| 7 | 43-49 | 6, 7, 10 | Launch follow-up + AMA outreach sent; citation content published; competitor list defined | First competitor brief shipped |
| 8 | 50-56 | 2, 5, 8 | Karma checkpoint ~600; comment log at 50+; funnel cycle #3 run | DM etiquette log reviewed for automation red flags |
| 9 | 57-63 | 7, 10, 12 | First citation check run across all 3 engines; second competitor brief; Claude workflow scoping begins | Citation volatility memo drafted |
| 10 | 64-70 | 5, 8, 12 | Comment log reaches 100; Skills and slash command built | Slash command tested end to end |
| 11 | 71-77 | 10, 12, 13 | Third competitor brief; Claude workflow live-tested; Capstone 13 integration planning starts | Human-gate location confirmed in writing |
| 12 | 78-84 | 2, 9, 13 | Karma checkpoint 1,000+; peer review of founder profile; Capstone 13 dry run | Governance memo drafted |
| 13 | 85-90 | 13 | Capstone 13 live run begins; portfolio compilation across all prior capstones starts | Week-1 post-mortem of the live run |
| 14 (spillover) | 91-97 | 13 | Capstone 13 live run concludes at the full two weeks | Final governance memo submitted with incident log |
Final Assessment
Part A, 25 Exam Questions
These span every prior stage. Answer in your own words, citing the specific study, founder, or figure the course associates with each claim, a correct number with no source attached is a partial answer.
Mechanics & Algorithm (1-5)
- What is Reddit's Contributor Quality Score, and by what multiplier does an established high-CQS account reportedly outrank a similar post from a new account (Reddit's September 2025 update)?
- State the karma benchmarks and timelines for "Experienced" and "Power" tier accounts, and name the source.
- Why does Community Karma (per-subreddit) carry more weight with moderators than sitewide karma?
- What two thread-level signals maximize the visibility of a reply, and by what multiplier does reply speed matter?
- Name the enforcement ladder from mildest to most severe consequence for a policy-violating account.
Ethics & Compliance (6-10) 6. State the current operating norm that replaced Reddit's retired 90/10 self-promotion rule, and name at least one subreddit-type where an even stricter ratio applies. 7. What is the correct disclosure phrasing this course requires before any product mention in a reply, and why does it matter more than the promotional content itself? 8. Describe the black-hat 1,000-account experiment from the CMSWire case study: what did it do, what result did it produce, and why is it disqualifying regardless of the result? 9. What did the Wappkit founder's fake-account "stealth marketing" attempt actually trigger, and what is the lesson for account structure? 10. Why does Reddit's content-manipulation policy treat "requesting upvotes anywhere, including off-platform" as a violation even when no bots are involved?
GEO / AI Citations (11-15) 11. Name two of the three AI answer engines in which Reddit is a top-cited domain, with the approximate citation share reported for each (Profound's study, via CMSWire). 12. What did Conductor document about Reddit's citation-share volatility in a single month, and what happened to Perplexity's Reddit citation share after Reddit sued it? 13. What did Diggity Marketing's case study report for a real-estate-data client's Reddit referral traffic and AI referral traffic growth, year over year? 14. Why is a Reddit thread or comment a durable citation asset compared to a paid ad, in terms of decay over time? 15. What is the risk of building a growth strategy that depends heavily on AI-citation volume from a single platform, and how should a founder hedge it?
Lead Gen & Launches (16-20) 16. What documented DM response rate did OneUp Today achieve, and what was the one condition that separated high-performing DMs from generic ones that fell below 20%? 17. Why does niche subreddit targeting (3-5 subs) reportedly outperform broad targeting for B2B lead generation, and by what figure (SaaS Hero)? 18. Describe the "r/SideProject trap" and name at least one subreddit category that converts better for actual paying customers. 19. What launch-post formats reliably outperform a plain feature announcement, and why? 20. What did the $200 Reddit-ad-spend result reveal about paid vs. organic acquisition for a cold indie launch (Indie Hackers)?
Automation & Claude (21-25) 21. What specifically shut down GummySearch's commercial service on November 30, 2025, and what should a builder conclude from that event about tooling strategy generally? 22. In Anthropic's Agent Skills model, what is "progressive disclosure," and why does it let a Reddit-ops system run a dozen Skills without bloating every conversation? 23. Name the three MCP primitives and, for each, give one Reddit-ops example of how it would be used. 24. In a Claude Project's custom instructions, what should always be the first rule, and why does field ordering matter to how Claude weighs instructions? 25. Draw or describe, from memory, the full human-in-the-loop pipeline from Stage 6: name every stage from trigger to KPI feedback, and state exactly where the human review gate sits and why it cannot move downstream of publishing.
Part B, Practical Exam Spec
The written exam proves recall. The practical exam proves you can execute under the same constraints as a real operating day. Run all four practical stations, each independently timed and graded; total score is the average of the four, with any ethics violation in any station zeroing that station's score outright.
| Station | Task | Time limit | Graded on |
|---|---|---|---|
| 1. Triage | Given 10 raw, unlabeled Reddit thread excerpts, score each for buying intent (0-100) and draft one 80/20 reply for the top 3 | 30 min | Scoring accuracy vs. instructor key, reply structure compliance, disclosure presence |
| 2. Subreddit fit | Given a new product description and 5 candidate subreddits, rank them by fit and promo tolerance and justify each ranking | 20 min | Correct tiering logic, evidence cited (rules, size, recent top posts) |
| 3. Launch post | Draft one launch post following the numbers/story-angle standard for a given fictional SaaS, correctly formatted for a specified subreddit's posting rules | 25 min | Archetype correctness, subreddit-rule compliance, absence of feature-dump framing |
| 4. Governance | Given a partially built automation pipeline diagram with the human review gate misplaced downstream of publishing, identify the error and redraw the correct gate placement with a one-paragraph justification | 15 min | Correct gate placement, clarity of justification, no missed automation risk |
A passing practical exam requires at least 75/100 average across the four stations with zero ethics-gate failures. A station-level ethics failure (an undisclosed mention, an "act as if you are a customer" framing, an automated-posting design) is not curved, retake that station only after a documented remediation conversation with the instructor.
Scaling: From Solo Founder to Team
Every capstone above assumes one operator. Most of the case studies grounding this course, Czerny, Chaturvedi, Chen, Rintala, ran their early Reddit programs as a single founder, and the realistic-expectations data backs that up: meaningful organic results generally require 10-20 hours per week sustained for at least six months (Reddit Marketing Masterclass; SubredditSignals). That ceiling is the actual signal to hire against, not revenue, not a vanity headcount target, but the moment your monitoring, drafting, and reporting workload exceeds what one disciplined person can hold inside that weekly budget without the quality (and therefore the ethics compliance) slipping.
When to hire. Three concrete triggers, any one of which is sufficient: (1) your intent-monitoring log in Capstone 5/8 shows response times consistently missing the first-hour window because there is more volume than one person can triage; (2) your content engine (Capstone 11) misses its weekly cadence twice in a row; (3) your competitor-intelligence briefs (Capstone 10) are more than a week stale because nobody has bandwidth to run the cycle. Hire into the specific bottleneck, not a generic "growth marketer" title.
Roles and what each owns. A mature Reddit operation splits into four functions, each mapped directly to capstones above:
- Community/engagement lead, owns Capstones 1, 2, 5, 9: the account, the karma trajectory, the comment log, the founder profile. This is almost always the founder for as long as the disclosed-founder-account pattern (the version every credible case study in this course uses, versus the faceless brand accounts that consistently underperform) stays the operating model.
- Content and launch lead, owns Capstones 4, 6, 11: the post portfolio, launch execution, and the weekly content engine.
- Growth/lead-gen lead, owns Capstones 3, 7, 8: subreddit mapping, AI-citation work, and the lead funnel, with direct visibility into the KPI dashboard from Stage 5.
- Automation/ops engineer, owns Capstones 10, 12, 13: the Claude Code repo, the Skills library, the MCP server configuration, and the governance memo itself.
SOP handoff. Do not hand a new hire a verbal briefing and your Slack history. Hand them the artifacts this stage already forced you to produce: the subreddit map (Capstone 3), the comment-log template and 80/20 reply standard (Capstone 5), the content calendar and template library (Capstone 11), and, critically, the CLAUDE.md and Skills repo from Capstone 12. That repo is not incidental infrastructure; treated correctly, it is your SOP, because it already encodes your brand voice, your disclosure language, your ratio targets, and your ethics red-lines in a form a new hire's Claude sessions inherit automatically rather than having to be retaught by a manager. This is the same "define once, reference everywhere" principle Stage 6 taught for your own knowledge base, at team scale, it is the difference between onboarding taking a week and onboarding taking an afternoon.
Governance at scale is the hard part, not the tooling. Every additional person touching Reddit on the company's behalf is another account that must be individually disclosed, individually trained on the 95/5 (or stricter) ratio, and individually bound by the same human-review gate Capstone 13 required of a solo operator's automation. The single biggest scaling failure mode this course's research surfaces is not a technical one, it's a team quietly reverting to faceless "brand voice" posting once more than one person is involved, exactly the pattern that OG Tool and every founder case study in this program identifies as the reason brand accounts underperform disclosed individual ones. Your governance memo template from Capstone 13 should be a living document that names, by name, every human account operating on the company's behalf, their assigned subreddits, and who holds the review gate for each, reviewed and re-signed every quarter, the same cadence Stage 5 already taught you to audit your KPI dashboard and tooling stack against.
The scaling test that matters: if you handed your entire Capstone 12/13 repository plus your Capstone 3, 5, and 11 artifacts to a new hire with zero verbal briefing, could they run one week of the operation correctly, right subreddits, right ratio, right disclosure, right human gate, using only what's written down? If the honest answer is no, you have not built a scalable operation; you have built a habit that lives in your own head, which is exactly the single-point-of-failure this entire course, and Stage 6 in particular, was built to eliminate.
Stage 7 / Course Completion Checklist
- All chosen capstones (minimum: 1-5 and 9; full scope: all 13) submitted as dated, evidence-backed folders, no capstone graded on prose claims alone.
- Every rubric's ethics/disclosure line scored honestly, with any automation-of-publishing violation reported and zeroed, not hidden.
- 90-day roadmap actually run and logged week by week, including the Capstone 13 two-week live run.
- Written exam (25 questions) completed with sources named for every factual claim, not just the number.
- Practical exam passed at 75/100+ average across all four stations with zero ethics-gate failures.
- Governance memo on file naming a specific human as the review-gate holder, current within the last quarter.
- If scaling beyond solo: SOP handoff artifacts (subreddit map, comment-log standard, content calendar, CLAUDE.md/Skills repo) actually tested against a new-hire "cold start" scenario.
- Can restate, from memory and without notes, the single sentence this entire course has been building toward: Claude drafts, scores, classifies, and summarizes, it never posts, replies, votes, or DMs on your behalf, and that line does not move as you scale.