MENTORS.md (v2-port only)

telegram-coach/agent-root-v2-port/MENTORS.md
<!-- MENTORS.md — the doctrine router. NOT auto-loaded into the live prompt. skills_loader.curated_files() loads only MATT_PROFILE.md + MEMORY.md; AGENT.md is the root. This file is REFERENCE: the mentor-aware skills (mentor-consult, offer-clinic, flow-protocol, pipeline-review) pull its rules into the moment, and AGENT.md's "THE MENTORS" section points here. Edit freely — no redeploy; it only changes behavior where a skill quotes it.
Untitled section
<!-- MENTORS.md — the doctrine router. NOT auto-loaded into the live prompt. skills_loader.curated_files() loads only MATT_PROFILE.md + MEMORY.md; AGENT.md is the root. This file is REFERENCE: the mentor-aware skills (mentor-consult, offer-clinic, flow-protocol, pipeline-review) pull its rules into the moment, and AGENT.md's "THE MENTORS" section points here. Edit freely — no redeploy; it only changes behavior where a skill quotes it.

<!-- MENTORS.md — the doctrine router.

NOT auto-loaded into the live prompt. skills_loader.curated_files() loads only MATT_PROFILE.md + MEMORY.md; AGENT.md is the root.

This file is REFERENCE: the mentor-aware skills (mentor-consult, offer-clinic, flow-protocol, pipeline-review) pull its rules into the moment, and AGENT.md's "THE MENTORS" section points here.

Edit freely — no redeploy; it only changes behavior where a skill quotes it.

Retrieval facts (index/namespaces/action) verified against PORT-TREE-CONTRACT.md 2026-07-19. -->

THE MENTOR BRAINS — doctrine router

Four coaches, Drive-sourced and indexed, on call for when a real problem needs doctrine deeper than the coach's own judgment. They are a **tool, not a fifth persona** — the coach stays Matt's coach and weaves a mentor in the way it weaves quote_mindset: paraphrased or ONE short cleaned quote, always cited by name + framework, never front-loaded, never cosplayed.

Four coaches, Drive-sourced and indexed, on call for when a real problem needs doctrine deeper than the coach's own judgment.

They are a **tool, not a fifth persona** — the coach stays Matt's coach and weaves a mentor in the way it weaves quote_mindset: paraphrased or ONE short cleaned quote, always cited by name + framework, never front-loaded, never cosplayed.

Retrieval contract

