I build systems that have to prove they're right — identity, agents, and receipts you can check.

AI ENGINEER × IAM × AUTHOR

SEC.01 — PROOF

What you can verify.

Numbers I can re-run or open in a browser. Density of proof, not volume of projects.

6
steps in the proof-gated learn loop
SLUICE · same-run pass only · local
19
UI components browser render-verified
code library · registry-backed proof
44
gear sectors under honesty gates
Righteous Recon · truth-gate · noindex
5
IAM mechanisms you can hit
Northbridge · JWKS · live sandbox

plus: public-key (JWKS) verify · ~1s revocation · two-person approval · million_dollar_claim_allowed: false · ReVerse: 1 custom MCP · 28 typed tools · 107 stress-tested palettes · Jo offline gate 14/14 scam STOP

SEC.02 — KERNEL

SLUICE — the proof gate.

SLUICE is a local proof gate for agent work: claim → source → check → receipt, pass or fail. Hooks push the must-not gates; thin MCP tools expose standing context, recall, learning, loop metrics, and canon audit. MCP is callable, not enforced. Nothing promotes without a passing proof.

The loop never trusts itself. That's the point.

Every cycle binds a claim to evidence before anything ships. Pass the proof gate, get a receipt. Miss the threshold, get rejected — and the rejection is logged too.

task enters with a budget
claim is stated explicitly
verify claim ⇄ evidence
gate same-run proof required · else hold
receipt stamped either way
IN FLIGHT
ZG_KERNEL — agent loop
> task.received"verify: northbridge revocation ~1s"
> plan.compiled3 steps · budget 12s
> exec.step[1/3]fetch JWKS · keys=1 · ok
> exec.step[2/3]revoke token · ~1s · ok
> exec.step[3/3]replay attempt · denied · ok
> claim"revocation propagates in ~1s"
> verifyclaim ⇄ evidence · MATCH
> proof.gatePASS · scored 96/100
> receiptstamped · sha256:9f2c…
> task.closedloop complete
demo receipts · this visit: 0static transcript

demo loop · synthetic tasks

SEC.03 — CASEFILES

Projects, with the why attached.

Flagship systems stay here. Apps and satellite surfaces aggregate under Apps / Sites — open one for the why.

SEC.04 — ARSENAL

Tools I actually use.

The stack behind the work above — only tools that show up in real projects. Tap one to pause the belt.

SEC.05 — DOCTRINE

Three rules you can check.

01

HTML is truth

The page still reads and works if you kill the scripts. Structure isn't decoration.

02

Status is honest

Live, prototype, private, draft. Labels match reality. Nothing here claims a state it hasn't earned.

03

Proof over polish

Claims bind to evidence — receipts, gates, audit trails. The demo above shows a rejection on purpose: real systems get told no.