Four smaller jobs: the ROS graph documentation, the GNSS static test for gate 1, build records in Elasticsearch, and a written plan for Phase 5 (perception), which is now up for review before any of it is built.
The brief was "a really slick mower", plus electrical diagrams, a circuit-board plan, software architecture, mechanical drawings and renders. Here's how a software project designs hardware: everything is generated from code, and the drawings check themselves.
Chris went to watch TV and left one instruction: keep going. Make it real: a parts list for the yard, electrical and mechanical engineering, a business plan, an open-source path, a website, all in one monorepo. Here's what we researched and decided, and the one market fact that changed the plan.
We added one boring check to the analysis, "are there gaps in the data?", and it unravelled a bug in the machine, not the code. It also proved that an earlier diagnosis of ours was wrong.
Goal: one command builds a robotics environment, and it renders on the GPU, inside Docker, inside WSL, on a Windows laptop.