Bear Hunter System

The Bear Hunter System is an encoding workflow. The learner builds the structure of a topic while learning the topic, and nothing is left to organise afterward. It replaces passive reading, linear notes, and every plan to collect material now and organise it later. Collecting first and integrating later wastes the work, because nothing was integrated to begin with.

The name comes from the hunting sequence the workflow runs on: sight the target before firing, fire, then process what you brought down. The three passes are named after those steps: Aim, Shoot, Skin. It is the default encoding workflow of this vault, for any subject. It sits inside Deep Processing, the dimension that accounts for what processing buys over exposure.

Once the written cycle runs close to unconscious competence, Aim and Shoot fuse into one fast pass with the questions held in the head. That pass is called Hipshot, and Skin runs on its map unchanged.

Core takeaways

• Write the questions before opening the material. Most topics resolve to 15–30 major concepts, and catching about 80% of them in about 25 minutes beats catching all of them in two hours.
• Answers go onto a growing map, in layers: the logic first, then the concepts, then the important details. Arbitrary details stay off the map and go to flashcards later.
• Skin rebuilds the map until it can be redrawn with every source closed. Two branches off a node is the target, four is the ceiling, and fewer than two means merge.
• Questions come before reading because trying to apply makes you understand, and trying to understand makes you memorise. Feeling overwhelmed or confused means relationships are surfacing; finding it easy usually means the technique is not being applied to standard.
• Three schedules run the workflow at different speeds, from Aim one week ahead to whole topics in about a day. Weekly and monthly interleaved retrieval runs underneath all three.
• Hipshot runs Aim and Shoot as one pass with the questions asked mentally. It needs near unconscious competence with the written cycle, and any session where relating drops out returns to the written loop.

Aim: the questions come before the material

Aim is writing down what the material must answer before opening it. The pass starts with keyword collection, and collection is meant to be cheap. Most topics, a couple of textbook chapters or a few weeks of class, resolve to 15–30 major concepts, not pages of them. Catching about 80% of them in about 25 minutes beats catching all of them in two hours. Collect them out of order on purpose; this breaks the framing bias of the material’s own headings. Invent your own keywords for concepts and diagrams that carry no label. For a wholly unfamiliar term, take a one-paragraph gloss and move on. The extraction itself can go to a tool, because it is the easiest part. The difficulty worth keeping is the thinking that follows. Then group what you have into three to seven hypothetical chunks. Hypothetical matters: committing early to a structure is the sunk-cost trap. If in doubt, draft the flow earlier rather than later, so the map carries the load your head no longer has to. The workflow raises load first on purpose, because the higher-order work happens under that load. Only then does it offload the load to the map.

Each concept then gets two questions. Why is this important? forces the big-picture judgment. How does it relate to ___? surfaces the relationships the importance question misses, because importance gets answered through whatever bias you already hold. The questions that work are why-shaped and how-shaped, and genuinely unknown to you. Emotional, personal, or genuinely curious questions work better still. Plain what is… questions can be dropped entirely, since higher-order answers complete the lower-order ones automatically. Cast the questions shallow and wide rather than deep and narrow. Questions pay on the content they target and almost nowhere else, so coverage of the topic, and not depth on one corner, decides whether Aim pays.

What importance looks like varies by subject. The patterns below are starting points. They never replace asking why is this important? each time, because that question is where the real chunks come from.

Subject	Importance usually runs through
Biology	Function; structure against function; scale; groups of causes meeting groups of effects
Chemistry	Reaction mechanisms; applications; common reagents
Physics & maths	Real-world applications; the concepts a concept depends on
English	The writer’s background, motivations, and values; the significance of the story
History	The movements of the period; cause and effect; the motivations of key players
Law	The principles of justice underneath; the landmark cases that exposed their gaps
Languages	Common usage; situational usage; the effect a form has on the message

