brain backup 2026-09-14

2026-09-14 22:38:47 -04:00
parent ca346cc6e7
commit f0ead4f6fa
147 changed files with 73451 additions and 8 deletions
@@ -0,0 +1,46 @@
+---
+project_key: remarkable-hermes
+status: active
+factory_maturity: discovery
+updated: 2026-08-17
+---
+
+# reMarkable Hermes Communication — Project Definition
+
+## Purpose
+
+reMarkable Hermes is the multi-host Paper Pro communication and watcher effort: a tablet-side Hermes surface, safe handwriting/document interaction, and the supporting logger/bridge infrastructure.
+
+## Execution map
+
+| Host / target | Repository / service | Paseo-project role | Status |
+|---|---|---|---|
+| iMac `.124` | Paper Pro SDK / cross-compile work documented under `~/remarkable-dev` | `reMarkable · App` | Exact repository path and daemon recovery still require discovery |
+| AeroPi5 `.126` | watcher/logger/UDP listener history | `reMarkable · Watcher` | Inventory reports watcher not working; ownership and files need discovery |
+| Paper Pro `.132` | sidecar and custom app target | Target environment, not a Paseo host | Explicit device safety controls apply |
+
+## Personas
+
+- App planner and Qt implementer: scoped app/worktree development.
+- Watcher incident triager: read-only service inspection first.
+- Watcher implementer and service verifier: only after root cause and task scope.
+- Device deployment verifier: checks the specific approved artifact on-device.
+- Deployment executor: performs an explicitly approved device-side action with rollback plan.
+
+## Safety boundaries
+
+- Do not restart xochitl, alter device system files, overwrite documents, or deploy a tablet app without explicit approval and rollback path.
+- Treat the Paper Pro as a target environment, never as a generic remote coding host.
+- Preserve handwritten source material and avoid bulk document manipulation.
+
+## Factory readiness next actions
+
+1. Discover the active iMac repository/workspace, build command, and Paseo daemon recovery path.
+2. Discover current Pi watcher ownership, files, logs, and failure mode without modifications.
+3. Register host-local Paseo workspaces only after that evidence is reviewed.
+4. Pilot a read-only watcher triage or local app build—never a tablet deployment.
+
+## Related records
+
+- `../remarkable_hermes_communication_app.md`
+- `../../areas/operations/services_inventory.md`