Building with Papert at My Elbow — Some Wild Ideas

For the last little while I've been building a dashboard with Claude Code. It reads how students actually use generative AI; the real prompts they type into ChatGPT, Claude, Gemini and the rest, and presents that back to me as learning intelligence rather than as a compliance report. Partway through, I did something I hadn't planned. I pasted the whole system document into Gary Stager's Daily Papert chatbot and asked what it thought.

The site holds an archive of around 200 of Papert's texts, audio clips and videos, and the chatbot answers from it in one of three voices. The site is careful, and right, to say that this is an AI composing from documented writings, not Papert speaking. I'll be equally careful here. What follows isn't Seymour's judgement of my work. It's a synthesis of his published thinking, aimed at my work; which turns out to be a remarkably useful thing to have in the room.

The Daily Papert chatbot — one of three response voices, set to Conversation Mode.

The first thing it did was refuse to guess

I opened with something vague: I am building this idea with Claude Code — what do you think of my concept and the tool I am building? A limited description attached.

It asked me to share more of what I was working on, what I was trying to make happen, and what problem or opportunity had led me there. A small thing, but it set the register for everything after. This was going to be a conversation, not a compliment machine.

Then it named the tension I'd been circling

I pasted the full system document — the philosophy, the detection signals, the identity and timetable resolution pipelines, the deployment, the known gaps. All of it.

The response opened by naming what I'd been trying to do without quite saying it out loud:

You're standing in the middle of a genuine design dilemma. You have access to extraordinarily rich data — the actual prompts students type — and you've made a deliberate choice to frame that data as learning intelligence rather than surveillance. That choice runs all the way through the system, from the absence of a "violations" category to the fact that the individual student view isn't in the sidebar. Those aren't cosmetic decisions. They're philosophical ones.

It picked up something I'd built deliberately but never articulated; that I'd made it slightly harder to look up an individual student than to look at a whole class, and that this was the point:

That's a form of syntonic design — the structure of the tool embodies the values you want the user to adopt. The teacher who uses this system will be nudged, repeatedly, toward "what's happening in my Year 9 English class?" rather than "what is Sarah hiding from me?" This is the opposite of most administrative software, which makes individual compliance tracking the path of least resistance.

And then it went where I'd hoped it wouldn't have to:

The same data stream can support coaching or punishment, and the difference lives entirely in how the person holding the data chooses to use it.

You've designed the interface to nudge toward coaching. You've written the tips in a conversational register. You've removed the vocabulary of compliance. But you cannot prevent a punitive reading. A teacher who wants to catch a student cheating can use "delegation language detected" as evidence. The fact that you called it a "coaching opportunity" won't stop them.

This is the same dilemma I faced when we put computers in classrooms in the 1970s. We wanted children to program the computer — to be in control, to build their own microworlds, to think powerful ideas. But schools are institutions with their own logic, and institutions tend to absorb new tools into existing power structures. The computer that could have been an instrument of intellectual liberation often became a slightly fancier workbook.

I've read that argument through Seymour's work many times. Having it applied to a thing I'd built landed differently.

One sentence of context changed the whole reading

The reply had ended by saying the answer had to live partly in who gets access. So I told it: nobody has access. It's a tool for me, as an educational leader and a teacher, curious to know what is actually happening.

The reframe was immediate and, I think, the most useful thing in the entire conversation:

You're not building an administrative dashboard for widespread deployment. You're building an instrument for your own inquiry into what's actually happening when students encounter AI. That changes everything. You're building a learning observatory!

It called the thing a learning observatory — a way to watch learning happen at a resolution that's normally invisible, without disturbing it. It pointed out that my classification categories weren't handed down from a curriculum document; they were my working theory of what matters, and because I was the only reader, I could hold that theory lightly and revise it when...