[idrdex]

I'm the guest on this episode. MD/PhD (Penn), spent 14 years building clinical AI — from $38M in NIH-funded work at UCSF to a governance compiler that now runs breast cancer navigation (mammochat.ai), Caribbean cancer care (caribchat.ai), and real estate ops (gorunner.pro). Same architecture across all of them.

The core thesis: we should stop prompting AI and start governing it. We filed 6 patent families on AI governance — not the AI itself, but the compliance layer. The $2M Casey DeSantis Cancer Innovation Award (with support from AdventHealth, 51 hospitals) is funding a 20K-patient clinical trial on governed mammography AI.

Happy to answer questions about governance-first AI, clinical trials, or building from a garage in Orlando with six kids.

[iririririr]

who does governance of your governance prompt?

all the leaked models show even the model trainera cannot handle that effectively. they are full of all caps desperation trying to govern their inference. what exactly you did that they never thought of?

[idrdex]

Great question — it's the right one to ask.

There is no "governance prompt." The system uses versioned contracts (markdown files with explicit constraints), not system prompts. Every contract is in git — auditable, diffable, with full commit history. The agent that compiles the system reads those contracts via graph traversal and is itself governed by the same contracts it compiles.

The difference from what model trainers do: they govern inference behavior via system prompts — unversioned, unauditable, and fragile (hence the "all caps desperation" you're describing). We govern behavior via contracts that are data, not instructions. If the contract changes, the compiled output changes deterministically. No prompt tuning, no crossing fingers.

The mathematical basis is fixed-point theory. Brouwer's theorem guarantees a fixed point exists in any continuous governance mapping. Banach's contraction mapping theorem guarantees convergence. The contracts form a lattice (Tarski), so the system has both a least and greatest fixed point.

I wrote up the math in detail: https://hadleylab.org/BLOGS/2026-01-30-six-theorems/

The recursive part: the governance contracts govern the compiler, and the compiler compiles the governance contracts. That's the fixed point. It's not turtles all the way down — it's a contraction mapping that converges.

[iririririr]

isn't that's a lot of trust on illiterate things reading open ended text?

[idrdex]

Fair challenge. The contracts are open on a governed ledger (git) — versioned, diffable, auditable by anyone who cares to look. Every constraint, every change, every build output has a commit hash. No hidden prompts.

But here's the real point: the language of transactions on Bitcoin is precise. There is no question what the transaction amount is. There is a question what it's for. Same problem. Same solution: governance. Bitcoin solved the "how much" with cryptographic precision. We're solving the "what for" with governed contracts. The ledger records both the action and the specification that authorized it. If the specification is ambiguous, it gets amended — like any governance. The contraction mapping tightens with each iteration until the language is precise enough to enforce.

No ledger, no AI governance. That's the line.

[iririririr]

bitcoin works because it ignores governance!

its what you get if you have a double entry bookkeeper in an ideal vacuum.