Building VialMath
We're building a real product in public — and showing the system behind it.
VialMath is a one-person software business run with a governed AI operating system — researchers, builders and independent verifiers that never grade their own work. This is how it actually gets built: receipts, constraints, failures and measurements.
Looking for the app? VialMath keeps your protocol coherent when one input changes — the product is over here. This page is the story of the build.
Why build in public
Transferable systems, with receipts.
Transferable, not proprietary.
We teach systems you can use on your own project — not private secrets, not a guru's "one weird trick".
Receipts over hype.
Every method comes with the constraint that shaped it and the measurement that tested it. Experiments are labelled experiments.
The product is the proof.
VialMath is the live case study. If the operating system weren't real, the product wouldn't ship.
The operating system
Five things we run, and what each one is for.
Described at the level that transfers. The internal controls, prompts and infrastructure stay internal; the shape of the system is the lesson.
-
An AI operating system with distinct jobs
Research, building, verification and governance are separate roles with separate briefs. The one rule that holds everything up: a chat that authors a change never approves it. Status is evidence-backed, never self-reported.
-
A side-business built from a recurring problem
A personal, repeating problem became a utility. The decisions worth showing: free versus paid, one-time versus subscription, and starting narrow instead of building a platform.
-
Product discipline
Issue-based development; exact-successor builds; negative controls that prove a test can fail; regression suites; independent verification. "Tests passed" is not the same sentence as "release-ready".
-
A growth laboratory
Hook research, experiment ledgers, reads on fixed clocks, and the difference between views and intent. No winner is declared from weak data.
-
Operational transparency
What the lanes did, what failed and how it recovered, and what changed because the evidence contradicted an assumption.
What lives here
Two things, as they're published.
The log
Episodes drawn from real operating events — a build that failed a gate, an experiment that didn't pan out, a number that turned out to be ours — with the sensitive details removed and the lesson kept.
The toolkit
Free, public-safe templates — the same shapes we use, with anything sensitive removed: an agent task brief, an independent-verification checklist, an experiment ledger, a decision log, a launch-readiness checklist.
Until the first episodes and templates are up, the changelog is the public record of what shipped, build by build, and the narrated walkthroughs are on YouTube. No newsletter, no membership, no counts we can't stand behind.
Relationship to the product
The product proves the method. The method built the product.
VialMath itself stays what it is: a content-free, local-first protocol calculator and tracker that computes from the numbers you enter and never tells you what to do. Nothing on this page changes that, and nothing here is a promise of income or outcomes. We show what we tried, what broke, and what the evidence said.