Projects
A selection of systems and study notes — built solo or with small teams, mostly to answer questions I had about how language models and software fit together. Code names used for anything internal; descriptions stay honest about scope without leaking specifics.
- Open Notebook
A self-taught study habit, kept in private. Papers I'm reading, evals I'm running, prompts I keep returning to. Some of it leaks into the projects below.
- Project Mercury
An AI-assisted intake. Reads incoming mail, classifies by type, extracts structured fields, routes to the right person. Replaced a brittle workflow engine with direct model-driven processing.
- Project Pilot
An always-on assistant for daily ops — triage, inquiry support, light analysis. Designed so recurring inference costs stay predictable and the failure modes are visible.
- Project Atlas
The dashboard the team opens every morning. Shows what's in flight, what's behind, and what needs attention. Started as a tracker and just kept growing.
- Project Bridge
Glue between a legacy system and the cloud. Syncs operational history, normalises messy fields and duplicates along the way, runs without interrupting anyone.
- Project Compass
A customer-facing portal. Track status, browse schedules, request quotes — live updates, no phone calls. Public, but the URL stays here.
- Project Lighthouse
A small public landing page. Smooth motion, clean layout, tiny bundle. Genuinely proud of how lean it stayed.
- Project Horizon
Schedules came in messy from many sources. This cleans them, matches them to the right reference data, and keeps everything synced quietly in the background.
Trade terms are dry to learn, so I made them less dry. Pixel-art characters walk you through each Incoterm, drag-and-drop tests what you remember, and there's a leaderboard for the competitive ones.
A small studio site — interactive knowledge map and a timeline of how the engineering and operations sides connect. Built on the same patterns as this one.