Aim goes as early as possible: before a lecture, a class, a reading, a video. It scales down. Five or ten minutes buys a superficial Aim of the largest chunks and major relationships, and even that pays. What it replaces is the hour of past papers. An hour answering questions you wrote is an hour spent entirely on your own weak points, because you only wrote questions you could not already answer. An hour of ready-made questions surfaces one or two isolated gaps and trains none of the skill of generating curiosity in dull material. Connected questions revise several points at once; isolated questions never do. Past papers also get less reliable over time: exam styles shift and curveball questions grow more common, so the ready-made hour trains last year’s exam. Going slightly out of scope is faster. Five or ten minutes on something non-examinable that unlocks the examinable content pays for itself in saved relearning. Distrust pages covered as a measure, because studying and learning are different activities. Aim is the first part of the learning itself rather than a plan made before it. The step has its own page, Aim, and the grouping discipline it feeds is Importance-Based Chunking.

Shoot: answers go onto the map

Shoot is working the resources to answer your own questions. Each answer lands on a growing map rather than in the order the material was written. The answers worth keeping are logical and interconnected. Logical means you know where the answer comes from, so it needs no memorising. Interconnected means it joins the nodes already there, and the count of connections is what tells the brain to keep it. Two comparisons show what that feels like. A violinist knows the bow’s length without ever memorising it. A footballer knows every teammate’s position in any situation. That is detailed knowledge nobody sat down to memorise; it was learned organically and it made sense. Most learning should look like that.

A Shoot session looks chaotic from outside: read, flip back and forth, write a few notes, connect them, find the next question, return to the resource. The first chunks go far apart on the page, because sub-chunks will need somewhere to land. From inside, following someone else’s prescribed order is the chaos. The brain is then solving meaning, structure, and relevance all at once, against a sequence it did not choose. The knowledge itself was never linear. It got flattened into a line to be delivered, and the map rebuilds it toward the shape it had in the head of whoever wrote it. Encoding does not have to match the exam’s format: encode in the shape that learns best, then practise retrieving in the shape the exam will ask. The material lands in layers, in order: the backbone and its logic first, then the concepts that hang off it, then the concrete details that anchor them. The fourth layer, arbitrary details, does not belong on the map at all; those go to flashcards later. Not every question gets answered perfectly, and that is fine; the learning occurs in the attempt. The loop iterates: Aim again as the map raises new questions, Shoot again to answer them, sometimes several cycles before a map is ready to Skin. One diagnostic runs the whole pass: if you aimed well, shooting is easy. Difficulty in Shoot usually means old linear habits are steering again. The mechanics are on Shoot.

Skin: the map becomes the artifact

Skin rebuilds the working map into a structure simple enough to redraw with every source closed. It is not tidying. Every chunk, sub-chunk, and re-chunk decision is a judgment about what matters most and why. That judgment is the highest order of the work, so much of the learning happens in Skin. The finished form has a name, GRINDE, and a six-part spec. Grouped: heavily chunked. Reflective: the layers visibly sorted, backbone to concepts to important details, so the map shows how you worked it out; this is the marker of an advanced learner. Interconnected: lateral links inside and across layers, real cause-and-effect only, never decorative arrows, each labelled with what the relationship is, the rationale written rather than a bare line drawn. Non-verbal: as few words as possible, with doodles and a personal shorthand carrying the content. Words hide the structure, and abstract visuals recruit more of the brain. Directional: a visible flow, which tests whether the logic is real, since logic is cause and effect. Emphasised: the main line made visually dominant by size, weight, or colour. Making it dominant forces an explicit judgment about which connections matter most.

The sizing rule is the 2–4 Rule: two branches off a node is the target, four is the ceiling, and fewer than two is the signal to merge. Worked once, with neutral content:

A chunk carrying six points splits into two sub-chunks of three. The split itself
creates a lateral relationship between them that would otherwise have surfaced later as
crossing arrows. A node with one line in and one line out, a single-node chain, gets
removed, its neighbours joined directly, the upstream chunk relabelled so the surviving
relationship reads straight. Later, when siblings appear, the removed idea returns as a
sub-chunk of its own.

Skin runs the same day when possible, or as one weekly pass over the week’s material. A rhythm you can sustain matters more than which of the two you pick. The checks at the end are short. Can the topic be explained from the map with the sources closed? Do the chunks reflect importance or the material’s order? Does any node carry more than four branches? Do any single-node chains remain? Does every arrow earn its place? Did the pass make the map simpler? A map that is beautiful but hard to retrieve is not done. One expectation is directly falsifiable. Material that would have produced around fifty flashcards should produce ten to twenty after a correct cycle. Most of it now follows from the logic and concepts on the map. The refinement passes are on Skin.

