Orion vault — clean initial history

Knowledge vault (Orion/PARA) migrated from the pre-Orion 484vault on
2026-10-01. Deliberately orphaned: prior history contained a plaintext
password and stays local-only on branch archive/pre-boilerplate-history.
Secrets and live Hermes state are gitignored.

2. Areas/Home Personal/knowledge/hermes/hermes-memory/MEMORY.md

@@ -0,0 +1,11 @@
+Gotcha: avdmanager writes AVDs to ~/.config/.android — copy to ~/.android/avd or emulator can't find them. Omarchy SUPER+J togglesplit fails when workspace pinned 'scrolling' (~/.local/state/omarchy/workspace-layouts/<ws>.lua, written by SUPER+L) or focused window is floating (Hermes app window is floating).
+§
+Hyprland on this box wraps `hyprctl dispatch` in a Lua shim — classic syntax fails. Use Lua form: `hyprctl dispatch "hl.dsp.focus({window='pid:N'})"`, `hl.dsp.window.bring_to_top(...)`, `hl.dsp.focus({workspace='N'})`. omafiles is single-instance via shared ~/.local/state/omafiles/session.toml — test instances need isolated XDG_STATE_HOME. WirePlumber 0.5.17 gotcha: invalid monitor.bluez.properties drop-ins silently kill ALL BT audio ("Protocol not available" in bluetoothd) — verify endpoints via `busctl tree org.bluez | grep MediaEndpoint` after any wireplumber config change.
+§
+Keynctr dev mode: run `npx vite --port 5173` then `NOSTR_GUI_DEV_URL=http://localhost:5173 KEYNCTR_ENABLE_GPU=1 npx electron .` in frontend/ (after cargo build --release — Electron spawns target/release/keynectr serve). UI edits hot-reload; Rust edits need rebuild + backend restart. Amber fixes committed f917e5e.
+§
+Shonar desktop source lives only on branch deferred/desktop-server @7b34368 (removed from main 8c510f4); the dead ~/Projects/Shonar/desktop leftovers dir was deleted Sep 14. Separate live repo ~/Projects/Shonar Desktop (master, engine :8000 via desktop-dev.sh) still runs the desktop app. Runtime state ~/.config/shonar-desktop/ (settings.json read at engine start; engine.db).
+§
+Vizio E3D470VX TV: laptop flaps link then 'no signal' — fix = force 1920x1080@59.94 on DP output when Vizio detected (same as Epson projector fix). skill_manage gotcha: patch op needs old_string+new_string; file_content is ignored ('old_string is required' loop). Full rewrite of a references/ file = write_file op.
+§
+Avi's Wi-Fi (10.144.x.x) isolates devices — phone can never reach laptop LAN IPs; share local apps via cloudflared quick tunnel (~/.local/bin/cloudflared tunnel --url http://localhost:PORT) + qrencode QR (typing trycloudflare URLs on the phone fails). He rejects USB/adb workarounds.

2. Areas/Home Personal/knowledge/hermes/hermes-memory/RESTORE-HERMES.md

