Hey HN, I'm Oscar. After 15 years running a dev shop, I got tired of LLMs hallucinating project timelines and dependencies. They are word calculators, not scheduling engines.

I built Motionode. Think of it as "Cursor for technical planning."

How it works: 1. Paste a raw, unstructured requirements doc. 2. An LLM extracts the core deliverables. 3. A deterministic physics engine takes over—mapping the actual task dependencies and calculating the critical path based on your specific team capacity (e.g., 2 frontend, 1 backend).

The V0 Vision: AI coding agents fail today because they lack a strict architectural blueprint. By capturing the project as a deterministic graph from day one, we are building the unified layer where an LLM can eventually generate a V0 codebase without hallucinating.

I'd love for you to throw a messy requirements doc at it and tell me where my scheduling math breaks.