Building in public.
Shipping daily.
Development updates, product decisions, and lessons from building an autonomous warehouse platform as a solo founder.
Modular Digital Twin: Splitting the Monolith
The warehouse twin started as a single 2,000-line HTML file. Today I split it into 8 ES modules: renderer, camera, scene, dock-doors, trailers, yard, pathfinding, and overlay. Each module owns its own state and communicates through the warehouse state engine. WebSocket security got hardened — every message now validates against the state engine before touching the twin. The yard management overlay with NXP-styled floating panels is live. Aisle-based pathfinding is queued next.
ONE Neural Engine: From 15 to 34 Modules
ONE started as a simple prediction engine. 20 days later it has 34 modules: Signal Bus, Guardian supervisor, Cortex learning loop, Predictor, Memory, circuit breakers, 6 vertical plugins, and 24 domain processors. The Guardian self-healing supervisor monitors every subsystem and auto-restarts crashed engines in under 2 seconds. Signal Bus processes 2,800+ events per minute. Every module emits structured telemetry. This is the architecture that makes sub-50ms response times possible.
Why I’m Building OMNIS
I spent 10 years on the warehouse floor. Dock worker, dispatcher, logistics coordinator, operations supervisor. I watched dispatchers assign doors with a whiteboard. I watched $150/hr detention charges pile up because nobody tracked dwell time. I watched supervisors lose 4+ hours a day to phone calls and manual coordination. Every warehouse software I used was either too expensive, too complicated, or missing the features that actually matter on the dock floor. So I’m building the one I wished existed. Node.js, Supabase, WebSocket, vanilla JS. No framework tax. Just the tools a dock needs.
Ready to see OMNIS in action?
Book a live demo and see every feature running on real warehouse data.