8000 docs(devlog): queue anytopdf integration, not started by adeelahmad · Pull Request #120 · adeelahmad/lense · GitHub
[go: up one dir, main page]
Skip to content

docs(devlog): queue anytopdf integration, not started #120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adeelahmad merged 2 commits into from
Oct 4, 2026
Merged

docs(devlog): queue anytopdf integration, not started #120

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d8eeda2
docs(devlog): queue anytopdf integration, not started
claude Oct 4, 2026
dd23782
Merge origin/main into claude/project-thread-17nx5n
claude Oct 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8000
23 changes: 23 additions & 0 deletions DEVLOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,29 @@

Plans and progress for work in flight. Newest first.

## 2026-10-04 · anytopdf as the conversion engine (not started: wait for Adeel's go)

Goal (Adeel): use the sister project [anytopdf-rs](https://github.com/adeelahmad/anytopdf-rs) (README on its sprint2
branch) to turn any source into one searchable, cited PDF: OCR, captions, transcripts, keyframes and metadata as an
invisible text layer, with an embedded manifest, chunks, source anchors and provenance. Do not start until Adeel says go.

Why it fits: one static Rust binary (Linux x86_64 and arm64 musl, so a Raspberry Pi) that Lens can download as a
component, instead of LibreOffice and Chromium in the full image; provenance per fact matches "trusted, cited memory".

Todo (when started):

- [ ] Wait for anytopdf's JSON output (`--json`, schemas, exit codes) and `extract --json` manifest to land
- [ ] anytopdf as a component Lens installs itself (settings: auto, on, off), with its version recorded
- [ ] A pipeline / workflow node "Make evidence PDF": inputs a recording or resource, outputs the PDF as a rendition
and its manifest chunks and anchors as Lens chunks (citations jump to time span, box or byte range)
- [ ] Use it where Lens has no converter first (images, captions, mixed folders); keep LibreOffice and Chromium as
the default for Office, HTML and email until anytopdf reads them (its roadmap: PDF, HTML, EML, Office)
- [ ] Reuse Lens's own OCR and transcripts as sidecars rather than running them twice
- [ ] Run it with no network, size and time caps, plugins off unless an admin allows them (its plugins run with full
user rights until its sandbox lands)

Refine later: anytopdf's intake channels (IMAP, webhooks, watched folders) and printing overlap Lens's sources and
sensors; decide which side owns them. MCP server mode could be an extension.
## 2026-10-04 · Notes: a page for everything

Goal (Adeel): every resource, entity and topic has its own page (its note), next to free notes written by people or
Expand Down
Loading
0