Portfolio
Zack
Forward-Deployed Engineering portfolio
The short version
The universe, being fond of irony, arranges for the costliest errors to be the quietest ones. So I build AI that is constitutionally incapable of keeping a secret: it works inside the systems you already run, every action is gated by code no prompt can flatter, every send leaves a signed receipt, and a human holds the release where it counts. The first domino stays standing because nothing is allowed to touch it.
What you actually get
Records that can prove they haven’t rotted.
Every section carries a fingerprint, plus a second check that catches an edit forging its own.
AI roles that don’t drift.
The role lives in the folder structure, not the prompt. A prompt can be talked out of a rule. A folder can’t move itself.
Rails that refuse instead of reporting.
In one audited session the written rule was skipped every single time. The gate that blocks was skipped zero times. So I build gates.
A new project wired in one command.
Connected both ways, and it refuses to finish if anything it registered doesn’t exist.
What you have to lose
Count the dominoes. A rule that only lives in a prompt fades during a long session. One reply goes out. The customer treats it as a commitment, because it came from your address. Now the question is “who authorized that,” and the honest answer is nobody, which is worse than the wrong person. So you freeze every automated send, and the tool that saved a step now costs one it never cost before.
Or the quiet one. A step changes a record and nothing happens for a month. Then a customer or an auditor asks why, and there’s no receipt, so the answer is “we don’t know.” You can’t prove it wasn’t tampered with. In some businesses that’s a compliance problem. In others it’s a lost account. In both, somebody switches the AI off, and the rollout you paid for is now a rollout you paid for twice.
That’s the bill: the margin on the bad quote, the hours re-checking everything the tool touched, the customer who stopped trusting your address, and the rollout itself. Every one of those started with a domino nobody was holding.
Don’t take my word for it
One piece of the machinery that holds the domino is public, on this site: the gate that decides whether the AI is allowed to send, and a signed receipt in the format it produces. You don’t have to be technical to check it. Hand it to anyone who is. One command. If the signature doesn’t hold, close the tab.
What you stand to gain
Trust you can show, not ask for: every action carries a receipt anyone can verify, so “who authorized that” always has an answer. Efficiency that survives the audit: the hours the AI saves stay saved, because nobody has to re-check what it touched. Margin you keep: the quote that goes out is the quote you meant, and the send nobody authorized doesn’t go out. And the rollout you pay for once, because nobody has to switch it off.
Five shipped systems. Verified receipts. One personal link. The résumé is public. One email gets you in.