As developers, we build systems that adapt to users. But what does it look like when the system adapts to the learner's cognitive profile — not just their preferences or pace, but their actual neurological constraints?

I've been building a self-directed PhD curriculum in Applied AI/ML and logging every session: energy levels, focus quality, what clicked, what didn't, what the AI did that made the difference. The goal is a five-year longitudinal dataset of one neurodiverse learner using AI as primary educational scaffolding.

Here's the hypothesis driving everything — and what I learned when I actually started studying.

Here's What I'm Actually Trying to Prove

The other night I sat down to study linear algebra at what I'd call energy level 2 out of 5 — functioning but effortful, like moving through moderate resistance. Not a good day to learn anything. I opened my curriculum, started reading about fields and vector spaces, and something happened that I didn't expect.

I generated eight conceptual questions.

Not exercises I'd been assigned. Not prompts from the material. Questions I produced autonomously, across multiple topics, while cross-referencing two documents — at low energy, late in the evening, after a full day of work. One of those questions was meta: is this worth recording?

The fact that I even asked that second question is, I'm realizing, part of the research.

The hypothesis

I have a PhD thesis. Here's the central claim:

Augmented intelligence — AI operating as a bidirectional cognitive extension, calibrated to a learner's individual personality and cognitive profile — enables learning outcomes that traditional institutional models of education failed to produce. For neurodiverse learners whose cognitive profiles create significant friction at the task-initiation and conception-to-execution interface, this augmentation doesn't merely improve outcomes: it enables doctoral-level engagement that was previously structurally inaccessible.

That's the formal version. Here's what it means in plain language:

I've tried to learn this stuff before. Online courses. Graduate programs. I'd sit down, follow along, execute the steps, pass the tests — and retain almost nothing. I couldn't explain what I'd done. I could run Gaussian elimination but couldn't tell you what it meant. The knowledge lived in my fingers, not my head.

The programs called this my fault. The solution they offered was "spend more time reading." I did. Same result. Eventually I stopped.

What I'm arguing is that this wasn't a learning failure. It was an interface failure. The structure of institutional education — passive content delivery, scheduled assessments, no adaptation to cognitive state, no scaffolding for task initiation — is structurally incompatible with how my mind works. And that the thing that's changing this isn't willpower or more effort. It's AI.

Not AI as a search engine. Not AI as an autocomplete tool. AI as something more like an externalized cognitive scaffold — one that holds the thread when my attention drifts, externalizes the working memory I can't reliably maintain, and closes the gap between what I can conceive and what I can actually execute.

The theory comes from Clark & Chalmers' Extended Mind Thesis (1998): the tools we use to think with are continuous with our cognitive systems, not separate from them. My glasses aren't separate from my vision; they're infrastructure for it. The AI isn't separate from my thinking; it's infrastructure for it.

What I'm trying to show, over five years of documented study, is that this infrastructure enables doctoral-level engagement that institutional structures — for this learner, with this profile — did not.

The methodology is the message

Here's the part that I keep finding strange and fascinating: the way I'm producing evidence for this hypothesis is by doing the thing the hypothesis describes.

Every session is logged. Energy level, focus quality, mood, cognitive load. Every concept I struggled with, every question I generated, every moment of confusion and resolution. The questions I asked at energy:2 late on a Thursday evening are data. The fact that I generated eight of them without being prompted is data. The meta-question — is this worth recording? — is data about the research process itself.

The formal term for this is autoethnography: using rigorous first-person documentation as research methodology. I'm the researcher and the primary research subject simultaneously. The data I'm generating is a longitudinal record of one neurodiverse adult learner using AI as a primary educational tool — over what will be a five-plus year span.

To my knowledge, this kind of longitudinal dataset doesn't exist in the academic literature on AI education. That's part of what makes it worth doing.

The strange part — the part I find genuinely interesting — is that the research process itself demonstrates the hypothesis. I figured out the hypothesis through a Socratic dialogue session with an AI, working through my own cognitive experience systematically until a claim emerged. The derivation process is data. The hypothesis and the method are the same object.

What studying at energy level 2 actually revealed

Back to that Thursday session. Here's what happened, and why I think it's relevant to the research.

I was working through the foundations of linear algebra — specifically the concept of a field, which is the mathematical structure that underlies the number systems we use. Fields have eleven formal axioms. I didn't try to memorize them. Instead I worked on building one generative question: what can I do with these numbers, and can I always undo it?

