# My reMarkable Obsidian Workflow > [!question] Lingering Questions > - The creator notes OCR output added inferred properties and context ("neuron," "perceptrons") that were never actually handwritten — partly because the same model powered both a transcript pass and the OCR pass. Where's the line between helpful inference and silent fabrication in an OCR pipeline, and does the vault need a convention to flag AI-inferred text separately from transcribed text? > - Is a plugin-only (no-automation) sync path sufficient for most use, or does the OCR automation genuinely earn its added complexity? The creator explicitly says the automation half "isn't for everyone." > [!tip] Article Ideas > - "Guaranteed capture makes tool choice a presence decision" — once every input method reliably reaches the vault, choosing analog vs. digital in the moment stops being a sync question and becomes a social/attention question. > [!link] Cross Reference > - [[3. Resources/MOCs/Personal Knowledge Management MOC]] — analog-digital capture bridging as a PKM tooling pattern > - [[3. Resources/Permanent Notes/A Knowledge Tool's Environment Is a Lever on Thinking]] — related claim about how tool environment shapes the thinking it produces > [!quote] Vocabulary > - **reMarkable Sync** — the community Obsidian plugin (by Tim Domin) that pulls reMarkable tablet documents into a vault sub-folder as PDFs on a schedule or on demand ## Bibliographic capsule A YouTube creator demonstrates a two-stage workflow for getting handwritten reMarkable tablet notes into Obsidian: first as a synced PDF via the community "reMarkable Sync" plugin, then optionally as searchable OCR text via an AI automation layer (OpenClaw or a Claude Desktop skill). ## Author's thesis Once every note-taking input — typed, reMarkable, or pure analog — reliably lands in one Obsidian vault, the choice of capture method stops being a technical sync problem and becomes a situational one: pick whichever tool fits the moment, including for reasons like staying present in a conversation rather than looking at a screen. ## Key arguments (≤3) 1. **A community plugin closes reMarkable's long-standing sync gap.** Installing and registering "reMarkable Sync" (Tim Domin) is the only reMarkable-specific step; everything downstream (folder destination, sync cadence, manual trigger) is generic Obsidian plugin behavior. 2. **OCR converts a static image into a durable, searchable vault asset.** The creator keeps both the PDF (for feel, color, and provenance — especially notes someone else wrote) and an OCR'd text version, explicitly framing text as the more durable long-term store. 3. **Reliable capture changes the psychology of tool choice, not just the mechanics.** Because every input method converges on the same vault, the creator picks e-ink specifically at talks and conferences to avoid a screen "between me and the speaker" — a presence argument, not a portability one. ## Claim atoms ### OCR makes handwritten notes durable and searchable > [!quote] ID:rw_h1 > I find that it's a much more durable way to store things rather than just the PDF. Where/why: mid-video, explaining why OCR follows the PDF sync. Reframes OCR from a nice-to-have into the durability layer that turns a static image into a first-class vault note. ### Guaranteed capture frees the note-taking method > [!quote] ID:rw_h2 > I just get to decide on the note taking method that I feel like at the time. Where/why: closing reflection, after showing that everything lands in Obsidian regardless of input method. The pipeline's real payoff is psychological, not technical — input choice becomes context-driven rather than sync-anxious. ### E-ink keeps you present in face-to-face settings > [!quote] ID:rw_h3 > I just feel like I can be more present if I don't have a screen between me and the speaker. Where/why: use-case justification for choosing reMarkable at talks and conferences. Argues for analog/e-ink on presence grounds, not just portability. ## Permanent candidates - **[P1] Universal capture sink makes tool choice a presence decision** — supported by H2; checked existing Permanents, found none capturing this specific psychological-payoff mechanism; promoted below. ## Processing checklist - [x] Confirmed this doc's `notes` field already contained a full deep-read (Refactor Appendix present) — ported directly - [x] Checked for an existing Permanent note before promoting P1 — found none, created - [x] Connect into the relevant MOC — [[3. Resources/MOCs/Personal Knowledge Management MOC]] ## Links - [[3. Resources/MOCs/Personal Knowledge Management MOC]] — analog-digital capture bridging and vault-input tooling - [[3. Resources/Readwise/Articles/My reMarkable Obsidian Workflow With the Obsidian reMarkable Sync Plugin]] — source document