Longer write-ups of things I have built. The complete history is on the CV.
Development transcripts, scrubbed of secrets and personal data, read by Claude into typed findings. The confident ones arrive as pre-filled tickets.
A tool that reads engineers' transcripts has two ways to fail. It can send something it should never have sent, or it can produce findings nobody acts on. The second one kills it quietly.
Thirty-plus components published as an npm library and adopted as mandatory across an engineering organization of several teams.
A component library is not hard because components are hard. It is hard because every team wants a slightly different one, and every exception you grant is a bug you will ship in someone else's product.
An OpenID Connect server with an RFC 8693 token exchange, three resource servers, a client behind a backend-for-frontend, and an MCP server for agents.
A person consents once, broadly. Every token after that has to be narrowed by intersection before it touches an API, and no exchange may ever widen one.
An MCP server in front of id, inventory and social. The user asks in a chat box, and the server mints one token per audience and calls each API as them.
A chat box beats a user interface for anything you can say in one sentence — but only if the agent can reach several APIs on the user's own authority, without ever holding their credentials.
An SPA behind a backend-for-frontend holding three separately-audienced tokens at once, isolated by cookie Path, degrading visibly when one cannot be got.
A client needing three APIs must hold three tokens with nothing in common. If any of them can be sent to the wrong proxy, the whole narrowing scheme upstream was decorative.
