Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

epic: make the vector store a reconciled projection, then widen what enters it

Aperta
  • Qualcosa non va?
#228 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@samarthsinh2660 ci sta già lavorando.

Dal 12/10/2026.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
dart
Ambito
databases

Direzione di ricerca

This is an umbrella issue and explicitly tracks no code of its own. Read docs/SHIVA/rag.md under “PDF documents” and the design at docs/superpowers/specs/2026-09-19-pdf-rag-design.md, then choose an open sub-issue (#231–#236) to work on. Done for this issue means its planned work is handled through those sub-issues; there is no standalone implementation or test target here.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement P1-High

PDF content support landed in #226: a PDF attached to a note is now extracted, chunked, embedded and citable down to the page. Building it surfaced a set of gaps that are deliberately out of that issue's scope — some are pre-existing problems in the note side of the vector pipeline that only became visible once documents started retrieving reliably, others are capabilities the v1 design consciously deferred.

This issue is the umbrella for that follow-up work. It tracks no code of its own.

The idea

Retrieval is only as good as what made it into the vector store, and today the store is written once and never reconciled. A note embedded before the embedder existed stays unsearchable forever; a vector written by one tostore version can read back empty after a package bump; a chunk whose document was deleted leaves its vector behind with no way to reclaim it. None of these announce themselves — retrieval just quietly returns less.

The through-line for the next phases: make the vector store a reconciled, self-healing projection of what the user actually has, then widen what can enter it.

Ordered by what unblocks the most:

Phase A — make existing content searchable (correctness, the highest value work here)
Notes that never got a vector, and stores that silently read empty after an upgrade. Until this is fixed, every retrieval quality measurement is against an unknown fraction of the library.

Phase B — keep it healthy over time
Orphaned vectors, and the dimension the app declares versus the one the model emits.

Phase C — widen what documents contribute
A document's content reaches retrieval but not the knowledge graph, and a Manas-scoped chat cannot reach documents at all.

Phase D — reach and polish
Formats beyond PDF, and jumping to a cited page in-app.

Sub-issues

Phase A

  • #231 — Backfill: re-embed notes that have no vector
  • #232 — Version-stamp the vector store path so a package upgrade cannot read empty

Phase B

  • #233 — Rebuild path for orphaned chunk vectors
  • #234 — Reconcile the declared embedding dimension with what the model emits

Phase C

  • #235 — Documents contribute to the knowledge graph
  • #236 — A Manas-scoped chat should reach its notes' attached documents

Phase D

  • #237 — Jump to the cited page in-app
  • #238 — Support formats beyond PDF

Phase E — beyond text documents

  • #240 — Images: search the text inside attached images (on-device OCR)
  • #242 — Selective OCR for PDF and Word: scanned pages and pasted pictures only (measure on a device first)

Deliberately not planned

OCR for scanned documents. A PDF with no text layer stays attached, openable and marked not searchable. This is a product decision, not a backlog item — a scan's extracted text is unreliable enough that citing a page from it would be worse than not citing at all.

Reconsidered: OCR is now used for text inside images (#240), and is planned for scanned PDF pages and pictures pasted into Word files (#242) — page by page, never for a whole document, because a PDF's own text is exact and OCR's is not. #242 must be measured on a device before it is built.

Reference

  • Parent feature: #226
  • Design: docs/superpowers/specs/2026-09-19-pdf-rag-design.md
  • Current behaviour, with diagrams: docs/SHIVA/rag.md, section "PDF documents"
Lingua principale
Dart
Stelle
2
Fork
2
Merge medio
1g 7h
PR unite (30g)
35

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di basictech01/uniun

Tutte le issue di basictech01/uniun

Issue simili

Altre issue su Dart

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.