Choose a path · Aegion 0.2.6

Every path

Aegion opens on one selection page, titled Choose a path. Six cards are the programs. Each card is a whole process, from the moment you tap it until you come back. Markets and the system keyboard are not cards on this page.

How to open the apps is in Help. What leaves the device is in Your data. The rules for using them are the Terms of Service.

How the app starts

1. You open Aegion. On the laptop that is ./aegis. On the Tank it is the installed app, version 0.2.6.
2. The window lands on Choose a path. A status line sits under the title. A logs button sits at the top.
3. You tap one card. That program runs. Paths, or Back, returns you to this same page.
4. Nothing on this page is the classic GTK window. ./aegis --classic is a separate older program and does not show these cards.

Artemis

Subtitle: Aegis Engine. This is the asking program. The card says it asks from the library, facts, math, and answers taught on this phone.

1. You tap Artemis. The screen is the engine: a question box, a mic, and Ask.
2. You type a question, or tap the mic and dictate. On a hands-free turn you can say “Artemis, run query …” and the rest of the sentence is the question.
3. Aegion looks for an answer in this order, and stops at the first one it can stand behind:
   1. Taught on this phone.
   2. Pack corrections.
   3. “Teach me” or a tutorial you already saved. That opens the Tutorials page when the question is asking to build one.
   4. Math and units.
   5. Weather, exchange rates, and the time in a city. Those are live and are not stored.
   6. Sports. Teams and champions are offline. Scores, standings, and news are live. Finals can be logged. Live scores are not stored.
   7. Companies and stocks. Price, SEC filings, Wikidata, and headlines are live and are not stored.
   8. Confirmed facts.
   9. U.S. places.
   10. The laptop engine, when the laptop link is up: its store, its web search, and its AI model.
   11. Definitions.
   12. Stored answers, re-checked before they are shown.
   13. Pages already saved from the web.
   14. A new web search, which gathers pages and saves them.
   15. Library search over the offline pack.
   16. An optional local AI model, only if the earlier steps did not answer.
4. The answer is shown with where it came from. A wrong answer can be corrected. A correction beats the old one next time.
5. Signal Walk questions asked here are answered from the walks file, or turned into walk commands: “start a walk”, “stop the walk”, “summarize my last walk”.
6. Settings on this same screen hold the look, the voice, the web switch, Auto-train, the shared archive, the laptop link, local AI, and storage.

Shared archive, on this screen: the address is https://mindflux.online/aegis unless you saved a different one. It is one SQLite archive. Connected copies share teachings, the question and the answer. Keystrokes stay on the device. A separate Contribute switch, after you allow it, sends a Wikidata item number, property numbers, and an article title. Your data lists everything that archive holds.

Tutorials

Subtitle: Learn a subject. You name a subject. A sourced tutorial is built from the web and kept offline.

1. You tap Tutorials.
2. You type a subject, or dictate one. Examples the screen expects: “Python basics”, “the Ubuntu terminal”.
3. You tap Build tutorial. Aegion reads Wikipedia, Wikibooks, Stack Exchange answers, and documentation pages.
4. It writes one tutorial from what those pages say. Every part names its source.
5. The tutorial is saved on this device. After that it can be read with the network off.
6. The saved list can be searched by title, subject, and key concept. Tap one to read it.
7. Go deeper builds the next level: subsections and linked articles, one level at a time. If a deeper pass finds nothing new, that button stays quiet for a while.
8. Saved tutorials also answer matching questions later, from Artemis, and they count as known for Auto-train.

Saying “teach me …” from Artemis opens this same build, rather than inventing a tutorial inside the answer box.

Shield of Zeus

Subtitle: Trainer. You start from the first session, or you paste new questions and answers. The card’s badge shows how many items are waiting, or that the starter is ready or already on.

1. You tap Shield of Zeus. The first block is what this phone has already learned.
2. Apply starter session, when it is still offered, installs the first set of answers.
3. Paste training takes lines you type. A line with => saves at once as a question and its answer. A question alone waits in the queue for review.
4. The queue lists what is waiting and what has been taught. Open one to review it. Asking drafts an answer. Use this keeps it. A draft that is not an answer cannot be used.
5. Auto-train works through subjects on its own while the app is allowed to. Recently learned rows can be opened: Use this turns one into a teaching, Wrong removes it.
6. The tutorials block on this page queues subjects to build next, one per line. A line that starts “how to” is treated as a how-to. Add subjects sends them to the tutorial builder. Recently built tutorials can be opened and read.
7. On the laptop, this page also holds Guardian’s process scan: process names, listening ports, and file hashes under Downloads, Documents, Desktop, and /tmp. The scan only reads. It does not change files. A summary, a score and counts with no file paths, can be sent to the MindFlux archive. Guardian is not its own card on the selection page.

Handshake

Subtitle: Handoff. What this phone knows, live tests, training, and settings. Five tabs, then back to the paths.

1. Handoff writes a short account of this device: counts and teachings. You can copy it into another chat. It does not include keys or a .env file.
2. Query runs a self-test of seven questions through the phone engine. Weather and the web stay offline for that test.
3. Training shows the Shield of Zeus state and recent teachings, and can open the trainer.
4. Storage shows what is taking space on this device.
5. Settings holds voice and local AI. The same switches also live on Artemis.

Signal Walk

Subtitle: Radio walk. On the phone the card logs radios along a GPS walk. On the laptop the card opens the viewer for walks already saved.

On the Tank

1. You tap Signal Walk. Aegion opens the walk recorder that is built into the same app. Aegion pauses behind it. Back returns to Choose a path.
2. A walk records Wi-Fi networks, Bluetooth devices, and cell towers, with the GPS point and an estimated distance to each.
3. The walk is saved on the phone in Download/signalwalk/walks.db. That file is Signal Walk’s own database. A session summary can go to the archive at mindflux.online: when the walk was, the sample count, and radio counts. The coordinates and the full samples stay in that file.
4. From Artemis you can say “start a walk”, “stop the walk”, or ask about the last walk. Those commands talk to this same log.
5. If the recorder does not open, the card says so and the reason is in Logs.

On the laptop

1. You tap Signal Walk. The viewer opens inside Aegion. It does not record a walk. Recording stays on the phone.
2. It reads the newest walks.db it can find: one pulled from the phone over USB, one synced from the laptop link, a copy under Downloads, or the copy the desktop app keeps.
3. The screen shows a radar of every radio, drawn from the walk’s own coordinates, a device list with filters, search in plain language, and a JSON export.
4. On a desktop, Full map opens the same walk in the browser, including saved places. The map page is read-only here.
5. Pull copies Download/signalwalk/walks.db off the phone with USB debugging. The Tank on USB-C is that pull. A copy made on 5 October held 33 walks and 30,651 samples.

SignalDub Studio

Subtitle: Audio and video. This card exists only on a desktop where ~/signal-dub/app.py is installed. On the phone the card is not shown.

1. The card text says it dubs and mixes audio and video in the browser, and names anything still missing: its own virtualenv, or FFmpeg.
2. You tap the card. Aegion starts SignalDub’s own server if it is not already up. That start can take several seconds. The badge says “starting…”.
3. The server is SignalDub’s program, not Aegion’s. It listens on http://127.0.0.1:8766/.
4. When it answers, Aegion opens that address in the browser. If the browser does not open, the badge shows the address so you can open it yourself.
5. If it does not start, the badge says “didn’t start” and the card shows why. A log is written under the Aegion data folder as signaldub.log.

What the six programs share

Back on Choose a path, the six cards are still the whole selection. Logs, from the button on that page, is the record of what those programs just did.