About
Why GauntletCI exists, and who built it.
Eric Cogen -- Founder, GauntletCI
I spent twenty years writing .NET in production. Payments, internal platforms, line-of-business systems where a green build did not stop a 2 a.m. page.
The bugs that hurt me were rarely the ones tests caught. They were the assumptions I did not know I was making. A guard clause removed in a "cleanup" PR. A method renamed from Delete to Get that still deleted. A catch {} swallowed under cover of a 200-line reformat. None of these failed code review. None of them failed CI. They failed customers.
After enough postmortems, I started writing down the checks I was running by hand on every diff. Look for removed lines. Look for signature changes without test changes. Look for new throw new without a matching Assert.Throws. The list grew. It became a habit. The habit became a tool.
GauntletCI is that tool. Thirty deterministic rules, every one tied to a production failure I either caused or shipped through. It runs locally in under a second, on every diff, before code review even starts.
Where to go next
- Browse the 30 deterministic rules -- every rule maps to a real production failure.
- Why tests miss bugs -- the six categories of risk that escape green builds.
- Why code review misses bugs -- the human limits of diff review at scale.
- The original STORY.md -- the long-form scar tissue narrative on GitHub.
