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

LayerWhereWhat moves
Application~/Documents/Aegis-TerminalThe repo. This is the thing you copy.
LifecycleHome directory and ./aegis-serviceStart, stop, and the login service.
System/usr/local, systemd units, udev rulesPointers. 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

You teach it Corrections win. They are yours.
It reads Pages and tutorials stay on the device that fetched them.
It checks A curious fact is kept only when the article and Wikidata agree.
It shares A phone may send a Wikidata id and property numbers. It does not send the question you typed. The server fetches the article itself before it publishes anything.
The keyboard GIF search sends the word you asked for, not the message you were writing.

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:

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.