Why a control plane matters for hardware
The farther the system gets from toy examples, the more important run tracking becomes. A hardware program that cannot track what produced which artifact is eventually impossible to trust.
Back to atlas
Platform
Software control plane
Runtime Platform
A large part of this repo’s value is that it already thinks in platform terms. The public site should show that the hardware story is accompanied by operational infrastructure rather than isolated notebooks.
Key points
Operational discipline is part of the research moat.
The platform makes hardware work reviewable by people who are not reading raw logs all day.
This is a strong public differentiator because it shows the project is organized to iterate.
Web surface
Port 3006
The Next.js app is the operator-facing surface.
Control API
Port 4201
Run and artifact metadata live here.
Runtime API
Port 4202
Benchmark and runtime endpoints are separate.
What NeuroEtch already has
The repo already includes a webapp, two APIs, stored runs, stage status, benchmark history, and operator docs. That is enough structure to present the project as a real execution platform.
Dashboard and run history.
Pipeline and verification surfaces.
Separate control and runtime responsibilities.