Planners, dispatchers and schedulers
People who override the model and have never once been asked why.
Spin up an idea, run it, show where it broke. Agents, optimization, math and sovereign AI: open, reproducible, and built to scale past the demo.
Have an operational constraint, messy real-world dataset, or production baseline to challenge? Email me at hello@gospinup.dev. Contributions and constraint overrides are credited in the spin.
Most technical writing describes an idea. A spin is the idea actually run — with the data it ran on, the code that produced it, the number it moved, and an honest account of where it fell apart.
Every spin follows the same seven sections in the same order, so you can skip straight to the part you came for.
Section five is the one that matters. A demo that only shows the working path teaches you nothing you can use. Everything here is MIT licensed and reproducible on a laptop.
The problem, in a practitioner's words
The data, public and linked
What I built
The result, with a number
Where it broke
Run it yourself
Discuss
An agent passes its eval and fails on day two. An optimization model hits its objective and gets overridden. A proof-of-concept works until the data has to stay in the country. Every spin here goes looking for that moment across AI, optimization, math and sovereign AI, with open code so you can check it yourself.
I write for the people who actually run these systems:
People who override the model and have never once been asked why.
OR people who can formulate the problem mathematically but haven't shipped an agent.
Engineers building agentic systems who've never had to prove a decision was feasible.
Anyone who has watched a technically correct plan get quietly ignored.
No prerequisites beyond curiosity and a tolerance for constraint notation.
Where I've presented this work, with slides and video where they exist.
Available for conference keynotes, technical workshops, panels, and podcasts. If you run a meetup, conference or reading group and this would be useful to your audience, get in touch.
Sessions & slide decksEssays and notes, published on Substack and LinkedIn, and listed here. Longer technical writeups live on this site, where the code renders properly.
Why a storage launch is on this notebook
essay22 days that shaped the AI landscape
essayA primer on Jev, the model that can't write a sentence, and what happened when I pointed it at live Google reviews.
Roughly twice a month: one new spin, or a note on something I got wrong. No pitch, nothing for sale, no course waiting at the end of it. Unsubscribe in one click.
Powered by Substack. Your address goes nowhere else.
Every spin has a thread on GitHub Discussions. If a constraint I mined looks over-fit, if my baseline is too easy, or if you've solved this properly in production and I'm busy reinventing it badly — say so there. Corrections get credited in the spin itself.