Why the passes run in this order

A topic separates into four layers, the layers of learning. The logic holds it together: cause and effect, why it happens and why it matters. The concepts are how it happens and what it is. The important details make a concept concrete. The arbitrary details are learned only because an assessment demands them. The sort between the last two is one question: does knowing this detail help me understand the concept it is attached to? Roughly 30–50% of details pass it. Studied front-to-back with no structure, a subject runs about 10% conceptual, 20% important detail, and 70% arbitrary, so seven-tenths of the time goes to memorising things with nothing to attach to. Learned in layers, innermost first, the split moves to roughly 30% on logic and concepts and the rest on details that now carry meaning. The layers are not fixed, and that is the lever. How relevant a detail is depends on whether structure exists to give it relevance, so the way to shrink the arbitrary layer is to overinvest in the first two. A tree with ten thousand leaves has five or six main branches. Out of order, the same content grows more complicated and more disconnected and collapses back into raw memorisation. What the levels of mastery mean, and why “required mastery” is computable at all, is the subject of Knowledge Mastery: From Recognition to Usable Knowledge.

The passes move up through levels. Aim forces the brain to levels three through five, application, analysis, and evaluation, from the start, by making problems before the content is understood. Shoot cycles applying and analysing. Skin lifts the work to evaluating, the level most learners never reach. Level three is the efficiency floor; a working session never drops under it. The mechanism underneath is the reason questions come before reading. Trying to memorise is hard. Trying to understand makes you memorise. Trying to apply makes you understand more deeply. Jump to application first, and the lower levels fill in underneath faster than they would if addressed directly. Retention works the same way. The brain keeps what has many connections running through it. Compare a station: it is large because connections run through it, and it does not get connections because it is large. So to make any single fact memorable, stop working on the fact and work on its relationships; the remembering arrives as a byproduct. What you think is what you learn. What you write is not.

So the technique is supposed to feel a particular way, and each feeling has a meaning:

How it feels	What it means
Overwhelming	The number of relationships surfacing while answering “why is this important”: a network of possibilities to refine
Confusing	Many viable non-linear structures exist, and deciding between them is prioritisation and evaluation, the highest order of the work
Time-consuming	Each keyword is getting deep examination; the depth is the consolidation, and the feeling fades as speed grows

When it is working, the topic seems to organise itself while being learned. The map makes your thinking more structured instead of only recording it. The reverse also holds: finding it easy is the warning sign. A learner who feels no difficulty is usually not applying the technique to standard. Study so easy it makes you drowsy is a clear signal that nothing is happening. Learning is a highly engaged state. The technique also withholds certainty for a long time. The certainty that traditional methods hand out early is an illusion; it does not reflect the knowledge actually built. That illusion is where inconsistent results, frustration, and performance anxiety come from. Reading that effort correctly, as a signal rather than a cost, is the subject of Cognitive Load & What Mental Effort Is Trying to Cue, and steering by it is the subject of Self-Regulation.

Running it: prestudy, the three schedules, the minimum viable version

Prestudy is the timing decision that pairs with the workflow: studying a topic before the class that formally covers it, so the live session becomes a second pass rather than a first. Prestudy decides when learning starts; the Bear Hunter System decides how. The mechanism is load. Prestudy spreads the cognitive cost across sessions instead of concentrating it in one intensive event, where overload is hard to recover from and compounds week over week. Done correctly, it ends with a clear big picture across the whole topic, the major ideas seen in relation, some hypotheses about how they connect, and no details memorised yet. Its ceiling: a learner with moderately efficient technique can frame four to six weeks of content in a single weekend. Its floor: a ten-minute skim before class still pays. The full treatment is Prestudy.

