Learning, Condensed

Encoding sets the upper limit on learning: the structure you build when you first meet material decides what exists to be remembered. Retrieval also builds. Each recall strengthens, reorganizes, and tests what encoding made. The main failure is passive review, because re-reading and recognition feel like learning but are not learning. So commit to an answer before you see it, connect facts to each other instead of collecting them separately, work with a concept before you learn its label, and use daily work as retrieval practice. When recall keeps failing, check the encoding before you change the schedule. Two more parts surround this cycle. One is regulation: how difficult the work feels is the measure to watch, and calibrating confidence matters more than scores. The other is a session routine that uses no willpower on choices.

---

1. Encoding

• Attempt an answer before you see the content. A real attempt made before you see the answer makes you look for connections and shows exactly what you do not know. Setting up the problem first changes practice transfer from roughly 1:1 toward 10:1 (Problem-First Learning, Prestudy).
• Build relationships between facts. Encoding is grouping, connecting, and ordering information into a schema. Storing facts separately without linking them is not encoding (Schema Construction, Importance-Based Chunking).
• The working cycle is Aim → Shoot → Skin: write the questions first, search sources for the answers, then clean up the map into a structure you can retrieve from (Bear Hunter System; faster variant Hipshot).
• Learn the concept before its label. Learn what a thing does and why it matters before you learn its name. A name learned first has no meaning attached to it (Reverse Explanation).
• Produce your own representations. The representations you construct are what does the encoding. Activity that looks like work but skips the thinking is a common mistake (Thinking on Paper, The Shortcut Problem).
• Do each step correctly the first time. One error costs ~4x the time of doing the step correctly. To get faster, change the process. Rushing does not make you faster (Accuracy Before Speed).
• Encoding needs meaning and attention. Meaning is what builds encoding, and without attention encoding does not happen. No technique works when attention is divided (Rules of Effective Memorization).

2. Retrieval and spacing

• Practice recall instead of recognition. Recognizing material feels like knowing it, but it is not knowing it. Re-reading feels fluent, and that fluency is the source of the false impression behind passive review (Retrieval, Spaced Interleaved Retrieval).
• Space reviews so that some forgetting happens. Increasing the intervals lets partial forgetting occur, and that shows which gaps are real. A session with zero failed recalls only confirmed what you knew and did not test it (SIR, Retrieval).
• Change the direction of retrieval. Knowledge practiced in only one direction fails easily. Across sessions, vary the form of retrieval and the similarity window (Interleaving: Multiple Angles).
• Reconstruction is a higher level than recall: form new relationships among known nodes and judge whether they hold. The ability to handle unexpected questions comes from this. Repeating stored answers does not provide it (Reconstruction).
• Teach it back. Explaining whole → parts → whole, from memory alone, tests how well the knowledge fits together at every level at once (WPW).
• Fix gaps instead of repeating the same review. When an item keeps failing, suspect the encoding: rebuild the structure or the connection instead of scheduling the same rep again (SIR gap repair, Retrieval).

3. Application

• Use daily work as retrieval practice. After each real-world use, label it as a rep. Study what real use did not cover. Schedule study around upcoming work, and do not run a separate review alongside it (Opportunistic Retrieval).
• For languages: work with material unprepared, at the edge of what you can understand. Do not memorize lists beforehand. Work out the meaning from context, then learn exactly the parts you were missing. Words learned while solving a real problem you are working on are remembered longer than memorized ones (Aim-Shoot-Skin for Language Learning).
• For scripts: learn the attributes at different times. Sound and meaning come first, and the written form is added sessions later. Items are learned in small groups that overlap. Recall works by cross-matching components (Pipelining, IME Method).
• Look for shared structure. Components appear in many combinations. Going through the whole collection at intervals finds overlaps that reviewing one item at a time never shows (Sound Series, How Chinese Characters Work).

4. Regulation and calibration

• Use how uncertain you feel as the measure. Feeling no uncertainty means you have moved into your comfort zone. The typical failure is the reversion response: going back to offloading when uncertainty rises sharply (The Learning Zone).
• Practice noticing when you shift from active processing into passive consumption. The shift happens often and without any signal (Building the Radar).
• Check whether your confidence is accurate, instead of watching scores. Use the two-question Mt-Stupid test and a conditions check. Judge trends over several weeks, never the results of one session (Confidence Calibration).
• The technique is only as good as the thinking it produces. An artifact that looks correct but has the wrong cognition behind it is a failure that looks like a success (The Technique Is Only as Good).

5. The routine around the learning

• Make no choices during a session. Deciding what to do next over and over wastes time and focus. Before the block starts, turn vague choices into closed questions (Decisional Delays, Choice Throttling).
• Rest ≈ work ÷ 3, taken at the first sign of dullness, before you can no longer keep working in the block (OFF-Rest Timing).
• Protect one to three priorities with no exceptions. The plan has to still work on a bad day. That requires slack time and concrete next actions. Optimism does not make it work (Priority 0+1, Building a Schedule That Survives).
• Practice bringing attention back quickly. Losing focus inside a work block is normal. Keeping an unbroken streak matters less than how fast your attention returns, because that speed is what improves results over time (Focus Management).
• Short sessions count as sessions. The sequence prime–map–explore–dive–consolidate works in fragments of 5–30 minutes, with one combined retrieval mission afterward to fix what was lost between fragments (Microlearning System).

6. The mindset that applies to everything

• Mindset decides what difficulty means to you: a reason to keep going, or evidence against you. Mindset is trained through behavior, by making smaller and cheaper mistakes. Affirmations do not train it (Mindset, Fixed vs Growth Mindset).
• Put attention only on the parts of the process you can control. Outcomes only show the effects of the process (Locus of Control).

---

Decision-making doctrine is under Decision Making. Environment and ownership are under Minimalism as Systems Design. Agentic engineering has its own hub. The standing stance toward doing intended things at all, which covers motivation architecture, defusion, and your relationship to mistakes, is in Mindset, Condensed. That page holds the stance. Sections 4 and 6 above cover steering within a session, which is that stance applied to one session. Every rule in sections 1 to 6 traces to a published page. A doctrine with no owner page is a gap. Three doctrines have no dedicated owner page yet and are flagged for the maintenance loop: recall-test hygiene (cueing, verdicts), session-scope rules, and the strong form of the lapse doctrine (when a failed item points to encoding rather than scheduling as the cause).