A Valid Tool Call Can Still Be an Invalid Effect
Permission to call a tool is only the beginning. What must be checked before a consequential action is allowed to take effect?
Read at ACM QueueFOUNDER, HALTSEAL
Control before
consequence.
I’m Scott Lee. I build systems for the moment software acts in the real world. Today, that means HALTSEAL: execution control before money moves.
New York area
01 CURRENT WORK
One payment.
A clear right to proceed.
HALTSEAL
Founder · Core system authorA new route is not
a new right to pay.
A $10,000 payout times out. The first provider cannot yet confirm whether it paid. A second path is available. Sending again could pay the same obligation twice.
I built HALTSEAL to put a decision at that boundary. Across the paths it governs, it checks the exact payment against current authority and evidence about earlier attempts before release.
BEFORE RELEASEHALTSEAL
May this exact payment
proceed now?
ACCEPT
The fresh checks pass.The exact payment, current authority and shared state pass.
HOLD
The outcome is unresolved.The original may have paid. It may still pay.
REFUSE
The payment is not allowed.The obligation is paid or the payment exceeds its authority.
Decision before action.
Proof before consequence.
Payments are the starting point. My ambition is a dependable execution layer for AI: a clear right to act, checked while the action can still be stopped.
Where the work standsPublic demo and synthetic evidence.
Customer-hosted validation is the next milestone.
02 WRITING & RESEARCH
Ideas you can inspect.
The ideas behind
the systems I build.
EssaySeptember 2026
What Are We Saving Time For?
If AI gives us back an hour, I hope we leave some of it open.
EssaySeptember 2026
The Plan Can Change
Why I started with payments, and what dependable delegation requires.
IETF DatatrackerIndividual Internet-Draft
Permit Receipts for consequential machine actions
My individual Internet-Draft submitted to the IETF proposes verifiable authorization evidence before AI-agent and workload effects are committed.
Review the public evaluation codeU.S. patentsIssued & allowed
Machine authorization and execution controls
My related work includes 25+ U.S. patents issued or allowed for issuance, spanning machine authorization and execution controls.
FinextraAuthor archive
Agentic payments and the authority to act
Essays on how permission, incentives and the final payment can diverge.
03 THE FOUNDER
Built from
experience.
The person on the receiving end
is always part of the system.
I build around a simple belief: powerful systems should give people more agency, and earn the trust they ask for.
I founded Gooroo to make good teaching easier to reach. We built a marketplace that reached more than $1 million in annual recurring revenue and a network of more than 1,000 tutors.
Building and operating that business taught me that trust lives in the details: what was promised, what was delivered and whether the person on the other side could rely on it.
That experience shapes HALTSEAL. I wrote the core system myself. My related inventions and public technical work explore the same question: what gives a machine the right to act? The ambition is large; the work starts with one payment and a decision we can inspect.
I studied Operations Research at Columbia Engineering, worked in treasury at J.P. Morgan and served as a sergeant in the Republic of Korea Army. Those experiences shape how I build: think clearly, follow through and stay accountable to the people affected.
$1M+ARR milestone reached
while building Gooroo
while building Gooroo
1,000+Tutors in the
Gooroo network
Gooroo network
04 LET’S TALK
The next chapter
starts here.
I’m looking for people who want to make this real: payment operators, builders and investors who care about the infrastructure behind trustworthy AI. If that’s you, I’d like to hear from you.
Have a payment workflow to discuss?