A probe that has never failed proves nothing
Why executable claims need retained counterexamples, distinct failure states, and a gate that distrusts the confidence of its operator.
Writing
Technical notes, long arguments, and unfinished ideas shared before certainty sands away their useful edges.
Featured
Why executable claims need retained counterexamples, distinct failure states, and a gate that distrusts the confidence of its operator.
How Auths Proof translates its production Rust authority kernel through Charon and Aeneas, refines it against a readable Lean specification, and makes semantic drift fail CI.
I built Auths to separate identity from authority and make exact, bounded authorization portable across systems that will inevitably change.
Japanese taught me that understanding depends not only on what a sentence contains, but on what two people can safely omit.
Seventeen years of Japanese began with a year of kanji, followed by grammar dictionaries, half-understood podcasts, and comedy with captions.
A capsec diff of two published Rust crate versions shows why dependency review should include newly reachable filesystem, network, process, and FFI behavior.
How capsec makes filesystem and network authority visible in Rust types, what the compiler rejects, and where audit must take over.
Why auths-proof separates identity evidence, delegated authority, and application execution behind one offline verification contract.
How auths-proof turns layer direction, offline verification, deterministic CBOR, and protocol bounds into executable repository checks.
How auths-proof admits KERI, raw keys, P-256, Iroh, HTTPS, and other systems without letting them redefine permission.
What an honest formal map contributes to an open mathematical problem—and why preserving the red nodes is part of the result.