The Careful Machine
Evidence-heavy research AI that verifies every claim against its records before anything surfaces, and declines when support is thin.
retrievereasonverify evidenceciterefuse
buildingsecure ai systems, rag + evidence, ai eval harnesses, full-stack platforms, agentic workflows
AI you can put in front of real decisions: it reasons over retrieved sources, shows its working, and knows when to decline.
“Who approved invoice #4417, and under what authority?”
every claim ships with its records
“Had the vendor supplied them before 2024?”
the gap is named, nothing is guessed
Production systems I architected and shipped, built to hold up under real constraints.
architectural views only · sensitive implementation details intentionally omitted
Evidence-heavy research AI that verifies every claim against its records before anything surfaces, and declines when support is thin.
retrievereasonverify evidenceciterefuse
A gated, human-audited loop that improves local models only when a candidate provably beats the version it replaces.
correctioncandidateimmunity gateevaluatepromoterollback
An agentic toolchain that lets one engineer change large codebases at speed, with review and verification built into the path.
planchangetestinspectmergerevise
Small standalone packages, zero dependencies, one job each, with tests and CI. The reliability and control tools came out of one body of production work; the evaluation utilities are fresh implementations of standard methods. Published together in 2026, eleven of them on npm. Each one carries a CLAIMS.md mapping every falsifiable claim on its README to the test that enforces it.
A local dashboard for Claude Code: sessions, events, cost, worktrees and reviews in one loopback web app. Zero dependencies, no build step, and a real security boundary.
npx clawdeck-panel run --checkout /path/to/your/project · every release tagged, CI attached · issues welcome
The reference implementation of the pattern the tools share: the model proposes, deterministic code certifies, and every design rule is a test you can run.
five recorded live runs, claude-sonnet-5, captured 2026-08-31 · the live bench runs the published verifier in your browser
npm install @m-sanchez/<name>
Eleven of the tools are published npm packages under the @m-sanchez scope, and gpu-quiescence is on PyPI (pip install gpu-quiescence). The reference implementation and the study install from a pinned git tag.
Four of the tools in one reproducible experiment: route to specialists, freeze the bars, test the win, check the confidence. In the designed world routing clears the accuracy bar and fails calibration. Against a real model it simply lost, by 15 points, and the same instruments said so.
synthetic, seeded, every number pinned by test · real-model arm recorded 2026-09-02, 400 questions, claude-haiku-4-5 · routing lost
git clone https://github.com/m-sanchez/routing-study && cd routing-study && npm ci && npm test
These are weeks old. If one of them earns a place in your build, or fails to, an issue on the repo is the feedback I most want.
Full profile on GitHubWeighted to current AI and full-stack work; earlier roles in brief.
Education
MSc, Web & Mobile Application Development · 2011–2012
BSc, Computer Software Engineering · 2007–2011
Universidad de Sevilla · Seville, Spain
Which classical engineering disciplines survive contact with stochastic systems, and which problems are genuinely new.
Frontend, backend, data, and the glue between them.
Retrieved facts, citations, and refusal when support is weak.
Local-first, controlled, and reviewable, with a person signing off.
Agents accelerate the work without owning the decision.
Always happy to talk AI engineering, compare notes, or dig into a hard problem.