Safety by Absence

Before I wrote software I homeschooled our kids for two years. Watch a child hit a fail state in a learning app — the red X, the buzzer, the timer running out — and you learn something no product spec will tell you: the failure screen teaches more than the lesson does. It teaches them what they are.

So our learning line has a rule that goes deeper than a design preference: no fail states, made impossible by architecture, not suppressed by a setting. There is no timer code in the kids' apps, so a child cannot be raced. There is no error-red token in the design system, so failure cannot be rendered. Not hidden — unbuildable. The safest feature is the one that doesn't exist. The line is COPPA-clean and everything a kid touches stays on the device.

The same thinking produced the ND line — Neuro Divulge. I'm ADHD, autistic, and dyslexic, diagnosed in my forties, and most "productivity" software is built by people whose brains hold a thread by default. Mine doesn't. The failure isn't planning — it's losing the thread between rooms, between tabs, between one thought and the next.

So the tools are built around structure, not willpower: ND Thread keeps one master list and one thing on the screen. ND Tendency tracks mood and habit patterns. ND Regulator teaches regulation skills — skills, not affirmations. ND Focus turns a week of scattered signal into a report you can actually hand a provider. They're in the store now, free to try, next to everything else we make.

One promise on this line above all: no efficacy claims, ever. An app doesn't treat anything, and we will never say it does. Structure around the day is what it honestly offers — built by someone who needs it, from the inside. That honesty is the product.