Framework

Pedagogy

How AMF thinks about learning and skill development.

Pedagogy: How AMF Thinks About Learning


Most musicians get better through repetition and hope. You play something enough times and eventually it sticks — or it doesn't, and you move on to the next thing. There's nothing wrong with that instinct. But it's not a system. It doesn't tell you why something isn't sticking, when to move forward, or what "getting better" actually looks like for this specific skill.

This section answers the question AMF was built around: How do I actually get better? Not in the abstract. In practice. On a Tuesday at 7pm, with thirty minutes and an instrument.


The Practice Model

AMF is built around micro-sessions — three 15-minute sessions per day, per instrument. With two instruments, that's six sessions per day. Six days a week, one day of free play on both instruments. No marathon sessions, no grinding. The research on how skills develop (spacing effect, deliberate practice theory, motor learning) consistently shows the same thing: short, focused sessions spread across days outperform long, infrequent ones for both retention and transfer. Playing for three hours on Saturday doesn't build the same neural pathways as three focused 15-minute sessions six days a week.

But frequency alone isn't the mechanism. The key is what deliberate means.

Deliberate practice is not autopilot repetition. Running through a chord progression until it feels comfortable is not deliberate practice — it's rehearsal of what you already know. Deliberate practice targets a specific thing that isn't working yet, engages full attention on the gap between where you are and where you need to be, and stops when focus degrades. Five clean repetitions of a voicing you're actively hearing and evaluating are worth more than twenty mechanical repetitions on autopilot. AMF's practice sessions are structured to stay in that focused zone, which is why they're short.


The Month Arc: Stabilize, Vary, Adapt

In Semester 1, the work moves through three phases — one full month each. Month 1 is Stabilize. Month 2 is Vary. Month 3 is Adapt. These aren't rigid divisions — they're stages of readiness that map to the semester's three months.

Stabilize. Get the skill clean before you do anything else with it. Slow tempo. Reference material available. You're not trying to use it in music yet; you're encoding it correctly. The goal is precision, not speed. A skill installed sloppily at full tempo is harder to fix later than a skill installed slowly and cleanly.

Vary. Once the skill is stable, move it across contexts — different grooves, different keys, different tempos, different emotional settings. This is where transfer begins. The skill starts to decouple from the exact conditions where you first learned it.

Adapt. Now bring PDC into it. Use the skill in real musical situations with full attention on what the music is asking for — including whether to use the skill at all.

The most important permission in this arc: if a skill isn't stable yet, don't vary it. There's no shame in spending six weeks in Stabilize. The arc is a readiness model, not a schedule. Rushing into Vary with an unstable skill just encodes inconsistency.


The 6 Mastery Levels

AMF tracks every skill through six levels. They run from first contact to full integration.

Level 1 — Exposure: You understand what the concept is. You can explain it in plain language. You haven't really played it yet.

Level 2 — Guided Execution: You can produce it on the instrument — slowly, with your reference material open.

Level 3 — Slow Recall: You can retrieve it from memory, without reference, at a reduced tempo. This is the first real test of installation.

Level 4 — Musical Use: You can use it in an actual musical context — over a backing track, in a real form, in time. It sounds like music, not an exercise.

Level 5 — Adaptive Use: You can choose whether to use it based on what the music needs. You can also choose not to use it — and that restraint is as deliberate as the deployment.

Level 6 — Integration: It's automatic. It shows up in your playing without being consciously activated. You're not thinking about using it; you're just making music and it's available.

The level worth working toward — the one that marks the difference between an executor and a musician — is Level 5. The jump from Level 4 to Level 5 is structural. At Level 4, you have a tool and you're using it. At Level 5, the music is asking for something, and that tool may or may not be the answer. The activation source has shifted from "I have this skill" to "what does this moment need?" That shift is what musical judgment actually is.


What's in This Section

This section contains two documents.

pedagogy-architecture.md is the full practice framework: how micro-sessions work, why the spacing effect matters, how deliberate practice applies specifically to music, what the month arc looks like operationally at each phase, and the historical and theoretical basis for AMF's pedagogical choices. If you're asking why AMF is structured this way, this is the document.

mastery-levels.md is the skill progression reference: all six levels with precise behavioral definitions, Definition of Done checklists for each level, worked examples across three AMF systems, and a multi-dimensional diagnostic for identifying which aspect of a skill is weakest. If you're asking where am I with this specific skill and what do I do next, this is the document.

If you read one thing first, read mastery-levels.md. Most practice systems fail not because the learner doesn't work hard enough, but because they don't have a clear target. Knowing exactly what Level 4 looks like — and exactly how it differs from Level 3 — changes what you do in every session.


A Note on Patience

AMF doesn't promise shortcuts. Musical skill takes time — real time, not the compressed timeline that most learning systems imply. What the pedagogy here is designed to do is make that time count: point your attention at the right thing, prevent the common failure modes (novelty-chasing, sloppy encoding, moving forward before skills are stable), and give you enough clarity about where you are that you're never just circling.

The system is honest with you. If a skill isn't at the level you thought it was, the Definition of Done makes that visible. That clarity can be uncomfortable. It's also the only thing that makes genuine progress possible.