That question — can I always undo it? — reconstructs most of what you need to know. Real numbers form a field because you can always divide (except by zero). Integers don't because dividing two integers often exits the set: 2 ÷ 3 isn't an integer. One question. Two examples. The structure follows.

But here's what I noticed while doing this: I would understand something completely while reading it, and then it would be gone the moment my attention moved. Not fuzzy — gone. I'd have to go back.

I've experienced this my whole life but never had a framework for it. What I know now, after logging it and thinking about it more carefully, is that there are two different things happening: processing and encoding. I can process content well — comprehension in the moment is fine. The transfer from working memory to long-term storage is where things break down. That transfer requires executive function support — sustained attention, active elaboration — and executive function is exactly what ADHD impairs.

So I'm not a bad learner. I have a specific interface incompatibility between my cognitive profile and passive content delivery. That's a design problem, not a character flaw.

And then something else came up, which I didn't expect at all.

The visualization thing

Someone asked me to describe what it looks like when I try to visualize a mathematical structure — say, a vector space. What I described was: something between a visual translation and a textual representation. Blurry. Non-static. It forms and then immediately dissipates. Not a picture, not words, but something in between that never quite stabilizes.

Memory palace techniques — where you build a mental house and attach concepts to rooms — don't work for me. The structure won't stay still long enough to attach anything to.

This turns out to be a recognized phenomenon. There's a spectrum from vivid voluntary mental imagery (hyperphantasia) to essentially no voluntary mental imagery (aphantasia). Most people assume everyone visualizes the same way they do. They don't.

The interesting part for the research: spatial-relational intuition and visual imagery are separable. You can navigate the relationships between abstract structures without forming a crisp internal picture of them. I described functions as "floating boxes with inputs and outputs" — that's spatial-relational thinking, not visualization. The channel exists; it just doesn't produce photographs.

What this means for curriculum design: the default assumption in most math education is that learners can build and manipulate internal visual representations. Diagrams in textbooks are meant to help you generate your own internal picture. If that generation isn't available, the diagram has to be the representation — exoskeleton rather than scaffold. The curriculum needs to build around that, not through it.

I'm logging all of this. Not because I have answers yet, but because the question of how cognitive profile shapes learning trajectory — when that trajectory is mediated by AI — is exactly what RQ5 is asking.

Why any of this matters for what I'm building

Hearth & Code isn't primarily a curriculum company. It's a research project that happens to be producing a platform.

The research question that drives everything: can AI calibrated to an individual learner's cognitive and personality profile enable learning outcomes that institutional structures failed to produce?

The answer I'm betting on is yes. The platform is how I test it. The PhD is the research log.

Every design decision in H&C comes back to this: not "what would make this feel like a good educational app," but "what does the evidence from a learner actually navigating this material actually show needs to happen?"

Right now the evidence is N=1. Mine. That's the point of starting here — to build the measurement infrastructure, establish the methodology, and generate the first data before trying to generalize.

The five-year plan is to have enough longitudinal data to make claims with research grounding, and a platform that has been designed around evidence rather than intuition. Intuition informed by lived experience is how I started. Evidence is how I'll finish.

What's next

The first module — Linear Algebra for ML — is in progress. The content is generated, the first session is logged, and the Checkpoint 1 computational exercises are the immediate next step. Python and NumPy, not paper. (Paper doesn't work for me. Now I know why, specifically, and it's in the research log.)

Phase B of the curriculum generation is queued: modules M02 through M18, covering multivariate calculus, probability, information theory, computability theory, algorithms, programming language theory, type theory, systems, databases, and security. All of it will be generated with the same learner-centered design principles: concrete worked examples, specific numbers, computational exercises, and no notation without explanation.

The PhD repo is public: github.com/hearthandcode/phd-applied-ai

The session logs are in there. The module content is in there. The thesis is in there, unfinished and honest about it. If you're curious what self-directed doctoral study actually looks like when logged rigorously and built in public, that's the place to look.

And if any of what I described about visualization, or the processing-encoding gap, or the interface incompatibility with conventional education — if any of that resonates with your own experience — I'd genuinely like to hear about it. That's also data.

Hearth & Code is building a gamified, adaptive, AI-native educational platform. The PhD curriculum is the research foundation. Both are built in public. If you're interested in where education is going when AI is the infrastructure rather than the tool, subscribe.