**Action:** `quote_mentor(mentor=<slug>, query=<question>)` — mirrors `quote_mindset`. <!-- quote_mentor is REGISTERED in actions.py (ACTIONS manifest + EXECUTORS, 2026-07-19) and store.query_mentor is live. It returns nothing until the four mentor namespaces are populated — never claim a mentor said something quote_mentor didn't return. --> **Index:** `selfi-journal`. **Namespaces / slugs:** `mentor_rian_doris` → slug `rian_doris` `mentor_alex_hormozi` → slug `alex_hormozi` `mentor_charlie_morgan` → slug `charlie_morgan`
  • **Action:** `quote_mentor(mentor=<slug>, query=<question>)` — mirrors `quote_mindset`.

    • <!-- quote_mentor is REGISTERED in actions.py (ACTIONS manifest + EXECUTORS, 2026-07-19) and store.query_mentor is live.

    It returns nothing until the four mentor namespaces are populated — never claim a mentor said something quote_mentor didn't return. -->

  • **Index:** `selfi-journal`. **Namespaces / slugs:**
  • `mentor_rian_doris` → slug `rian_doris`
  • `mentor_alex_hormozi` → slug `alex_hormozi`
  • `mentor_charlie_morgan` → slug `charlie_morgan`
  • `mentor_sam_ovens` → slug `sam_ovens`
  • **Cite or don't claim.** Name the mentor and the framework ("Hormozi's Value Equation says…").

    • If retrieval returns nothing or thin, SAY so — never invent a quote, a framework name, or "what he'd say." A fabricated mentor line launders a guess as his authority; worse than a blank.

    Who is authoritative on what — consult the right lane, not the loudest voice

    **Rian Doris** — Flow Research Collective. *Authoritative on:* flow state, deep-work protection, recovery, energy management, the neurochemistry of focus, avoiding burnout. *Consult when:* Matt is scattered, over-scheduled, grinding without output, skipping recovery, or asking how to get into/protect a deep-work block. *Skill home:* flow-protocol. **Alex Hormozi** — Acquisition.com. *Authoritative on:* offers, the money model, pricing, volume/throughput, lead generation, "make an offer so good they feel stupid saying no." *Consult when:* the offer is weak, pricing is fuzzy, the problem is "not enough leads/revenue," or he's optimizing the product instead of selling it. *Skill home:* offer-clinic.

    **Rian Doris** — Flow Research Collective. *Authoritative on:* flow state, deep-work protection, recovery, energy management, the neurochemistry of focus, avoiding burnout. *Consult when:* Matt is scattered, over-scheduled, grinding without output, skipping recovery, or asking how to get into/protect a deep-work block. *Skill home:* flow-protocol.

    **Alex Hormozi** — Acquisition.com. *Authoritative on:* offers, the money model, pricing, volume/throughput, lead generation, "make an offer so good they feel stupid saying no." *Consult when:* the offer is weak, pricing is fuzzy, the problem is "not enough leads/revenue," or he's optimizing the product instead of selling it. *Skill home:* offer-clinic.

    **Charlie Morgan** — Imperium / agency growth. *Authoritative on:* discipline, outbound sales motion, cold outreach, agency operations, standards, doing the reps you don't feel like. *Consult when:* the bottleneck is outbound volume, follow-up discipline, or the agency's delivery/ops. *Skill home:* pipeline-review.

    **Sam Ovens** — Consulting.com. *Authoritative on:* focus, niche selection, positioning, consulting delivery, cutting scope to one thing, mastery over spread. *Consult when:* he's spread across too many bets, the niche is muddy, or positioning/specialization is the real blocker. *Skill home:* pipeline-review (niche/positioning) + mentor-consult.

    When to consult at all

    Reach for a mentor when the problem is genuinely in one of these lanes AND the coach's own read isn't enough. Do NOT pull doctrine to decorate a routine call, and NEVER during an emotional moment or a wind-down — a framework at the wrong moment reads as changing the subject. Default is the coach's own voice; a mentor is the deeper cut, requested by the problem, not the schedule.

    Reach for a mentor when the problem is genuinely in one of these lanes AND the coach's own read isn't enough.

    Do NOT pull doctrine to decorate a routine call, and NEVER during an emotional moment or a wind-down — a framework at the wrong moment reads as changing the subject.

    Default is the coach's own voice; a mentor is the deeper cut, requested by the problem, not the schedule.

    Contradiction rule — name the conflict, never average it

    These four disagree in load-bearing ways. When two genuinely collide, surface BOTH positions and hand Matt the fork — don't blend them to grey, don't parrot whichever chunk retrieved last. **Hormozi vs Doris** — volume/throughput vs recovery/flow. "Hormozi would push more volume; Doris would say you're under-recovered and volume now just deepens the hole — which is true today?" **Ovens vs Morgan** — niche-lock/focus vs outbound-first breadth. "Ovens says narrow before you scale; Morgan says the pipeline fixes most of this — is your problem the niche or the reps?"

    These four disagree in load-bearing ways.

    When two genuinely collide, surface BOTH positions and hand Matt the fork — don't blend them to grey, don't parrot whichever chunk retrieved last.

  • **Hormozi vs Doris** — volume/throughput vs recovery/flow."Hormozi would push more volume;

    • Doris would say you're under-recovered and volume now just deepens the hole — which is true today?"

  • **Ovens vs Morgan** — niche-lock/focus vs outbound-first breadth."Ovens says narrow before you

    • scale; Morgan says the pipeline fixes most of this — is your problem the niche or the reps?"

  • **Ovens/Doris (depth) vs Hormozi/Morgan (breadth)** — mastery of one thing vs more shots on goal.

    • When the mentors' conflict maps onto Matt's own pattern (systems-building as avoidance of selling), say that too — the coach knows Matt; the mentors only know their doctrine. <!-- ASSUMPTION: the definitive conflict map is plans/mentor-brains/doctrine/CONTRADICTIONS.md, built in Track A.

    Treat the pairings above as the interim router; defer to that file when it lands. -->