Selected work

Five questions,
made executable.

Each project makes a boundary visible: between identity and personhood, permission and action, confidence and evidence, an open problem and a solved one.

Who acted?

Auths

Decentralized identity and signing for developers, software supply chains, and budgeted agents.

Mechanism: KERI key-event histories, Git-carried attestations, and signed receipts make identity state and agent spend independently verifiable.
Boundary: Verification establishes continuity from deliberately trusted roots; it does not reveal or require a legal identity.

What were they allowed to do?

Auths Proof

A strictly offline reference kernel for proof-carrying authorization.

Mechanism: A sealed, effect-free pipeline turns untrusted bytes into a non-constructible VerifiedAction while every authority dimension can only attenuate.
Boundary: Time, trust anchors, status, registries, and resource limits are explicit inputs; the kernel deliberately owns no ambient effects.

What can the code do?

capsec

Behavioral safety for Rust through auditing, capability types, and runtime control.

Mechanism: Zero-sized proof tokens expose permissions in signatures; static analysis finds ambient I/O; runtime capabilities can expire or be revoked.
Boundary: Direct standard-library calls, unsafe code, and FFI remain explicit escape hatches surfaced by auditing rather than wished away.

What makes a claim trustworthy?

recurve

A framework that turns promises into falsifiable claims and drives agents behind an executable gate.

Mechanism: Every probe must reject a retained known-bad trap before it may certify work; GREEN, RED, and BROKEN remain distinct verdicts.
Boundary: Assurance is graded by the strength of each probe and its underlying oracle, never by the confidence of the agent.

How far can the discipline reach?

Navier–Stokes proof map

A machine-checked map of what a proof or disproof of the Clay problem would require.

Mechanism: Lean declarations, dependency ledgers, kernel-clean probes, and tamper traps keep proved, open, and unmeasurable claims honest.
Boundary: It does not claim a solution to the Millennium problem. Clay-side nodes remain open; proved model results validate the method, not the apex.