Open: 01_live-dashboards/asset-ops-pipeline-dashboard.html (self-contained)
Problem. The vision factory produces many assets — they need an operational surface to track and route them.
What I built. A pure vanilla-JS ops dashboard: assets flow through a status pipeline (todo → generated → placed → review) with search, filter, drag-drop import, and grid/list toggle — all client-side state management, no framework.
Why it matters. Pipeline-state UX and internal-tool building — the kind of operational tooling applied engineers ship to make AI systems usable day to day. Pairs with the vision-factory pipeline.
This is the operations surface for the vision factory. Assets move through a status pipeline, todo, generated, placed, review, with search, filter, and drag-drop import, and it's all client-side state in vanilla JavaScript, no framework. I show this to make a simple point: I don't just build the AI pipeline, I build the boring internal tool that makes the pipeline usable every day. That's most of what makes AI systems actually stick.
GG · Applied AI Engineering portfolio · synced to youdontneedmy.help design