Socratic Tutor

A student's reasoning updates a record of established steps, which is used to check the tutor's next question before sending it. Illustration: check the next reply against what the student has established.
projects

The Socratic Tutor gives an AI study conversation a record of which steps the student has established. Before the tutor sends a reply, a local program checks it against that record and rules intended to hold back unreached solution steps. The conversation can then be reviewed against what the student actually said.

That restraint also exposed the central difficulty. In two recorded sessions on one microeconomics problem set, the tutor followed several session rules but struggled to teach unfamiliar material: an explanation could itself reveal a step the student had not reached. The system was better at assessing existing understanding than helping a learner build it.

An illustrative version of that failure pattern is:

Student: I don’t understand why this condition matters.

Tutor: Which part of the condition could you use?

Another question preserves the student’s chance to solve the problem, but it may provide little help with the missing concept. A more permissive teaching mode is still a design direction, not an observed solution to this problem.

What the program keeps track of

An AI agent conducts the dialogue; the Python program maintains the session record and checks proposed replies locally, without asking another model to judge every turn. Preparation defines the problem’s key claims, reference steps, glossary, and review criteria. During the conversation, word-pattern checks look for evidence that the student has established a claim or encountered a known pitfall.

When enough progress has been recorded, the reference steps are released for a comparison using quotations from the student’s messages. Pausing saves the transcript, summary, and learner record. Skip and defer rules allow incomplete parts to be parked, though the live runs found that returning to a parked question was too rigid.

The checks have limits: unfamiliar wording can be missed, unrelated phrases can trigger a match, and an agent can credit weak evidence. They provide an inspectable record rather than a guarantee against revealing an answer or misjudging understanding. Automated tests exercise the session rules; the live-run findings explain what happened in the two sessions. The README documents the current workflow.

For a hint or feedback on a single attempt, Tutor Diagnosis offers those tools within RAG Analysis. Guided Solutions describes a document workflow for keeping my reasoning and later tutoring work beside an agent’s reference derivation. Those are useful alternatives when I need a specific study task rather than a tracked conversation.

Aaron Scherf
Authors
Aaron Scherf (they/them)
PhD Student
I am a PhD student in Sustainable Development at Columbia University and a former USAID Foreign Service Officer. In Ukraine, I led the monitoring and evaluation team for over 50 development projects during the war. Previously, I worked on program design and social inclusion in Colombia, as well as budget analysis and knowledge management in Washington. Those experiences taught me how to ensure evidence is trustworthy and actionable, especially in conditions of rapidly changing and incomplete information. I now bring that perspective to research, data analysis, and practical software tools. I am available part-time for consulting and applied research collaborations.