The schedules come in three tiers, each with the system’s own grades for efficiency and difficulty. Standard, efficiency 5/10, difficulty low. Aim at least one week’s material at the end of the previous week. Shoot before, during, and after each learning event. Skin daily and re-Skin the week, or Skin the week at once, whichever rhythm fits your actual schedule. Accelerated, efficiency 7/10, difficulty moderate. One weekend Aims an entire topic and Shoots 60–70% of it from self-study material. The remaining 30–40% happens before, during, and after the week’s events. Classes stop being first exposure and become recheck, re-Skin, and easy retrieval sessions. Skin closes the week. A different subject each weekend keeps you weeks ahead of the curriculum. Ultra-accelerated, efficiency 10/10, difficulty high. Aim, Shoot, and Skin all run before the main events, entire topics in a session, with curriculum time freed for retrieval. The target is roughly 90% coverage at 90% retention, explicitly not 100%, at about a day per topic. By the system’s own admission this tier is essentially impossible without substantial cognitive training. Under all three tiers, weekly and monthly interleaved retrieval keeps running underneath; the tiers change encoding and never the retrieval floor. When time is genuinely tight, the minimum viable version is a deliberate reduction. Take the five to ten most important concepts, a cut-down of the usual 15–30. Ask the why-question on each. Form three to seven chunks. Draw only the relationships needed to explain the topic. Do one cleanup item after learning. Four things hold at any speed: relationships stay first, the work never collapses into pure memorisation, the layers stay ordered, and the order stays yours. That last one is order control, the skill the whole workflow trains.

Hipshot: Aim and Shoot as one pass

Hipshot is what Aim and Shoot become once the writing has done its work: a single fused step, the questions held in the head, with Skin unchanged at the end. The writing was the training. Putting every keyword and question on paper before answering any of them is what teaches a brain to generate curiosity on demand. Once the questions arrive unprompted, the paper is overhead, so the paper is the one thing dropped. The questions stay. The name describes the change: instead of a careful sight down the barrel, a quick shot from the hip.

A shot from the hip is still aimed. Each cycle takes one keyword: question, answer, place, relate, next. The session runs inside the Bear Hunter System as its first named variation, and scheduling stays with the parent, inherited once the standard versions feel stable. Collection now carries a filter: only the keywords that build the topic’s fundamental logic make this pass, layer one in the Layers of Learning sense, and a filter that sharp already takes competence a beginner does not have. The rest wait. Each keyword that survives gets the questions the written Aim exists to produce: what is it, why does it matter, how does it relate to what the map holds. The questions are asked mentally. Shoot answers on the spot, straight to the resources (guides, videos, search) and straight onto the mind map. No comprehensive question list ever exists outside your head.

At a wider grain the same cycle is a hypothesis loop. Each round of questions proposes a rough logic layer, shooting validates or corrects it, and the layer commits to the map once it holds up, never the instant an answer surfaces. The map speeds the loop as it grows. Every placement gives the next keyword something to attach to. Every answer sharpens the next questions. The cycles climb from layer one through two, three, and four. Run correctly, the whole thing feels like free exploration and organic discovery rather than executed steps. The speed has a plain cause. The sub-skills that once needed their own attention now run unattended: laying out the map, thinking in relationships, turning an idea into a note. Relationships form fast enough that the map gets built while the answering is still happening. So Aim takes drastically less time, and far fewer iterations separate the first keyword from a map ready to Skin. Underneath, this is Inquiry Based Learning at full speed: question then answer in rapid alternation, with the questions never leaving the head.

Only the medium changes. The questions themselves are the same ones the written Aim would have asked, at the same quality. Any drop in question quality means the variation is being faked rather than run. What the speed trades away is the comprehensive list. The written system lays out every keyword and question before answering any of them. Hipshot gives that inventory up and builds bit by bit. That only works while the big picture is still being held in mind.

Holding that big picture is the prerequisite, and the level required is high: close to unconscious competence with the standard written Aim–Shoot cycle. Attempted earlier, the variation fails with a signature. Answering consumes the attention, the relating step drops out, placements stop sharpening the next questions, and the map degrades into a one-directional information dump. Three tells catch it early. They are the same shortcut showing up three ways, and any one of them alone means the session drops back:

• Relationships slip to second place, and the session starts sliding toward memorization.
• The layers of learning get compromised: details land before the logic that should carry them.
• Order Control gets compromised: the material’s order steers the session instead of relevance pulling it.

