Skip to content

[Epic] v1.5 — Trust & Sources #154

Description

@mrsibe

[Epic] v1.5 — Trust & Sources

Theme

One sentence: make every answer auditable at the level of the sentence, and make the sources controllable.

v1.4 (#82) closed the Trusted Research Loop end to end — block-aware chunking, structured citations, a real PDF reader, click-to-source, and an eval harness with a frozen baseline. What it did not change is the grain of the trust: a citation still points at a whole retrieval chunk, and an answer can still sound sourced while one of its sentences is not.

v1.5 is deliberately narrow. It does not add generator features (audio overview, mind map, flashcards, quiz, slides). Those are the features users love; they are not the features users work around. The things users write plugins and forks for — citation precision, source control, folder management, export — are where a small product can beat a large one, and where KnowNote's existing provenance architecture is already an advantage rather than a gap.

The bar

Citation is a link to a location          ← shipped in v1.4
        ↓
Citation is the exact supporting passage  ← this epic
        ↓
A claim without support says so           ← this epic

Children

# Issue Priority
#160 Architecture prep: freeze the retrieval / ingestion / citation seams P0 (step 0)
#155 Exact-passage citation: cite source spans, not chunks P0
#156 Citation coverage: uncited / invalid / inferred P0
#94 Source scope, persisted per session P0/P1
#157 Retrieval explainability (per-answer snapshot) P1
#95 Ingestion runs: persistent pipeline state, non-destructive re-index P1
#78 Chunking experiments (freeze the chunk baseline) P1
#96 Global search + the shared FTS index P1
#77 Retrieval experiments on the frozen chunk baseline P1
#98 Batch / folder import P1
#158 Folder as a live source (watch / re-index / stale) P1
#80 Knowledge MCP server — stretch, orthogonal P2

The three workstreams

Trust        #160 → #155 → #156
                        ↑
                       #94 → #157

Source       #95 → #98 → #158

Retrieval    #95 → #78 → #96.buildFTS → #77 → #96.searchUI

The point of #160 is that these three streams share retrieval, ingestion and citation seams. Without it, each stream would grow its own version and KnowledgeService would absorb every one of them.

Build order

Not by issue number — freeze the seam, then stack capability on it.

Order Work Why here
0 #160 Architecture prep Contracts first; no feature work
1 #155 Exact-passage citation v1.5 core capability
2 #156 Citation coverage Needs the spans from #155
3 #94 Source scope First real validation of the RetrievalRequest.filter seam
4 #157 Retrieval explainability Scope + retrieval trace now exist
5 #95 Ingestion runs Foundation for everything source-lifecycle
6 #78 Chunking experiments Fix chunking before tuning retrieval
7 #96 FTS backend One index shared by search and BM25
8 #77 BM25 / hybrid / RRF / reranker Measured on the frozen chunk baseline
9 #96 Search UI Backend already exists
10 #98 Batch / folder import On the unified ingestion pipeline
11 #158 Watched folder Filesystem events only enqueue
12 #80 MCP Adapter over the now-stable query layer

The one ordering rule worth stating separately: #78 before #77. Chunking is the input distribution retrieval is measured on; tuning retrieval and then changing chunking voids the experiment.

Already shipped in v1.4, not re-opened here

Deliberately deferred

Stretch / orthogonal

  • [Feat] Implement the Knowledge MCP server #80 Knowledge MCP server is in the v1.5 milestone because it was moved up at the maintainer's request, but it is not part of this theme and is not on the release critical path. It is labelled stretch and runs last, after KnowledgeQueryApi can be separated from Electron.

Exit criteria

  • Citation quote and highlight are span-accurate on the [Feat] RAG eval harness: dataset format, runner, metrics #75 eval set, with no precision regression against the frozen v1.4 baseline.
  • Citation coverage and unsupported-sentence rate are measured and visible.
  • A user can scope a question to selected sources and see which were used.
  • A failed reindex never destroys the previous usable index.
  • Nothing in the epic requires a network call beyond the configured model endpoint.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:provenanceSource location, citations, document structurearea:retrievalRetrieval quality and evaluationarea:uxInterface, workflow, information architectureepicTracking issue for a multi-PR epic

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions