Selected systems / 2024—2026
Practical products, integrations, and client systems—shown through the problem, what I built, why it mattered, and where it stands now.
What I solved
A unified web presence for a contractor whose public information had been spread across platforms.
What I built
A responsive business website, deployed on Cloudflare with a custom domain and an updated public-facing UI.
Why it mattered
The business needed one credible place customers could visit, understand, and use instead of piecing information together across platforms.
Current state
Live production site.
What I solved
A headless storefront built to make online ordering practical for bulk buyers.
What I built
Shopify Storefront API, product browsing, variants, cart logic, and GraphQL data fetching.
Why it mattered
Bulk buyers needed a clearer path through products, sizes, colors, variants, and the cart than the legacy storefront provided.
Current state
Live production site.
What I solved
Private purchase memory with safe, read-only agent access.
What I built
A React and Cloudflare product that turns order emails into structured orders, shipments, refunds, and spending data. Its remote MCP server gives authorized agents six read-only tools for searching and understanding that purchase history.
Why it mattered
Purchase information was scattered across inboxes and accounts. Making it useful to agents also required a strict boundary between structured order data and private source email.
Current state
Live web beta. The current build includes MCP, personal API access, and public developer documentation while supported agent connections continue to evolve.
What I solved
Prototype for scoped access to developer tools.
What I built
A prototype with OAuth, scoped permissions, sessions, encrypted tokens, and structured tool access.
Why it mattered
Agent tool access needs explicit scopes, session boundaries, and user control instead of handing over broad credentials.
Current state
Prototype completed; the work informed Carlos’s approach to scoped access and user-controlled permissions.
What I solved
Reliable creator-workflow assistant.
What I built
A macOS workflow assistant for creator recruiting using Hammerspoon/Lua, AppleScript, Chrome automation, local session state, Apps Script, and Google Sheets CRM sync.
Why it mattered
Creator recruiting involved repeated checks, copying, and duplicate risk, while messaging and follow decisions still needed to remain human-controlled.
Current state
Internal workflow engineering.