r/Paperlessngx

Image 1 — Paperless-ngx on your wrist: open-source Pebble watch app to triage your inbox
Image 2 — Paperless-ngx on your wrist: open-source Pebble watch app to triage your inbox
Image 3 — Paperless-ngx on your wrist: open-source Pebble watch app to triage your inbox
Image 4 — Paperless-ngx on your wrist: open-source Pebble watch app to triage your inbox
Image 5 — Paperless-ngx on your wrist: open-source Pebble watch app to triage your inbox
Image 6 — Paperless-ngx on your wrist: open-source Pebble watch app to triage your inbox

Paperless-ngx on your wrist: open-source Pebble watch app to triage your inbox

I built a small companion app for Paperless-ngx on Pebble smartwatches (made for the new Pebble Time 2).

It shows your inbox, displays the document thumbnail (zoomable, readable), lets you set correspondent, document type, tags and date using Paperless' suggestions, and removes the inbox tag when you're done. The app only talks to your own server via the REST API and a token. No cloud, no tracking.

Built with help from Claude (AI) and tested on my own setup. It's free and MIT-licensed, and I'm happy about bug reports and ideas on GitHub.

GitHub: https://github.com/Zeichenfolge/paperless-pebble
Appstore: https://apps.rePebble.com/439d3664960b40d0a1911cb0

u/M_ich_ael — 13 days ago

How would you separate AI-generated derivatives from source documents in Paperless-ngx?

Paperless-ngx is designed around preserving and organizing documents, while an AI workflow may create summaries, translations, extracted tables, classifications, or rewritten text from those documents. Treating a generated derivative as a new version of the source seems risky because versions share the root document's metadata, and replacing the original would weaken provenance. Treating every derivative as an unrelated document makes it difficult to find what source and revision justified it.

A safer model might keep the consumed source immutable, create each generated result as a separate document, and attach fields for source ASN or ID, source checksum, generator, creation time, review status, and the kind of transformation. Tags could separate generated, reviewed, and superseded material, while links connect a derivative back to its source. A generated item would never inherit the source's retention status automatically.

How would you model this with current Paperless-ngx features? Are custom fields and links enough, or is a sidecar manifest outside Paperless a better source of provenance? When would the file-versions feature be appropriate instead of a linked document?

reddit.com
u/RocketSeven — 13 days ago