A compromised run costs nothing to abandon. The fallback is the written system, which works as well as it ever did. Finding the variation overwhelming at first is ordinary, and it passes with practice. Even a glimmer of clean Hipshot on an easy subject is progress. A mistake-free run takes consistent practice and deep familiarity.

Practice never removes the mess. A Hipshot map has connections going everywhere, and Skin runs on it unchanged. The bar is checkable: the map should come out at least as good as one a dedicated written Aim and Shoot would have produced, logical, chunked, layers intact, and at moderately low effort. Effort still running high means the fused step has not replaced anything yet. No outside trial of this variation exists. The reachable research supports only the family it belongs to: support that helps a novice becomes overhead once the skill runs on its own. That covers the shape of the idea and nothing about this named procedure.

Acquiring Hipshot is mostly waiting. It tends to emerge on its own, the way seamless cycling between the written Aim and Shoot emerged before it, one more scaffold falling away once each step can stand alone. The written system stays the default until, some session, the questions arrive before you have picked up the paper.

Where a model fits in

A model fits into this at specific joints. Hand it the tedious low-effort work:

• keyword extraction
• consolidating several sources into one, which prevents split attention
• generating alternate Aim questions after your own attempt, never before it
• asking what relationships the map might be missing
• generating test questions once the map exists

Challenge everything the model returns, since it has no inherent grip on truth no matter how it reads. Keep it away from the thinking the workflow exists to force. Chunking and organising are the higher-order learning, so outsourcing them removes the learning. The question-writing skill behind Aim is never outsourced either. A beginner cannot yet feel passivity from inside, which is why the honest advice is not to use a model for structuring at all until the difference between active and passive is a felt thing. The decay this guards against is the subject of The Shortcut Problem.

When it goes wrong

Fault	Cause	Repair
Passive Aim	Questions are mostly what is…	Rewrite as why/how/relates questions; drop the what-questions entirely
Jeopardy question	A question rebuilt from an answer already held; it looks like inquiry and generates none	Ask only what is genuinely unknown to you
Importance checklisting	”Why does it matter” answered with one reason, then moving on	Most things matter for several reasons; produce them and weigh them
Copying during Shoot	Notes following the material’s order	Back to the Aim questions; answers land under chunks
Reverse causality	Importance justified by what a thing produces rather than what produced it; the relationship now rests on rote	State “A is important because B,” then ask: would I only know that by having memorised it?
Waterfalling	Every connection radiating outward or down; zero lateral links	Ask how the chunks affect each other; the inter-chunk relationships are the backbone
Spiderwebbing	Chunks formed first, relationships drawn in afterward	Regroup around the real relationships, never just redraw arrows
Wheel-and-spokes	Sound chunks, every link radiating from one hub	Connect the chunks to each other, not only to the centre
Overloaded chunk	More than four branches off one node	Split into sub-chunks
Single-node chain	One in, one out	Merge it; a terminal node merges into its parent
Pretty but unretrievable	The map satisfies the eye and not the memory	Brain-dump it closed-book and repair what would not come back
Skipped Skin	Rough notes never become an artifact	Schedule the pass; it can itself serve as a spaced session

The prevention for the three structural faults, waterfalling, spiderwebbing, and wheel-and-spokes, is one procedure: textbook hierarchy → flat list → relationships identified → chunks formed from those relationships → map. The list step exists to strip the material’s grouping bias before any chunking happens. Reverse causality, worked once: mRNA is important because it creates protein. That is an arrow pointing at what mRNA produces. The relationship rests on rote, because the map gives no reason mRNA rather than anything else does the creating. The arrow adds an item to memorise instead of removing one. Flip the question: what produces mRNA, and what problem the cell solves by making it. Now the arrow carries logic that regenerates the protein fact for free. Intuitive chunking prevents the fault; importance checklisting and plain question-and-answer drilling breed it. When retrieval later fails, the failure carries its own diagnosis. No approach to a problem means a gap in how concepts relate, common where procedural drilling crowded out the conceptual network. A high volume forgotten is almost always a chunk-structure fault and never a plain effort fault: check the map for waterfalling and spiderwebbing, and check whether the chunks are intuitive. Recurring execution errors mean too little practice, sometimes downstream of a conceptual misunderstanding. Failure only in new contexts means missing relationships. Difficulty matters more than correctness: struggling marks a gap even when the answer came out right, and an answer sheet checked before producing your own answer manufactures the illusion of knowledge. The general form of every row above is one page: The Technique Is Only as Good as the Thinking It Produces.

