I investigate cases where a computational check says everything is fine, but the property it is supposed to establish has already failed.
One experiment replayed as VERIFIED while executing a 100,000-byte write under a 4,096-byte cap.
That has taken me from agent authorization and formal verification to scientific software and hardware verification. I tend to build the smallest experiment I can that could prove my idea wrong, then keep the result even when it does.
I use AI heavily in this work, including Claude, Codex and Cursor for code, research and drafting; the commit history makes that visible. I choose what to investigate, set the tests and stopping conditions, and decide what the evidence justifies claiming. Results that fail or narrow the original idea stay in the record.
Pinned below. If you read one, start with mcp-authority-boundary.
Merged, mine: common_cells #355 (a SymbiYosys proof for the ECC encoder and decoder,
which found an undriven syndrome_o), PyBaMM #5747 (a lithium-conservation fix in the
Basic electrolyte model), inspect-robots #425 (records the effective grader configuration).
Reported here, fixed upstream: inspect_ai #4602, inspect-robots #413, LemmaScript #206.
Open: cvc5 #12937 (approved by a maintainer, awaiting merge), cedar-spec #995, Strata #1448, genome-nexus #881, and two in Strata-CLI.