@@ -0,0 +1,33 @@
+# Restoring Hermes from this vault (computer-dies procedure)
+
+> **Path note (2026-10-01 Orion reorg):** `04-SYSTEMS/hermes-memory/`, `04-SYSTEMS/hermes-config.yaml` and `04-SYSTEMS/hermes-automation/` below now live under `2. Areas/Home Personal/knowledge/hermes/` (this file's own directory). Daily knowledge-routing now targets the Orion areas (`2. Areas/*/knowledge/`, `3. Resources/Research/`, `4. Decisions/`).
+
+If a brand-new Hermes instance is installed on a new machine, point it at this vault and it can rebuild itself from these pieces:
+
+## What's here
+- `03-SKILLS/hermes-skills/` — full copy of `~/.hermes/skills/` (learned procedures + scripts/templates/references).
+- `03-SKILLS/Knowledge Vault Skills Index.md` — machine-generated catalog of every skill (name, trigger description, path). Do not hand-edit; rebuilt hourly.
+- `04-SYSTEMS/hermes-memory/mnemosyne-export.json` — full Mnemosyne export (working memories, annotations, canonical facts). Restorable with the `mnemosyne_import` tool (`input_path` mode).
+- `04-SYSTEMS/hermes-memory/mnemosyne.db` — hourly WAL-safe live copy of the Mnemosyne DB (superset of the JSON export; use this if the JSON is older).
+- `04-SYSTEMS/hermes-memory/MEMORY.md` + `USER.md` — legacy Hermes memory + user profile.
+- `04-SYSTEMS/hermes-config.yaml` — Hermes config. Contains NO literal secrets (API keys are `${ENV_VAR}` references); the env vars themselves live in `~/.hermes/.env` which is deliberately NOT copied here.
+- `04-SYSTEMS/hermes-automation/` — `scripts/` (vault-sync.sh, skills-index.py, release-watch) and `cron-jobs.json` (all scheduled job definitions, so automation can be recreated without re-authoring prompts).
+
+## Restore steps for the new instance
+1. `cp -a "<vault>/03-SKILLS/hermes-skills/." ~/.hermes/skills/`
+2. Ask the agent to run `mnemosyne_import` with `input_path` = this vault's `04-SYSTEMS/hermes-memory/mnemosyne-export.json` (idempotent; skips duplicates).
+3. `cp` the two memory files into `~/.hermes/memories/`.
+4. Diff `hermes-config.yaml` against the new default config rather than blind-copying (schema may have changed).
+5. Restore automation: `cp -a "<vault>/04-SYSTEMS/hermes-automation/scripts/." ~/.hermes/scripts/`, then recreate the cron jobs from `cron-jobs.json` (names, schedules, and full prompts are in there).
+6. Re-supply secrets: set the env vars referenced in config (e.g. `HERMES_CUSTOM_*_API_KEY`) in `~/.hermes/.env`. These are NOT in the vault by design.
+
+## Automatic sync (running since 2026-09-11)
+- **Hourly** (cron `vault-sync-mechanical`, script `~/.hermes/scripts/vault-sync.sh`): mirrors skills dir, rebuilds the skills index, copies automation scripts + cron job definitions, memory .md files, config, and a WAL-safe live copy of the Mnemosyne DB into this vault. Silent unless it errors.
+- **Daily 11pm** (cron `vault-knowledge-routing`): agent reviews new memories/skills since `.last-sync` and routes them to `02-WORKFLOWS/`, `04-SYSTEMS/`, `05-KNOWLEDGE/`, `06-DECISIONS/`, `07-TROUBLESHOOTING/` as proper notes.
+- `.last-sync` in this dir marks the last successful hourly sync.
+
+## Known limits
+- Secrets (`~/.hermes/.env`) are intentionally NOT in the vault — a new machine needs them re-entered.
+- `~/.hermes/sessions/` (raw chat transcripts, ~360K) is not backed up; memory + skills are the durable layer. Say the word if you want transcripts mirrored too.
+
+Last verified: 2026-09-13 (by Hermes, full audit + gap fixes).

2. Areas/Home Personal/knowledge/hermes/hermes-memory/USER.md

@@ -0,0 +1,9 @@
+Design/doc preferences: no metaphor framing in design docs — describe systems plainly (metaphors read as confusing). Visual taste = subtle ambient effects; when something "looks odd" dial it down, don't delete it. Expects per-unit commits and on-device verification (screencap/dumpsys readback) before any feature is reported done.
+§
+Scope pivots mid-build: expects prior work preserved-but-isolated (deferred branch/module), never deleted, and directives obeyed immediately. Wants honest status over optimistic UI — unfinished integrations must be labeled/hid, not left configurable.
+§
+Runs Hermes on a Framework Laptop (Omarchy/Hyprland). Disaster-recovery knowledge base = Obsidian vault at /home/avi/484vault (auto-synced off-device via Syncthing to phone + server; user chose Syncthing because his Nextcloud server lacks full uptime). Prefers automation of durable chores over being asked to repeat them.
+§
+Don't deep-verify the user's Syncthing/sync health unless asked — he knows his own sync topology and cut off a live verification dive as unnecessary.
+§
+Answers the exact ask: a small specific question gets just that answer — no unsolicited adjacent repo work (cut off mid-flight surgery over this: "i was just asking for a short description... what are you doing?"). Large fixes are fine when he requests them; scope creep is not.