Mission
What the project is trying to build, how the first version is intentionally narrow, and which constraints define the initial robot.
/overview/index
This site is intentionally plain. It is meant to read like an old technical handbook: mission first, directory map second, operational assumptions always visible, and no marketing chrome.
LiDAR-centered mapping and bounded navigation between named locations.What the project is trying to build, how the first version is intentionally narrow, and which constraints define the initial robot.
How the repository is laid out across robot runtime, firmware placeholders, shared protocols, tests, and operator tooling.
How contributors are expected to discuss changes, describe validation, raise security issues, and flag safety-sensitive diffs.
| Area | Current emphasis | Notes |
|---|---|---|
| Identity | Established | Repository naming, licensing, and issue templates are already present. |
| Documentation | Primary reference surface | README, support, security, and contribution rules currently carry most of the project definition. |
| Subsystem code | Placeholder-heavy | Several directories exist to define shape and ownership before reproducible implementations land. |
| Deployment posture | Local-first | The project explicitly avoids assuming cloud dependency as the baseline control path. |
Read this site as a compact handbook for the repository: overview first, structure second, process and safety notes after that.