Scaffold repo: docs layout, guidelines and initial plan
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013kj58Jugkic783b8ZrtTVZ
This commit is contained in:
@@ -0,0 +1,21 @@
|
||||
---
|
||||
type: default
|
||||
---
|
||||
# Navigation service
|
||||
|
||||
Part of **Project Yukart**, making an old 2008 Mitsubishi Z27AG a bit smarter with modern technologies.
|
||||
This file serves as the minimalist portal to other docs
|
||||
|
||||
|
||||
## What this repo is about
|
||||
|
||||
Runs on the Orin. Answers routing questions and publishes turn-by-turn guidance
|
||||
onto the message bus, so no display has to know where routes come from.
|
||||
|
||||
Routing is served by a local Valhalla instance against artifacts built by
|
||||
[tool-mapmint](gitea:yukart/tool-mapmint), which is the offline-capable default.
|
||||
The provider is kept behind an interface so a cloud routing API can be swapped in
|
||||
without touching anything downstream.
|
||||
|
||||
- For implementation practice guidelines, refer to the [guidelines](docs/GUIDELINES.md);
|
||||
- For implementation plans and history, refer to [them](docs/impl/);
|
||||
Reference in New Issue
Block a user