SELF-MASTERY12 weeksIn-depth

The Apprenticeship Playbook

Learn a context-dependent skill when no one hands you the apprenticeship.

Problem it solves

Generic advice teaches the average case, but context-dependent skills only pay out in the specific case, so tips and checklists never fire on the live decision.

Best for

Operators getting good at a context-dependent skill (negotiating a deal, allocating a treasury, reading a contract, judging a hire) where generic advice never fires on the live decision.

Not ideal for

Standardized skills a course or checklist already teaches well, or anyone unwilling to run repeated reps and log calls before the outcome is known.

Overview

Why this framework exists

Generic advice teaches the average case; context-dependent skills only pay out in the specific case, so the 10,000 tips never fire when the moment arrives. This playbook manufactures the two things an apprenticeship gives you (proximity to a practitioner making real decisions, and a tight feedback loop) when you have no mentor, employer, or permission. Six plays run over about 12 weeks: cap inputs at 3 practitioners, reconstruct 1 real deal a week while logging your call before the outcome, then promote only the rules that survive into a checklist that is yours.

Core principles

4 total
  1. Get proximity to one practitioner making real decisions, then build a tight feedback loop on those decisions. That is the whole mechanism.
  2. Learn from real deals with money or reputation on the line, not case studies, because only those carry the constraints generic advice strips out.
  3. Timestamp your call before the outcome is known. A rule you invent after seeing the result teaches nothing.
  4. Context-dependent skill is built by volume of corrected reps, not insight density: a mediocre loop every week beats a brilliant one every quarter.

Steps

6 steps
  1. Name the one skill, in a testable sentence
    Write the skill as a sentence with a pass/fail outcome, not a topic. Weak: "get better at treasury management." Strong: "decide, within one trading day, whether a given mNAV premium is a buy, using a rule I can defend out loud." Budget 30 minutes.
    Pro tipIf you cannot write the pass/fail version, you do not yet know what you are trying to learn.
    WarningDo not skip this. Every hour after it is wasted if the target is still a topic.
  2. Find 3 practitioners, not 30 pieces of content
    Pick 3 people who currently do the real version of the skill and leave a public trail: trades they post, deals they narrate, code they ship, decisions they explain after the fact. Currently-doing beats famous. 3 is enough to triangulate and few enough to actually track.
    Pro tipA mid-tier operator posting live reasoning is worth more than a legend who only sells the polished story.
    WarningMore than 5 and you are back to consuming content.
  3. Reconstruct one real deal end to end
    Take one decision each of them actually made and rebuild it from the outside: what they knew at the time, the options, what they chose, what happened. Write down the decision you would have made before you know their outcome, then compare. Do 1 per week; after 6 weeks you have 6 reconstructed deals and a written record of where your instinct and theirs diverge.
    Pro tipThis is the apprenticeship substitute you can run alone: standing over their shoulder on a live deal, retroactively.
  4. Build the office-hours loop
    Convert the solo version into a real feedback loop, in order of preference: (1) a standing 30-minute weekly call with one practitioner, one live decision per session; (2) a peer running the same reps, two people each bringing one live decision a week; (3) a public post-mortem of your reconstructed deals with your pre-outcome call attached. The non-negotiable is the cadence and the real decision.
    Pro tipMost people say yes to "can I show you one real decision and get 10 minutes of reaction?" far more than to "will you mentor me?"
    WarningA brilliant mentor once a quarter loses to a mediocre one every week.
  5. Keep a decision journal, call timestamped before the outcome
    For every real decision you observe or make, log four lines before you know how it turned out: what I would do; why (the rule I am applying); what would prove me wrong; confidence (0 to 100). When the outcome lands, log what actually happened and which rules survived. Aim for 3 to 5 logged decisions a week.
    Pro tipThe timestamp is the point. A rule invented after seeing the outcome teaches nothing.
  6. Promote surviving rules into your own checklist
    Every 2 to 3 weeks, read your journal and pull out the rules that keep being right. Those, and only those, go into your personal checklist, built from decisions you watched or made, in your specific context, with the failure cases attached.
    Pro tipYou start by rejecting other people's checklists as too generic; you end by writing one that is not.

Checklist

Saved in your browser

Examples

2 cases
Turning a vague goal into a testable skill

An operator wants to "get better at treasury management." Applying Play 1, they rewrite it as a pass/fail sentence: "decide, within one trading day, whether a given mNAV premium is a buy, using a rule I can defend out loud."

OutcomeThe rewrite exposes that "treasury management" was three different skills bundled together. They pick the one that matters this quarter and stop trying to learn all of it at once.
Play 1
The 10-minute reaction ask

Instead of asking a busy practitioner "will you mentor me?", the operator asks "can I show you one real decision I am wrestling with and get 10 minutes of reaction?" and brings a single live call, already reasoned out.

OutcomeThe yes-rate is far higher, because the ask is bounded and the practitioner reacts to specific reasoning rather than answering a cold open question. It becomes a standing 30-minute weekly call.
Play 4

Common mistakes

6 traps
Collecting more advice
Adds average-case knowledge to a specific-case problem. Fix: cap input at 3 practitioners and spend the rest of the time on reps.
Studying only outcomes
Survivorship bias, and the outcome hides the decision. Fix: reconstruct the decision before the outcome was known.
Waiting for a mentor to say yes
Access becomes the blocker and you do nothing. Fix: run the solo reconstruction and decision journal today, upgrade to a live loop later.
Journaling after the fact
A post-hoc rule teaches nothing. Fix: timestamp the call before the outcome, every time.
Chasing the famous practitioner
Polished story, decisions hidden. Fix: prefer the mid-tier operator who narrates live reasoning.
Quarterly deep mentorship
Too few corrected reps to build tacit skill. Fix: weekly cadence beats depth per session.

Origin story

How this framework came to be

Built by Stratapedia on Naval Ravikant's idea that specific knowledge, the kind that cannot be trained or outsourced, is taught through apprenticeships, not schools (How to Get Rich). Naval supplies the diagnosis (why generic advice fails for context-dependent skills) and the one-word prescription (apprenticeship). The six plays are the Stratapedia operational build: how to run the apprenticeship loop when no one has handed you one.

Source

Traced to primary
Source · ESSAY
Stratapedia Originals
Stratapedia
Open source →

Related frameworks

Browse all Self-Mastery →