Why Synapse exists, the convictions behind its design, and the principles that govern how it is talked about.
The founding motivation was preparing children for an AI-shaped future through adaptive, patient, one-on-one tutoring, rather than a one-size-fits-all institutional model. The developer's own grandchildren were the first test users, and real testing with them (not simulated) shaped early design — for example, a 10-year-old sustaining 10+ minutes of unprompted engagement on a self-directed topic was an early signal the tutoring approach worked.
The explicit design intent is that Aria assists a teacher rather than replacing one. Aria handles individualised, always-available tutoring that no teacher can provide to every child simultaneously, while keeping the teacher informed and in control. This is not a slogan bolted on afterward — it shapes concrete design choices:
The conviction behind the Social Resilience feature is that social confidence is built through practice, not information delivery. This led to a specific design principle: universal access. Every child has the feature available, not just those flagged with an identified need, because:
"Universal" here describes the design intent — what the product offers every child — rather than a switch Synapse forces on. In practice: a new family child profile has the space open from creation onward, with no adult step required first; profiles created before 11 Aug 2026 were not changed retroactively; and school accounts remain genuinely teacher-opt-in, because a classroom's default is the school's own safeguarding decision, not Synapse's. See Social Resilience for the precise current behaviour.
See Social Resilience for the full feature design.
The conviction behind the Director tab is that children growing up in an AI-saturated world need to understand AI, not just consume its output. Learning to direct an AI, recognise its mistakes, and question what it produces is treated as a literacy skill on par with reading — not an elective or a "nice to have."
See Director Tab (AI Literacy) for the full feature design.
The developer has a strong, stated preference to stay personally in the background and let the product and its process speak for itself. Content about Synapse should be written in the voice of the product, not a named individual.
The intended tone, as explicitly articulated during the pilot governance work:
Explicitly to avoid: marketing language ("revolutionary," "game-changing," "seamless"), positioning Synapse against other named products, making the developer personally prominent, and overstating the pilot's status — at various points it has been accurately described as "a conversation with one principal," not a deployment.
Putting the product through deliberately harsh, structured criticism — and publishing the findings rather than hiding them — is treated as a genuine expression of the "honest, not promotional" principle, not just a QA process. See Adversarial Review Process for what this produced in practice, including findings the developer explicitly said he could not dismiss.
The school-ownership model (see School Ownership Model) was arrived at partly for practical accountability reasons, but it is also consistent with the "assist, don't replace" philosophy applied at the institutional level: a school owning its own instance, data, and AI provider account keeps the school — not the developer — as the party in control.