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,23 @@
|
||||
---
|
||||
type: default
|
||||
---
|
||||
# Flutter display client
|
||||
|
||||
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
|
||||
|
||||
The in-car display. Renders vehicle telemetry and a moving map, and runs on a
|
||||
tablet connected to the Orin over USB or WiFi.
|
||||
|
||||
Flutter rather than native Android so the display unit stays swappable — the
|
||||
display is deliberately a separate unit from the compute, and nothing here should
|
||||
assume it will always be an Android tablet.
|
||||
|
||||
It is a bus subscriber like any other display: it talks to the message bus and to
|
||||
[svc-gw](gitea:yukart/svc-gw), never to hardware.
|
||||
|
||||
- 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