Case studies
Each follows the same arc: problem, evidence, investigation, decision, fix, verification, lesson. Every number comes from Falkor's own dated records.
Execution-grounded claim verification
Published
Falkor's chat tools were silently switched off on every real turn, because the system prompt contained the word “Falkor”. The fix went further: each answer's claims are now checked against what the turn actually executed.
Preventing false-positive certification
Published
A certification harness that could declare success without evidence. A watchdog accusing a healthy store. 136 information sources shown as “active” that nothing ever ran. This is how Falkor learned to prove its own status.
Governing AI-assisted software delivery
Published
Nearly 3,000 commits since March, most of them written by AI coding agents working in scoped lanes, with handoffs, evidence gates, independent review, and an operator who overturns a “PASS” that isn't one.
Stopping a rewrite and rebuilding in place
Published
A from-scratch replacement demoed with 0 of 13 user journeys working. It was frozen, audited for its best parts, and Falkor was rebuilt in layers instead.
Working on something similar? Discuss a project, or see how I work.