What the workflow leaves you with

A structure simple enough to redraw with the sources closed, one that answers questions the sources never asked. The knowledge is easier to reconstruct, use, adapt, and improve. It was built during the learning, which was the whole claim. From there retrieval takes over, and the artifacts convert directly. Aim questions become the retrieval prompts, the map becomes their answer key, and the conversion runs after each Skin. Spaced Interleaved Retrieval then tests whether the encoding held and keeps it reachable long-term, with failures reading back as structural diagnosis rather than as a demand for more hours. The full pipeline runs on Prestudy, BHS, and SIR: Turning Information into Usable Structure.

The limits are known. The cost is front-loaded, and the front-loaded stage is where people who quit tend to quit. Progress is slow at first and then compounds as each new piece meets structure already built; measured over the whole arc, the early loss is made back even at early competence. The load never falls; you get better at carrying it, until passive study becomes the thing that feels intolerable. Mapping’s measured benefit outside this vault is a range, small to large depending on use and comparison, and not a single point. The system also names the material it handles worst: material that is not inherently logical, languages above all. Such material resists importance-based chunking, and the importance question does less work there.

How to practice this

1. Before opening the material, collect 15–30 keywords in about 25 minutes. Write a why-question and a how-question on each. Notice that you only write questions you cannot already answer.
2. Answer the questions on a map, backbone first, then concepts, then important details. Notice whether shooting feels easy; difficulty usually means the material’s order is steering.
3. Skin the map the same day or once a week. Redraw it with the sources closed and notice what does not come back.
4. Count the branches off each node and split any node carrying more than four. Notice whether the pass made the map simpler.
5. Try Hipshot only once the written cycle feels close to automatic. Notice whether relating drops out; if it does, return to the written loop.
6. Notice how a session feels. Easy or drowsy means nothing is happening. Overwhelming or confusing means relationships are surfacing.

Open questions

• Where does the boundary actually fall between an important and an arbitrary detail in a given curriculum?
• How much of the importance question survives on material that is not inherently logical?

Sources

• Prequestion meta-analyses (2023, 2025: Psychonomic Bulletin & Review; Educational Psychology Review): questions asked before study lift performance on the content they target (g ≈ .66) and almost nothing else (g ≈ .01). The support for Aim, and the constraint that makes coverage the variable.
• Dunlosky et al. (2013), PSPI: elaborative interrogation at moderate utility; Donoghue & Hattie (2021), Frontiers in Education: ten-technique synthesis, 242 studies.
• Cowan (2001), Behavioral and Brain Sciences: the working-memory capacity of about four chunks; the honest grounding for the branch ceiling as a heuristic, not a mapping law.
• Nesbit & Adesope (2006), Review of Educational Research: concept and knowledge maps, 55 studies: benefits small to large depending on use and comparison.
• Hattan, Alexander & Lupo (2024), RER; Simonsmeier et al. (2022), Educational Psychologist: prior-knowledge activation is real and conditional; prior knowledge correlates with knowledge gain at a mean near zero.
• The workflow itself, the three passes, the layer model, the schedules, and every operating default on this page (concept counts, chunk counts, branch limits, tier grades, coverage shares), is the learning system this wiki organises, stated as its own operating doctrine throughout.
• Kalyuga, Ayres, Chandler & Sweller (2003), “The Expertise Reversal Effect,” Educational Psychologist 38(1): instructional support that helps novices becomes overhead for advanced learners; bounds the family this variation belongs to, and tests nothing about the variation itself.
• Collins, Brown & Newman (1989), “Cognitive Apprenticeship: Teaching the Crafts of Reading, Writing, and Mathematics”: scaffolds are deliberately faded as competence grows.
• Four stages of competence: a broad practitioner frame, used here only for the vocabulary of “unconscious competence”; a frame, not a finding.