reMarkable Sync Flow¶

Trigger¶

User draws on tablet; cloud or admin requests sync/extract.

Flow¶

sequenceDiagram
  participant TAB as reMarkable
  participant ST as Station
  participant RM as Remarkable_Service
  participant DEV as Device

  TAB->>RM: Upload rm or screenshot
  RM->>RM: Convert to SVG PNG
  ST->>RM: Poll pending sync
  RM-->>ST: Command extract or insert
  ST->>TAB: Apply on device
  ST->>RM: Acknowledge
  RM->>DEV: Update metadata

Steps¶

1. Tablet script uploads capture to /remarkable/ or related endpoint.
2. Remarkable service stores file; runs conversion pipeline.
3. Station announces tablet presence (IP/name) when connected locally.
4. Station polls sync queue for its station_id.
5. Station executes command (mode 0/⅓ sync, extract, insert, restore).
6. Station acknowledges; cloud updates device/file state.
7. User or AI views result in Frontend or via MCP screenshot tool.

Outcome¶

Cloud and tablet stay consistent; artifacts available for AI and profile.

Plan constraints¶

Tablet minutes, sync frequency, storage for .rm archives.

Failure modes¶