My Specific Knowledge Map

This page tracks the recurring pattern behind the sources being ingested into the wiki. The surface interests look broad: trading, AI coding, learning science, Naval, Howard Marks, writing, and mental models. Underneath, they point to one coherent direction:

You are trying to become an AI-augmented learner-builder-investor: someone who learns fast, thinks clearly under uncertainty, builds with leverage, and turns judgment into compounding assets.

This is not a fixed identity. It is the current pattern suggested by the wiki.


The Core Pattern

The repeated theme is not "trading" by itself, "coding" by itself, or "learning" by itself. The repeated theme is:

Build judgment systems in domains where mistakes are costly, then use leverage to compound the useful parts.

That shows up in five loops:

  1. Learning loop - become more capable through serious upskilling, prerequisite mastery, deliberate practice, and deep memory.
  2. Market loop - survive uncertainty through Howard Marks, second-order thinking, edge, position sizing, and ruin avoidance.
  3. AI leverage loop - use Codex and agentic workflows to turn judgment, planning, and review into more output.
  4. Naval loop - aim effort toward specific knowledge, permissionless leverage, accountability, ownership, and long-term games.
  5. Writing/synthesis loop - convert scattered inputs into reusable thinking through essays, articulation, and cross-domain synthesis.

What Themes Keep Appearing?

Recurring InterestWhat It Seems To MeanWhat It Gives YouFailure ModeBest Output
Learning / upskillingYou want the machinery of self-improvement, not motivational decorationFaster skill acquisition, better foundationsEndless preparation without enough applicationCurricula, practice plans, review systems
Marks / investingYou are drawn to judgment under uncertaintyRisk awareness, cycle thinking, price/value disciplineBecoming too abstract or too cautiousInvestment/trading checklist, cycle notes, risk journal
TradingYou want an applied arena where feedback is real and ego is punishedEdge, sizing, emotional discipline, probabilistic thinkingOvertrading, leverage, mistaking luck for skillSmall-size journaled experiments
AI codingYou want leverage over executionAbility to build tools, automate workflows, increase outputDelegating judgment instead of executionAgents, scripts, dashboards, wiki tools
NavalYou want a philosophy for wealth, freedom, and personal fitDirection: specific knowledge + leverage + long-term gamesStaying at aphorism levelPersonal operating principles
Writing / articulationYou want to make your thinking legible and reusableCommunication, public assets, clearer thinkingConsuming more than producingEssays, memos, synthesis pages

The strongest repeated signal: you keep choosing sources about compounding capability. Not random self-help, not random market tips, not random coding tutorials. The sources cluster around durable capability: learning, judgment, leverage, risk control, synthesis, and self-direction.


Your Specific Knowledge Pattern

Specific knowledge is knowledge rooted in curiosity, obsession, lived context, and unusual combinations. It is not merely "what subject do I know?" but "what combination of interests makes my judgment hard to copy?"

The wiki suggests your specific knowledge may be forming at this intersection:

In plain English:

You are not only trying to become a trader, coder, or learner. You are trying to become someone who builds systems for becoming better.

That is the interesting pattern. The wiki itself is an example: instead of merely reading books and PDFs, you are building a knowledge machine that extracts concepts, links them, audits them, and turns them into operating systems.


What The Wiki Suggests You're Trying To Become

The best current label:

A systems-minded operator who uses AI, markets, and learning science to build compounding judgment.

Possible identity directions:

DirectionMeaningEvidence In The Wiki
AI-augmented researcherUses AI agents to process dense material and maintain a second brainagentic-coding-workflows, this wiki itself
Beginner investor/trader becoming process-drivenWants to trade/invest without being destroyed by ego, leverage, or vibesbeginner-trader-investor-learning-path, trading-edge, position-sizing
Leverage-oriented builderWants code/media/tools to scale judgment beyond manual effortpermissionless-leverage, ramping-your-coding-output-with-openai-codex
Skill maximalistBelieves ability can be built through serious trainingadvice-on-upskilling, deliberate-practice
Writer/synthesizerWants to turn scattered reading into clear frameworkshow-to-articulate-yourself-intelligently, something-is-different-about-2026

