avi/Orion
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Orion/3. Resources/Research/workflows/Power-Loss Safety Snapshot.md
Avi a66996ac10 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.
2026-10-02 08:34:48 -05:00

1.2 KiB
Raw Permalink Blame History

last-updated hermes-owned tags
2026-09-18T03:35:00-05:00 true
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