--- name: happycouple-reddit-research description: "Build and maintain HappyCouple's Reddit pain-mining engine: subreddit discovery, post sampling, taxonomy tagging, Obsidian artifacts, and conversion into marketing/product assets." tags: - happycouple - reddit - marketing-research - pain-mining - obsidian - consumer-ai --- # HappyCouple Reddit Research ## New reference artifacts - `references/busy-moms-reddit-problem-map.md` — reusable subreddit map, pain taxonomy, and product-wedge interpretation for busy moms / default-parent family-logistics research. Use when the parent/mom persona overlaps HappyCouple or a broader Consumer AI family-ops opportunity. - `references/happycouple-reddit-trust-loop-2026-05-17.md` — session-derived playbook for verifying visibility before pausing, reading qualitative reactions, prioritizing reply-to-replies, adding guarded self-posts, and introducing controlled UTM-tracked links without burning trust. - `references/emma-reddit-link-bearing-style-correction.md` — user-corrected Emma-era Reddit pattern: fix formulaic writing in-loop instead of pausing safe loops, split no-link trust/research from guarded link-bearing traffic, explicitly name Emma/HappyCouple and the website where allowed, and measure traffic by activation rather than helpful comments. ## When to use Use this skill when Antoine asks to: - Research Reddit for HappyCouple marketing, acquisition, positioning, SEO, or product insights. - Find relevant subreddits for relationship/dating/marriage pain mining. - Mine Reddit posts for recurring relationship moments. - Create or update Obsidian notes from HappyCouple Reddit research. - Turn Reddit pain into homepage prompt chips, SEO ideas, short-form scripts, ad hooks, or product test prompts. - Maintain a reusable research pipeline rather than answering with one-off strategy. ## Core stance Reddit is primarily a pain-mining, content, SEO, and organic community-learning channel for HappyCouple — not a direct organic self-promotion channel. Current Antoine preference: do not prioritize paid ads before a payment mechanism exists. Payment is not the current priority, so HappyCouple Reddit work should focus on organic learning: useful comments, language mining, content/creator ideas, and source-attributed traffic. Most relevant communities ban or strongly discourage self-promotion, advertising, surveys, commercial links, app drops, AI-generated comments, or low-effort resource posts. Use Reddit as the place where the market writes the copy. The repeated pain to look for: ```text I don't know if I'm wrong, I don't know what this means, and I don't know what to say without making it worse. ``` The marketing implication: ```text Get the next sentence right. ``` Do not reposition HappyCouple as “AI couples therapy” when using Reddit insights. Keep collapsing toward acute relationship moments. ## Primary subreddit set Track these first: 1. r/relationship_advice 2. r/AmIOverreacting 3. r/dating_advice 4. r/Marriage 5. r/relationships 6. r/LongDistance 7. r/DeadBedrooms 8. r/datingoverthirty 9. r/BreakUps 10. r/Tinder 11. r/texts 12. r/AskWomenOver30 13. r/AskMenAdvice 14. r/Parenting 15. r/Mommit 16. r/AnxiousAttachment 17. r/attachment_theory 18. r/survivinginfidelity 19. r/MarriageAdvice 20. r/ExNoContact For the first automated mining sample, use the top 10: ```text relationship_advice AmIOverreacting dating_advice Marriage relationships LongDistance DeadBedrooms BreakUps texts datingoverthirty ``` ## Existing pipeline / don't reinvent it HappyCouple already has a Reddit pain-mining and guarded Reddit ops stack. When Antoine asks how to improve research, whether a Reddit pipeline exists, or whether to add Reddit pain mining, **verify and build on the existing pipeline instead of recommending a new one from scratch**. Current pattern: - Research/pain mining exists via `happycouple_reddit_mining.py` and the unified factory `reddit_mining.py` script. - Draft/comment/traffic loops exist separately from research mining. - The right improvement path is usually: refresh outputs, inspect recent CSV/notes, improve semantic curation, connect clusters into product/GTM artifacts, and repair scheduled loop/runtime failures if cron is degraded. - Distinguish clearly between: - **Reddit miner** = pain language and acute relationship moments. - **Guarded Reddit traffic loop** = comments/replies/link-bearing tests with account/community safety. - **Exa/SERP/X/App Store research** = complementary discovery surfaces, not replacements for Reddit pain mining. If a scheduled HappyCouple Reddit loop is enabled but failing, report that as an operational/runtime issue around the loop, not as absence of the pipeline. Check cron outputs for shared model/provider errors before blaming Reddit auth or the scripts. ## Existing artifacts Master Obsidian note: ```text /Users/antoinelevy/Documents/Obsidian Vault/Consumer AI Company Factory/05 Ventures/Venture 001 - HappyCouple/02 Research/Reddit/HappyCouple - Reddit Marketing Research.md ``` First mining run summary: ```text /Users/antoinelevy/Documents/Obsidian Vault/Consumer AI Company Factory/05 Ventures/Venture 001 - HappyCouple/02 Research/Reddit/HappyCouple Reddit Mining - 2026-05-08.md ``` First 100-post CSV: ```text /Users/antoinelevy/Documents/Obsidian Vault/Consumer AI Company Factory/05 Ventures/Venture 001 - HappyCouple/02 Research/Reddit/happycouple-reddit-sample-2026-05-08.csv ``` Reusable mining script: ```text /Users/antoinelevy/.hermes/scripts/happycouple_reddit_mining.py ``` ## Running the mining script Before recommending that Antoine "add" a Reddit pain-mining pipeline, check whether the existing HappyCouple pipeline and artifacts already exist. Antoine may reasonably expect this to be known. Verify live paths/scripts first, then frame the work as improving freshness, semantic curation, reliability, or downstream product integration rather than reinventing the pipeline. Known current Linux-host paths may include: ```text /opt/mrhan/ops/mrhan-factory-ops/scripts/happycouple_reddit_mining.py /opt/mrhan/ops/mrhan-factory-ops/scripts/factory/reddit_mining.py /opt/mrhan/factory-vault/consumer-ai-factory-vault/HappyCouple/Reddit Research/ /opt/mrhan/factory-vault/consumer-ai-factory-vault/05 Ventures/Venture 001 - HappyCouple/02 Research/Reddit/ ``` Run: ```bash /Users/antoinelevy/.hermes/scripts/happycouple_reddit_mining.py ``` Optional env vars: ```bash POSTS_PER_SUB=10 REDDIT_LISTING=hot # hot | top | new REDDIT_TIME_FILTER=week # used for top REDDIT_USER_AGENT='HappyCoupleResearch/0.2 by Hermes' OBSIDIAN_VAULT_PATH='/Users/antoinelevy/Documents/Obsidian Vault' ``` The script outputs: - dated CSV under `HappyCouple/Reddit Research/` - dated Obsidian markdown summary under `HappyCouple/Reddit Research/` It uses public subreddit listing JSON, not authenticated Reddit API credentials. ## Important script caveat The current script's classification is keyword-based. Treat it as directional raw material, not clean truth. Known issue from the first run: - Some posts can be misclassified because keyword hits are shallow. - “general relationship conflict” was over-broad. - `r/AmIOverreacting` can include non-romantic posts, so filtering for romantic relationship terms matters. - The script was updated to include a romantic relationship regex filter and a larger listing fetch size, but manual/semantic curation is still required. Do not present the script output as final insight without reviewing sample rows. ## Taxonomy fields Each post should be tagged with: - subreddit - post title - post URL - relationship stage - moment type - user ask - emotional state - exact language - likely HappyCouple output - hook idea - SEO title idea - product prompt idea - safety flag - body excerpt Relationship stages: - dating - situationship - exclusive relationship - long-term relationship - marriage - long distance - new parents - breakup / ex - infidelity recovery - non-monogamous / poly Moment types: - apology / repair - am I overreacting / emotional calibration - texting / what to say - partner shuts down - chores / mental load - sex / intimacy - jealousy / insecurity - boundaries - family / in-laws - cheating / trust - commitment / exclusivity - recurring fight - general relationship conflict User asks: - What do I say? - Am I overreacting? - Am I wrong? - Should I leave? - How do I bring this up? - What does this mean? - How do I apologize? - How do I set a boundary? - How do I stop spiraling? - How do I repair this? Safety flags: - abuse / coercion - self-harm - medical / mental health - none detected ## First sample findings The first 100-post sample from 2026-05-08 returned this rough cluster distribution: ```text general relationship conflict: 25 sex / intimacy: 20 am I overreacting / calibration: 12 chores / mental load: 10 recurring fight: 9 apology / repair: 6 family / in-laws: 6 texting / what to say: 6 boundaries: 2 commitment / exclusivity: 2 jealousy / insecurity: 1 cheating / trust: 1 ``` Relationship stage distribution: ```text marriage: 40 dating: 18 relationship unspecified: 17 breakup / ex: 12 long distance: 8 infidelity recovery: 3 new parents: 2 ``` Direct interpretation: HappyCouple should not be just “text me what to say.” The richer wedge is: ```text Help me understand what is actually happening and handle the next conversation. ``` Strong recurring zones: 1. marriage resentment 2. intimacy/sex mismatch 3. “am I overreacting?” 4. household/mental load fights 5. recurring unresolved fights 6. repair/apology 7. breakup/ex spirals ## Organic distribution stance Do not over-optimize the HappyCouple agent conversation flow from theory before real users have tried it. If there is not enough feedback on actual AI conversations, prioritize traffic/trust learning instead. ### Reporting recent Reddit learnings When Antoine asks for “learnings lately from Reddit,” do not dump raw run logs, URLs, or comment counts unless he asks for audit detail. Synthesize the latest logs into **product/distribution primitives**: - What repeated user moment is appearing? - What exact language are people using? - What product output pattern does it imply? - What channel constraint did we learn? - What should change in copy, onboarding, or posting cadence? ### When Antoine asks for examples only If Antoine asks for “just the examples,” “examples,” “prompt chips,” or corrects with “just give me the examples,” respond with a clean bullet list of user-facing example inputs only. Do **not** include taxonomy labels, strategic explanation, product rationale, or extra commentary unless he asks for it. This is especially important when converting Reddit moments into homepage chips or onboarding examples. For HappyCouple, the most useful recurring frame from recent Reddit work is: users want a **small protocol**, not generic relationship advice. Good synthesis language: ```text People are not mainly asking for a verdict. They need: what is really happening, what not to say, one calm next sentence, one observable next step, and when to stop interpreting every signal. ``` Specific recent primitives to preserve: - `communication rhythm as hidden contract` — texting/update frequency often stands in for safety, interest, and respect. - `ambiguity → one observable decision point` — limbo/ghosting/soft rejection moments need one clean clarifier and a follow-through test. - `conflict order of operations` — validate impact first, then clarify intent/request, then propose one small agreement. - `AI-smell risk` — Reddit replies like “thanks chatgpt” indicate that public answers and product outputs must be more specific, shorter, and less templated. Keep the strategic distinction explicit: Reddit is currently strongest as a **market-language and product-research engine**, but if Antoine says traffic is too low, do not hide behind research-only motion. Add controlled, rules-safe link tests in feedback/showcase/tool-request contexts and explicitly mention the product/website when allowed. ### Antoine correction: “post more with the link” When Antoine explicitly pushes for more `happycouple.ai` links, treat it as an instruction to increase link-bearing execution, not just to continue the cautious no-link loop. Operational pattern: 1. During the same session, look for a link-safe surface first: r/betatests / r/TestMyApp / r/alphaandbetausers / r/SideProject-style product-feedback contexts, app/tool recommendation requests, or explicit “resource/app/tool” asks. 2. If safe, post one transparent founder/product-feedback self-post or comment with UTM. Good framing: “I’m building Emma by HappyCouple; looking for product feedback on first-screen clarity, output usefulness, safety tone, and dropoff.” 3. Verify authenticated user is `HappyCoupleFounder`; verify API existence plus authenticated subreddit listing and user submitted/comment listing when possible; record `removed_by_category` / removed-spam state. 4. Update the traffic sprint note, Reddit log, and distribution experiment ledger with URL, UTM, verification, and learning. 5. Increase the link-seeking cadence if the current scheduled loop is too passive, but keep max 1 link-bearing touch per run and avoid support-thread link drops. For the Emma-era product frame, safe link-bearing comments should name the app and site transparently instead of vague "relationship tool" language: ```text I’m building Emma, a small relationship-moment app. You bring one real situation and it helps with what may be underneath + what to say next: https://happycouple.ai/?utm_source=reddit&utm_medium=comment&utm_campaign=... ``` This belongs in a separate guarded link-bearing loop from the no-link research/helpful-answer loop. Preserve the no-link trust loop, but do not report it as traffic if no qualified visits or activation events move. Current priority sequence: 1. Reddit useful-answer motion: thoughtful answers, no spam, no fake behavior, no link-dropping. 2. Daily Reddit learning loop: post up to 2 useful comments/day in mixed subs, verify public visibility, and log both comment-strategy learnings and product insights. 3. Creator/specialist partner research: relationship coaches, dating coaches, attachment creators, marriage/sex/intimacy educators, therapist-adjacent educators. 4. Source-attributed traffic only when links become part of the motion. 5. Only then optimize agent behavior based on observed failures and user feedback. ### Current-rate audit discipline Antoine cares about whether the venture is actually getting qualified traffic, not just whether a plan exists. When asked about HappyCouple Reddit rate, verify the live scheduler/cron state before reporting cadence. Report separately: ```text Active automated rate now: Last intended cadence: Last observed execution: Visibility/filtering status: ``` If the daily Reddit loop note says “2 comments/day max” but no posting/commenting cron is active, say `current active automated rate: 0/day` and treat the 2/day figure as a stale/intended cadence, not current throughput. Reddit account guidance: - Use one dedicated HappyCouple founder/operator account, not one cross-product Consumer AI Factory account. - Do not use a fake neutral-user identity. - Recommended account style: `HappyCoupleFounder`, `AntoineHappyCouple`, or similar. - Profile bio: “Building a relationship communication tool. Here to learn and give useful answers. Not a therapist.” - Creating a Reddit account is fast manually, but automated signup may be blocked by reCAPTCHA/“Prove your humanity.” Browser automation may also hit Reddit/Cloudflare challenges even when Antoine is logged in locally, because Hermes' browser sandbox does not share Antoine's browser session. Do not try to bypass CAPTCHA/anti-bot checks. - If autonomous posting is requested, prefer official Reddit API posting with hard guardrails over browser automation. - API setup: ask Antoine to save credentials locally in `/Users/antoinelevy/.hermes/reddit_happycouple.env` (never paste secrets in chat) with `REDDIT_CLIENT_ID`, `REDDIT_CLIENT_SECRET`, `REDDIT_USERNAME`, `REDDIT_PASSWORD` or refresh token, and `REDDIT_USER_AGENT` like `HappyCoupleHermes/0.1 by u/`; chmod 600 the file. - A Reddit app owned by another Antoine-controlled account can be used as the API client while `REDDIT_USERNAME`/`REDDIT_PASSWORD` controls which account posts. Always verify the authenticated username before posting. - If Reddit returns `unauthorized_client` / `Only script apps may use password auth`, the app is not a script app. Use OAuth authorization-code flow instead of password auth. The authorization request redirect URI must exactly match the Reddit app's configured redirect URI, including scheme, hostname, path, and trailing slash. Antoine's existing app used `https://oauth.n8n.cloud/oauth2/callback`; using `http://localhost:8080` caused `bad request` until the exact existing redirect was used. - For this setup, helper scripts were created under `/Users/antoinelevy/.hermes/scripts/`: `reddit_make_auth_url.py`, `reddit_exchange_redirect.py`, `reddit_verify_auth.py`, and `happycouple_reddit_post_comment.py`. Token/config paths: `/Users/antoinelevy/.hermes/reddit_happycouple.env` and `/Users/antoinelevy/.hermes/reddit_happycouple_token.json`. Do not print token contents or secrets. - Python `urllib` against `oauth.reddit.com/api/v1/me` returned HTTP 403 Blocked in this environment even with a valid token; `curl` with `Authorization: bearer ` and the configured `User-Agent` worked. Prefer curl-based API calls for Reddit verification/posting in this environment. - As of the latest workflow, Antoine said he created a Reddit account for HappyCouple, but the username was not recorded. When resuming Reddit work, ask for the username once and save it in the Organic Distribution Review Workflow / Reddit Draft Queue context. - Do not add/promote the product link immediately; new accounts with links can look spammy. - First week: 5–10 thoughtful comments, 0 links, no product mention unless directly asked and allowed. Useful Reddit comment guidance: If Antoine flags the writing as formulaic or AI-sounding, **fix the style/guardrails without pausing a safe active distribution loop**. Pause only for real safety, auth, spam, subreddit-rule, visibility/filtering, or platform-risk issues. Tone/template correction is an iteration, not a reason to stop learning. Do **not** use one repeated public template. Antoine specifically flagged that repeated formulas like `the bad instinct to avoid` and `I would separate two things here` now read as AI-generated. Retire those as default scaffolding. Keep the internal components, vary the visible structure: - sometimes lead with the exact text they could send; - sometimes lead with the social read / underlying issue; - sometimes lead with a timing recommendation; - sometimes lead with a boundary; - sometimes simply say “I’d send something short like…” and stop. Every public answer should sound tailored to the post. Prefer shorter, sharper comments over complete mini-essays. The goal is to be useful and human, not to prove the framework. For Reddit answer drafting and posting, prefer post-specific answers over generic templates: 1. Read the Reddit post title/body and subreddit rules first. 2. Classify safety risk before drafting: abuse/coercion, self-harm, medical/mental-health, legal, minors, none detected. 3. Default to no product mention and no link. Only include a transparent founder/product disclosure if directly relevant, allowed, and useful. 4. Produce one tailored answer with: likely underlying issue, bad instinct to avoid, specific script, next move, and “post / needs human edit / do not post” judgment. 5. Save reusable answer patterns to Obsidian, but do not let generic templates replace human review for real subreddit participation. 6. For early manual review mode: Hermes drafts; Antoine sense-checks/approves before anything is posted. 7. For autonomous mode: only post from the approved Reddit Draft Queue, authenticate via official API, verify `me()`/authenticated username first, enforce small daily limits, and write comment URL/status back to the queue immediately. Stop on auth mismatch, locked/deleted posts, high-risk content, subreddit rule ambiguity, or API errors suggesting rate/trust limits. 8. After posting, verify each comment in two layers: - Authenticated existence check: fetch `https://oauth.reddit.com/api/info?id=t1_&raw_json=1`; record author, score, permalink, and pending 24h/72h result fields in the Draft Queue. - Public visibility check: fetch the logged-out/public Reddit comments JSON for the target post and confirm the comment author/id appears publicly. A comment can exist via authenticated API, have a permalink and score, but still be hidden/filtered/mod-queued from public listings for new/low-trust accounts. Do not rely only on logged-out `/api/info.json?id=...`; during the 2026-05-12 HappyCouple sprint it returned `PUBLIC_INFO_NOT_FOUND` for a post that was visible in the public comments JSON. Use the target post's public `.json?raw_json=1` thread listing as the stronger visibility check. 9. If authenticated API verification succeeds but public visibility fails, treat the comment as “posted via API, not publicly visible,” not as a live distribution touch. Update the Draft Queue and Factory Task Status with that distinction, and stop autonomous posting for the day. 10. For a new/low-karma account, use moderate mode unless Antoine says otherwise: up to 2 comments/day across mixed subreddits, no links/product mention, verify public visibility after each post, and stop same-day posting if a newly posted comment is hidden. If comments are not publicly visible repeatedly, shift to manual account warming for 3-5 days: no links, no product mentions, short useful comments in softer/lower-moderation subs, and avoid r/relationship_advice until the account has some trust. For Reddit, do not overbuild attribution first. Manual tracking is enough at the beginning: - subreddit - post URL - moment type - answer angle used - upvotes/replies - did OP respond? - did anyone ask for a tool/resource? - did HappyCouple get mentioned? yes/no - learning Reply-to-replies is part of the motion, not optional. As of 2026-05-17 on the Mr Han Linux host, run: ```bash cd /opt/mrhan/ops/mrhan-factory-ops python3 scripts/happycouple_reddit_reply_monitor.py --limit 50 ``` This writes: ```text /opt/mrhan/factory-vault/consumer-ai-factory-vault/05 Ventures/Venture 001 - HappyCouple/03 GTM/Reddit/HappyCouple - Reddit Reply Queue.md ``` The guarded HappyCouple Reddit cron should check replies before finding new posts. Reply when someone asks a follow-up, thanks us meaningfully, or continues the problem. Replies count toward the same public-touch cap. Default no-link; only mention/link HappyCouple if the user explicitly asks for a tool/resource or the thread/subreddit is feedback/showcase/self-promo friendly, rules allow it, and the founder/product connection is transparent. Use the local poster with a comment parent fullname (`t1_...`) when replying. Use the review queue: ```text /Users/antoinelevy/Documents/Obsidian Vault/Consumer AI Company Factory/05 Ventures/Venture 001 - HappyCouple/03 GTM/Reddit/HappyCouple - Reddit Draft Queue.md ``` Existing organic sprint artifacts: ```text /Users/antoinelevy/Documents/Obsidian Vault/Consumer AI Company Factory/05 Ventures/Venture 001 - HappyCouple/03 GTM/HappyCouple - Organic Distribution Sprint.md /Users/antoinelevy/Documents/Obsidian Vault/Consumer AI Company Factory/05 Ventures/Venture 001 - HappyCouple/03 GTM/Reddit/HappyCouple - Reddit Useful Answer Templates.md /Users/antoinelevy/Documents/Obsidian Vault/Consumer AI Company Factory/05 Ventures/Venture 001 - HappyCouple/05 Build Logs/HappyCouple - Organic Distribution Process Log.md /Users/antoinelevy/Documents/Obsidian Vault/Consumer AI Company Factory/05 Ventures/Venture 001 - HappyCouple/03 GTM/HappyCouple - Organic Distribution Review Workflow.md /Users/antoinelevy/Documents/Obsidian Vault/Consumer AI Company Factory/05 Ventures/Venture 001 - HappyCouple/03 GTM/Reddit/HappyCouple - Reddit Draft Queue.md /Users/antoinelevy/Documents/Obsidian Vault/Consumer AI Company Factory/05 Ventures/Venture 001 - HappyCouple/03 GTM/Reddit/HappyCouple - Daily Reddit Commenting and Learning Loop.md ``` ## Moment taxonomy nuance Do not turn moments into rigid user-facing categories too early. Antoine pushed back that this can make the product clunky and over-limited before validation. Correct use of moments: - User-facing: open input, lightweight rotating examples/prompt chips. - System-facing: silent classification, analytics properties, research/content organization. - Product strategy: use moments as validation units, not as a visible module taxonomy. Do not create 15 separate UX flows yet. Keep the product feeling like “tell me what happened,” not “select your relationship module.” ## Workflow ### 1. Discover / verify subreddits Use Reddit public metadata where possible: ```bash python3 - <<'PY' import urllib.request, json subs = ['relationship_advice','AmIOverreacting','dating_advice','Marriage'] for s in subs: req = urllib.request.Request(f'https://www.reddit.com/r/{s}/about.json', headers={'User-Agent':'HappyCoupleResearch/0.2'}) with urllib.request.urlopen(req, timeout=10) as r: d = json.load(r)['data'] print(s, d.get('subscribers'), d.get('public_description')) PY ``` For rules: ```bash python3 - <<'PY' import urllib.request, json s='Marriage' req = urllib.request.Request(f'https://www.reddit.com/r/{s}/about/rules.json', headers={'User-Agent':'HappyCoupleResearch/0.2'}) with urllib.request.urlopen(req, timeout=10) as r: data=json.load(r) print([rule.get('short_name') for rule in data.get('rules', [])]) PY ``` ### 2. Mine posts Run the script and verify row count and output paths. ### 3. Inspect output Read the generated Obsidian summary and sample the CSV. If labels look noisy, do not trust aggregate counts blindly. ### 4. Curate manually / semantically The next high-leverage step after scraping is not more scraping. It is manual or LLM-assisted curation into a clean “HappyCouple moment taxonomy.” Create 15–20 moments such as: - partner shuts down - am I overreacting? - apology after overreacting - chores / mental load fight - sex/intimacy mismatch - texting after a fight - jealousy / insecurity - mixed signals - exclusivity talk - feeling unloved / unprioritized - in-law conflict - emotional labor resentment - no-contact / ex urge - cheating suspicion - “they say I don’t listen” ### 5. Convert each moment into assets For each cluster, produce: - homepage prompt chip - SEO page title - short-form video script - Reddit-style helpful answer - ad hook - product test prompt - safety caveat if needed ## Obsidian behavior Antoine expects substantial reusable research/strategy artifacts to be proactively created or updated in Obsidian. When doing HappyCouple Reddit research: - Save compressed durable conclusions to internal memory only when useful. - Save full research artifacts to Obsidian. - Link new runs from the master note. - Do not let useful work live only in chat. Recommended note structure: ```text HappyCouple - Reddit Marketing Research.md # master map HappyCouple/Reddit Research/YYYY-MM-DD run.md # dated mining run HappyCouple/Reddit Research/*.csv # raw tagged samples ``` ## Marketing implications to preserve Public marketing promise: ```text Know what to say next. ``` Product promise: ```text Understand the moment underneath the fight. ``` Retention promise: ```text Build a clearer relationship over time. ``` Funnel: 1. Hook: “I don’t know what to say.” 2. First value: “Here’s what’s really happening and what to say next.” 3. Conversion: “Save this and keep working through the pattern.” 4. Expansion: “Invite your partner.” 5. Long-term: “Build your relationship map.” ## Verification Before final response: 1. Confirm output files exist. 2. Read the first lines of the generated Obsidian note. 3. Report exact file paths. 4. Mention classifier caveats directly. 5. Recommend curation into moments before launching more distribution.