This is close to Naval's "productize yourself" formula: yourself is the unusual taste-pattern across trading, AI coding, learning, and synthesis; productize is where Codex, writing, tools, and Obsidian turn that judgment into scalable output.


The Personal Operating Thesis

If this wiki were turned into one thesis, it would be:

Learn deeply, think probabilistically, avoid ruin, build with leverage, and convert insight into reusable systems.

Expanded:

  • Learn deeply because shallow familiarity creates illusions of competence.
  • Think probabilistically because markets, careers, and AI workflows are uncertain.
  • Avoid ruin because one oversized mistake can end the learning game.
  • Build with leverage because code, media, and AI agents can scale judgment.
  • Convert insight into systems because chat insights disappear unless filed, linked, tested, and reused.

Strengths Already Visible

  • You seek foundations. You ask what prerequisites and beginner rules matter before chasing advanced tactics.
  • You like dense sources. Marks, Naval, learning science, and AI-coding workflows are not light snacks.
  • You want application. You repeatedly ask "what should I apply and learn?" rather than only asking for summaries.
  • You care about maintenance. You ask for linting, concept pages, and Obsidian structure. That means you are not just collecting notes; you are building an operating environment.
  • You combine domains naturally. Trading, AI coding, learning, and writing look separate, but your questions keep pulling them into one system.

Main Risks

RiskWhat It Looks LikeCountermeasure
Over-ingestionReading everything before practicing anythingEvery source should produce one action, checklist, or experiment
Domain sprawlTrading, coding, learning, writing all compete for attentionTreat them as one stack: AI-assisted learning and decision systems
Abstract philosophyNaval/Marks become quotes instead of behaviorConvert each principle into a rule, template, or journal field
AI as consumption acceleratorCodex helps ingest more but not build moreUse AI to produce tools, reviews, dashboards, and decisions
Trading overconfidenceGood theory creates premature confidenceKeep size tiny until records show process quality

The most important warning: do not let the second brain become a beautiful substitute for first-hand reps. The wiki should push you into practice, then absorb the feedback.


Leverage Map

The wiki becomes valuable when it creates templates you actually use:

  • Trading thesis template
  • Position-sizing calculator
  • Loss protocol
  • Codex project brief
  • Learning prerequisite map
  • Weekly synthesis memo
  • "Specific knowledge evidence log"

30-Day Experiments

1. Specific Knowledge Evidence Log

Create a weekly note with four prompts:

  • What did I keep returning to without being forced?
  • What felt like play to me but looked hard to others?
  • What did someone ask me for help with?
  • What source or idea changed how I behaved this week?

This tests specific knowledge against behavior, not self-image.

2. Trading Decision Journal

For every trade/investment idea:

  • What game is this: investment, trade, speculation, or experiment?
  • What is the edge?
  • What is already priced in?
  • What invalidates it?
  • What is max loss?
  • What is position size and why?
  • Was outcome due to process or luck?

This converts Marks into behavior.

3. Codex Leverage Sprint

Pick one small workflow and build a tool around it:

  • Obsidian link checker
  • concept-page generator draft
  • trading journal template generator
  • flashcards from concept pages
  • source-ingest progress tracker

This converts permissionless leverage into something visible.

4. Weekly Synthesis Page

Each week, write one synthesis page answering:

What did this week's sources collectively teach me that no single source said alone?

This trains the exact cross-domain muscle your wiki keeps pointing toward.


Questions To Keep Asking

  • What do I do even when nobody asks me to?
  • Which topic keeps returning after novelty fades?
  • Where do I have unusual taste or patience?
  • What painful problem am I willing to study longer than most people?
  • What can I build that uses my wiki as raw material?
  • Which of my interests creates the best feedback loop: trading, coding, writing, or teaching?
  • What am I collecting because it is useful, and what am I collecting because it delays action?

Working Hypothesis

Your current specific-knowledge pattern is:

AI-assisted synthesis and systems-building for learning and financial decision-making.

More simply:

You are building yourself into a person who can learn hard things, reason under uncertainty, use AI as leverage, and turn knowledge into practical systems.

This page should be revisited after another 10-20 ingested sources and after you have a few real practice artifacts: trading journal entries, Codex-built tools, essays, or learning plans. The pattern will become sharper once behavior produces feedback.


Sources