Why every regulatory change needs a record chain
A task list is not a control. Each step needs an authoritative record, a failure signal, an owner, and evidence required. Pairs with the regulatory-change workflow map.
Research & Field Notes
Field notes on change, proof, and limits.
Order follows offer mix. Each note demonstrates a method capability on a worked problem and closes on a workflow door. Delivery reconstructions live under Examples.
Evidence debt
The gap between a claim in circulation and the evidence you can produce under the scope that now applies. Shows up when you encode or freeze the current path.
When agreement is zero
What happens when an automated claim auditor fails blind gold: zero kappa, prompt fragility, and why you do not encode a review step you have not reconstructed.
A citation is not support
Why retrieving a relevant document is not the same as verifying a claim. The boundary between retrieval coverage and evidence determination.
Technical Game
Harnesses, scaffolds, and benchmarks live on GitHub
Evaluator internals, benchmark studies, and scaffold experiments belong to the technical game. They live on GitHub for technical evaluators rather than cluttering the buyer surface.
Open source
Technical repositories
Inspectable code, test suites, and calibration harnesses.
Apply these concepts to one of your workflows.
Start with a free diagnostic note.