a66996ac10
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.
1.3 KiB
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.