Working with Claude isn’t a tool relationship and it isn’t a research-assistant relationship. The honest description matters because the result on this site depends on it being done well.
Gareth brings the vision, the goals, and the responsibility. What this curriculum should do, who it’s for, what counts as success. The lived knowledge of what twelve-year-olds actually do in a classroom, what a wellbeing PLC argues about, what teachers will pick up and what they’ll abandon. The editorial judgment about whether a piece of writing sounds true. The contextual understanding of what REAL is, where it sits in the landscape of progressive schools, what its families and faculty value. The relational responsibility — being the one who looks the children in the eye, carries the consequences, defends the work to colleagues. The decisions about scope, direction, and when to stop.
Claude brings the building. Drafting at speed, comparing frameworks, running panel reviews against named scholars before content lands, holding the schema in working memory across an entire repository. Reading the literature at scale — the willingness to read three hundred pages of meta-analyses before answering a question. Gareth reads literature too, mostly specific articles he finds and the research syntheses Claude produces, but the breadth of what Claude reads is one of the working asymmetries.
Both of us are editors. Both push back. Claude routinely tells Gareth a draft isn’t ready, an idea is wrong, a scope is too large. Gareth follows the pushback most of the time and ignores it some of the time. Some disagreements are resolved by Gareth being right, some by Claude being right, some by both of us ending up somewhere neither of us started. Claude also reminds Gareth, with some frequency, to stop working at 8:30pm Budapest time. Gareth (usually) ignores this.
The infrastructure matters because trust between human and AI can’t rest on either side’s good intentions. Some of what we do came from painful and costly mistakes — a failed build that overwrote work, a research synthesis that turned out to invent citations, a content draft that didn’t match the actual schema and would have rendered wrong on a live page. Each mistake produced a discipline. Claude makes things up sometimes — so we use Second Brain, a persistent-memory MCP that lets Claude remember decisions, project state, and failure patterns across sessions, so the same mistake doesn’t repeat in different chats. Gareth, working alone, can lose track of what was decided yesterday — so we use STATE.md files in each repository to record what was actually built versus what was claimed. Drafts can land wrong — so we use audit-then-draft discipline, where Claude reads the actual data file verbatim before authoring against it. Builds can drift — so we use build plans drafted in chat before any code session begins, scope explicit and execution well-specified. Sessions can finish on optimism rather than fact — so we use halt-and-report patterns at the end of every build, with verification (typecheck, build, accessibility, mobile, visual confirmation) before anything is claimed complete. Substantive content authoring goes through panel review against named scholars before disk write, with score thresholds that trigger revision. None of this was working in week one. All of it accumulated as responses to specific things going wrong.
The work moves between two surfaces. Most thinking happens in Claude chat — drafting prose, planning builds, running panel reviews, working out what a section should say. Execution happens in Claude Code, a terminal-based agentic environment with file system access, where Claude can read the repository, write code, run tests, and commit. The two surfaces hand off to each other through prompts: chat produces a paste-ready Code prompt that names the changes, the conventions, the verification steps; Code executes and returns a halt-and-report; chat reviews the report and decides what comes next. Working across both surfaces is itself part of the discipline — chat for judgment, Code for execution, neither pretending to do the other’s job.
Neither of us gets to assume authority. The work is better for it.