StoryPath is a Grades 1–5 reading-based learning aide that turns practice into stories. This is why I built it that way.
StoryPath started with a piece of homework. My son had just turned seven, and he brought a worksheet home from school one afternoon. I sat down to help him through it, and I was struck by how little it explained. It asked him to practice an idea it had barely taught. The page was joyless and obtuse, and a page like that can make a seven-year-old think he is the one failing. He was not. The worksheet was failing him.
My work has me using AI constantly, so turning to it was natural. That night I used it to rebuild the lesson from the ground up, into something that actually explained itself. The realization that mattered came later. I had also been using AI to tell my son bedtime stories, and at some point those two things came together. A rebuilt lesson did not have to be a lesson that happened to be clear. It could be a story. We had read bedtime stories his whole life, and once I taught a skill inside one, it was obvious.
The story was not a coating on the lesson. The story was how the lesson worked.
He understood it, and then he asked for the next one. So we kept going. A little every night, we built StoryPath together. My best friend was also the best tester I could have had. He met every new thing I added with real excitement, and every night he pushed me to do more. His enthusiasm shaped every feature StoryPath has. I started Bardic Learning Systems to turn those evenings into something other children could have. StoryPath is what they became.
The thing I stumbled onto, that a lesson teaches best as a story, was not new. It was very old. Before there were schools, there were stories: the myth that explained why the seasons turn, the song that mapped the way to water, and the history a grandparent handed down so it would not be lost. For most of human history, a story was how knowledge passed from one person to the next. It was the original technology of education. Then schooling industrialized it. That brought real and important gains, scale and structure and access for millions, but it came at a cost, and the cost was immersion. The worksheet my son carried home is what that cost looks like up close. StoryPath exists to give the immersion back.
There is a second reason story is the form, and it has to do with reading itself.
Reading is a skill of its own, and it is built in only one way, by reading.
Many learning apps move in the other direction. They splinter a lesson across as many channels as they can: a video here, a narration there, a game mechanic standing in for what reading used to do. StoryPath does the opposite. It is a reading experience that happens to teach. A child using it is reading the entire time, so every lesson is reading practice as well, whatever else it is teaching. Choosing one form and committing to it is not a limitation. The focus is the strength.
I should be honest about where I started, because it was not from optimism. I have three children, and I have watched what a screen can do to a child: the slack face, the gone look, the pull of content built so that stopping feels like work. Our home is not relaxed about devices. We work to limit what our children take in, because I have seen how little some of it gives back. Starting to build with AI did not soften any of that. It made me hold it closer.
A screen can hold a child’s attention completely and develop almost nothing.
Engaging and nourishing are not the same thing, and much of what is made for children is the first with none of the second. Video is the clearest case. It can absorb a child for an hour and ask nothing of them. AI does not settle this question. It sharpens it. The same technology can be aimed at a child to capture them, or it can be aimed the other way, and a tool does not decide which. The person who builds with it does.
That responsibility is the whole job, and it comes down to a single idea I keep returning to. Every one of us is building a toolbox, a collection of things we know how to use. Schooling often treats that toolbox as the destination, as though the point were to memorize its contents. It is not. Consider paint. Manufacturing it is mechanical work, the kind automation already does much of and may one day do entirely. No one is moved by that. We are moved by the painter, the human mind that takes the paint and makes something no one has seen before. That is the uniquely human act, the thing we most celebrate in one another, and it is what an education should build a child toward. The toolbox matters, but only for what it makes possible: someone who can take what exists and create what does not yet exist.
StoryPath runs on the very screens I worry about, and I want to be plain about that. The screen was never the problem. What fills it is. A screen is only a surface. It will carry something hollow as readily as something worthwhile. What StoryPath puts on it is a story, one a child has to read, follow, and think their way through. It asks something of a child rather than only holding their attention.
Time inside StoryPath is time spent, not time taken.
StoryPath began at one kitchen table, with one seven-year-old and the worksheet that started all of this. It exists now because the help I was able to give him that night should not depend on a child happening to have a parent who knew how to rebuild a lesson. Every child deserves to learn from something built with care, something that respects a child’s attention instead of mining it and asks for their real effort in return.
That is the whole of it. A Grades 1–5 curriculum a child will want to read, made by someone who came to this work wary and stayed that way, because I am raising three children of my own. My hope is plain: that a child opening StoryPath feels what my son felt on those nights, that learning is something you get to do, not something done to you.