-
Notifications
You must be signed in to change notification settings - Fork 154
[Feat] Cross-notebook source reuse (library-level sources) #99
Copy link
Copy link
Open
Labels
area:foundationModule boundaries, architecture, tech debtModule boundaries, architecture, tech debtarea:provenanceSource location, citations, document structureSource location, citations, document structureenhancementNew feature or requestNew feature or requestpriority:P1High value, current or next milestoneHigh value, current or next milestone
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
area:foundationModule boundaries, architecture, tech debtModule boundaries, architecture, tech debtarea:provenanceSource location, citations, document structureSource location, citations, document structureenhancementNew feature or requestNew feature or requestpriority:P1High value, current or next milestoneHigh value, current or next milestone
Context
Sources belong to exactly one notebook. Reading the same paper in two contexts means importing it twice, storing it twice and embedding it twice — and the two copies drift as soon as only one is re-indexed.
Open Notebook is moving toward cross-notebook sources; for KnowNote it is the natural consequence of having made the source a first-class persisted entity (#82).
Why this is not v1.4 or v1.5
Each notebook currently owns its vector space — one vector table per notebook, each with its own width, which is the mechanism that keeps different embedding spaces from being compared. Letting notebooks share sources therefore has to answer, before any UI exists:
e5-smalland notebook B uses something else?Those are indexing and storage decisions, not a UI feature. Doing this early would destabilise the provenance work v1.4 is built on.
Proposal (sketch — needs its own design pass)
Acceptance
Depends on
#66–#70 (source provenance), and the storage / embedding-space questions above answered in writing.