ARCH // GLITCH CORE · 00
You are entering a living system manual.
The portfolio language settles here into verified paths, commands, and configuration sources.
PERSONAL SYSTEM MANUAL
MIXED SOURCES · 2026-08-24
08 — Applications and workflows
Verified launch paths and detected applications
CONFIG Sources: active binds, Caelestia app settings, desktop files, and autostart.
| Application | Launch path | Verified evidence |
|---|---|---|
| Kitty | Super + Enter | active Hyprland binding |
| Thunar | Super + E | active binding and Caelestia explorer |
| LibreWolf | Caelestia launcher favourite | local desktop files; profiles were not inspected |
| Spotify | automatic after 2 seconds | Flatpak command in autostart |
| GoofCord | automatic after 3 seconds | command in autostart |
| Virtual Machine Manager | local desktop launcher | VM state was not inspected |
Super + D invokes $menu = wofi; Super + Space opens the Caelestia launcher. These are separate launchers.
Verify one launch path
Section titled “Verify one launch path”Use the generated shortcut explorer to confirm the combination, dispatcher, argument, and source line. For a desktop launcher, inspect only its Exec= and related public fields; application profile contents are outside this manual’s audit boundary. For autostart, distinguish a configured command from a process confirmed at runtime—the stored configuration proves intent, not later process health.
If an application fails, check whether its executable or Flatpak application ID is available, then run the same launch target from a terminal to capture an error. Correct only the proven binding, desktop file, or package boundary. Verify both direct launch and the original launcher path. Restore the copied desktop/configuration file if the change creates a regression.
Related: Troubleshooting and Keyboard workflow.