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.

3. Resources/Research/workflows/Keynctr Dev Loop.md

@@ -0,0 +1,17 @@
+---
+last-updated: 2026-09-13T23:00:00-05:00
+hermes-owned: true
+---
+
+# Keynctr Dev Loop (hot-reload UI, rebuild Rust)
+
+**Project:** [[keynctr]] · `frontend/` + Rust crate `keynectr`
+
+1. Build the backend once: `cargo build --release` (Electron spawns `target/release/keynectr serve`).
+2. Terminal A: `npx vite --port 5173` (in `frontend/`).
+3. Terminal B: `NOSTR_GUI_DEV_URL=http://localhost:5173 KEYNCTR_ENABLE_GPU=1 npx electron .`
+   - `KEYNCTR_ENABLE_GPU=1` is required on this machine ([[electron-apps-crash-software-gl-arch-hyprland]]).
+- **UI edits** hot-reload via vite — no restart.
+- **Rust edits** need `cargo build --release` + backend restart.
+
+Related: [[Workflows Index]]

3. Resources/Research/workflows/Polaris Vault Workflow.md

@@ -0,0 +1,39 @@
+---
+last-updated: 2026-09-25T23:30:00-05:00
+hermes-owned: true
+---
+
+# Polaris Vault Workflow
+
+> Standing directive (2026-09-25): new projects should operate like the **Polaris / orion boilerplate** — a plain-markdown, agent-maintained knowledge vault. Avi asked for "the full process of how I should guide you in following this boilerplate for new projects." Live instance: `/home/avi/Projects/Polaris/` (boilerplate from github.com/kyleisuncool/orion-boilerplate).
+
+## Structure
+- `0. Inbox/` — everything lands here first; goal is to get it OUT (daily notes live here).
+- `1. Projects/` — active work; every project needs a "done when" sentence.
+- `2. Areas/` — long-lived responsibilities; a finished project hands its knowledge back to an Area.
+- `3. Resources/` — things collected while working (PDFs, references); projects reference them.
+- `4. Decisions/` — decisions noted during work, cross-linked, hanging threads resolved here.
+- `5. Archive/` — only moved when told; reversible (`resume X` restores context).
+- `6. Templates/` — reusable document shapes (daily note, decision, contracts, hubs) to minimize token use.
+- `wiki/` — `hot.md` = current 360° state; `index.md`, `log.md` (log folds every ~22 entries into compacted lines).
+- `AGENTS.md` = the rulebook; skills in `.agents/skills/`: ingest, cascade, archive, close, daily, fold, skeleton, lint.
+
+## Commands (say to the agent)
+| Say | Effect |
+|---|---|
+| `new area: X` / `new project: X` | Creates hub against its contract |
+| `ingest` | Files everything in Inbox: people, decisions, updates, references |
+| `cascade` | Rewrites `wiki/hot.md` with everything learned this session, logs it |
+| `daily note` | Closes today's note, writes tomorrow's |
+| `weekly sweep` | One-line list of everything tracked |
+| `close workstream: X` | Finished project hands deliverable back to its Area |
+| `archive: X` / `resume X` | Retire/restore an Area |
+| `lint` | Health check: dead links, missing fields, overdue follow-ups |
+
+## Key conventions from the boilerplate walkthrough
+- Inbox → process → Projects (active) → Areas (retained knowledge) → Archive (done, retained, no usage penalty).
+- Deliverable flow: build artifact in the code repo, HTML → PDF via browser, put in Outbox, note who it went to + channel + where.
+- Inbox and Outbox exist per-machine (desktop + Nextcloud); bring-in docs go to project folder + Resources, with extracted summary + text-by-text copies in-vault.
+- Purpose: minimize token usage per session — keep reproducible templates, compacted logs, deep recall only on request.
+
+Related: [[User Preferences]] · [[Keynctr Dev Loop]] · [[Decisions Log (legacy)]] (D-2026-120)

3. Resources/Research/workflows/Power-Loss Safety Snapshot.md

@@ -0,0 +1,17 @@
+---
+last-updated: 2026-09-18T03:35:00-05:00
+hermes-owned: true
+tags: [shonar, power-loss, checkpoint, workflow]
+---
+
+# Power-Loss Safety Snapshot (Shonar engine + repo)
+
+Standing checklist before a predicted power cut (added 2026-09-18, `shonar-desktop-dev` skill):
+
+1. `git add -A && git commit` — commit even a WIP that may not compile (label it "WIP snapshot"). An uncommitted mid-edit is the only thing a hard cut truly loses.
+2. `PRAGMA wal_checkpoint(TRUNCATE)` + `PRAGMA integrity_check` on `engine.db` so nothing survives only in the WAL.
+3. Sweep stuck recordings: rows with `processing_status` not in (completed, failed, none) AND no queued/running job rows, whose transcribe+summarize jobs all succeeded, need `UPDATE recordings SET processing_status='completed', processing_error=NULL WHERE id=?` — `sweep_stale` requeues orphaned jobs at startup but never repairs the recording row, so the UI shows "processing" forever otherwise.
+
+**Concurrent-session note:** another Hermes session may be editing the same working tree live. Recompile before "fixing" a break you saw minutes ago — the sibling may have fixed it; snapshot-commit whatever compiles and tests green.
+
+Related: [[Shonar]] · [[Keynctr Dev Loop]]

3. Resources/Research/workflows/Workflows Index.md

@@ -0,0 +1,6 @@
+# Workflows Index
+
+## Workflows
+- [[Keynctr Dev Loop]]
+- [[Power-Loss Safety Snapshot]]
+- [[Polaris Vault Workflow]] — new-project vault boilerplate (directive 2026-09-25)