The map
How it fits
Three layers on the laptop, one app on every screen, and two small servers you choose to host.
On the laptop disk
| Layer | Where | What moves |
|---|---|---|
| Application | ~/Documents/Aegis-Terminal | The repo. This is the thing you copy. |
| Lifecycle | Home directory and ./aegis-service | Start, stop, and the login service. |
| System | /usr/local, systemd units, udev rules | Pointers. They are reinstalled, not moved. |
Two Python environments stay separate. .venv is the backend and Vosk. .venv-kokoro is torch. The Kivy build uses aegis-mobile/.venv. Merging them breaks either GTK, torch, or the APK build.
Trust boundaries
Servers you can put on chief
This overview folder is only for reading. Two other trees in the repo are real servers, and they should not be mixed with each other:
- server/ — PHP and MySQL. Checked facts for every phone. Needs a database, a salt, a cron key, and
verify.phpevery few minutes. keyboard-media/— PHP, no database. A JSON list of GIF files and the files themselves. Run it on the LAN at port 8088 and type that address into the keyboard settings.
Data you do not upload with this site
data/aegis.duckdb is the laptop library. The phone pack assets/aegis-pack.sqlite is built from it and is git-ignored. .aegis-doctor/backups holds hundreds of snapshots taken before edits. Their names are listed on the backups page. The files themselves stay on the laptop. Also leave behind ~/.config/aegis/phone-proxy.env, ~/.config/aegis/keyboard-emails, Firefox’s profile, and the Vosk model under models/. The overview describes them. It does not contain them.