deterministic controls around nondeterministic intelligence
Eighteen years running programs that move money: tokenization, browser checkout, audit and controls. Since January 2026, one person operating an AI production line that plans, builds, verifies its own work and records what broke. Five products came out of it. This page is the record.
the line, by the numbers
I write the ask. Scheduled lanes build and test it. Every change must pass its tests and an automated review; changes to deployment, to what the loop may do, or to its written rules wait for the operator to read them before they merge, and everything else merges once its checks pass and is read afterwards, with a revert path. The two numbers below are what that has produced.
five products · each row opens its page
seven stations · this page is built and tested on the same line
Work goes in as a written ask and comes out as a merged pull request. Between the two, the line plans it, builds it, and proves it works before anyone sees it. Every change must pass its tests and an automated review; changes to deployment, to what the loop may do, or to its written rules wait for the operator to read them before they merge, and everything else merges once its checks pass and is read afterwards, with a revert path. What broke gets written down and feeds the next pass.verify
the full walk-through →what the loop learned, in its own words
the short version
Computer engineer out of Venezuela. Online banking in Java before the cloud, then a decade of payments: tokenization, browser checkout. Now technology programs and controls: proving to auditors and regulators that a system does what it claims. Building with AI turned out to be the same job with a different kind of unreliability underneath. That is where the tagline comes from.
the correspondence is open