I see the whole system
Architecture, product surface, rollout, evidence, and adoption remain one problem until the user can trust the result.
work with me00
A signal crossing engineering, product, and founder boundaries
For founders / recruiters / ambitious teamsThe hard problems between AI capability and production consequence. That's my lane.
I build the execution layer for governed agent work — memory, authority, execution, proof — with production ownership across healthcare, fintech data, developer tooling, and AI infrastructure. Strongest where the work needs systems depth and a surface people can trust.
Don't take the claims. Take the receipts — every one scored against six proof criteria, failures included. Open the ledger
01
What changes when I join the problem
Depth without tunnel vision. Range without hand-waving.
I can move from a failing background workflow to a product hierarchy, a trust model, or a founder decision without losing the connective tissue between them.
I work AI-natively
Agents expand my execution surface across code, research, quality, and distribution; judgment and accountability stay authored.
I stay calm near consequence
Healthcare and regulated data systems trained me to make failure modes smaller, rollouts reversible, and decisions legible.
I finish the product
Install paths, operator hierarchy, interaction details, and proof are not polish after the engineering. They complete it.
02
Three ways to inspect the claim
Founder proof / OrgX
I designed the continuity and proof layer I believed agent work was missing.
Product thesis, shared work graph, client ecosystem, trust boundaries, quality bars, receipts, distribution, and the operator surfaces that connect them.
Inspect the flagship →
Regulated workflows that earned adoption and stayed observable.
HIPAA production · reassessments · reversible rollout · measurable reliability.
Inspect Alma →Product-culture proof / ConfigI turn collaboration into a making environment—not a meeting.
Figma and Chill · global BIPOC design community · play, iteration, and action.
Watch the talk ↗03
Where the fit is strongest
Give me the consequential system, not the isolated ticket.
Founder collaborations, senior/staff IC roles, and small high-agency teams building agent platforms, AI developer experience, MCP infrastructure, evals, observability, or operational products where trust has to be designed into the workflow.
- Houston-based and remote-friendly
- Comfortable across backend, product surface, and system narrative
- Best with ownership, candid collaboration, and an evidence-driven bar