Your Library Puts Your Material First
Arivu now leads Library with pages, notes, annotations, and objects you saved or wrote, while keeping generated concepts and entities in a separate view.
Your Library should answer a direct question first: what did I save or write?
Arivu used to place generated concepts and entities in the same default list as bookmarks, Notes, annotations, daily notes, and research objects. Those derivatives can be useful, but they are not the same kind of material. Mixing them together made a busy Library feel larger without making your own work easier to find.
Library now opens with saved and authored content. Generated concepts and entities remain available through a clearly labeled secondary view and continue to appear where their relationships are useful in Graph.
Two Views, Two Jobs
The main content view contains the durable material you chose to keep or create:
- captured pages;
- standalone and daily Notes;
- annotations and selected passages;
- typed knowledge objects such as decisions, meetings, people, books, projects, and research threads.
The derived view contains generated concepts and entities that passed Arivu’s current evidence and quality rules. Keeping them separate makes their status clearer. A concept can help you discover a pattern without pretending it is a Note you wrote. An entity can connect several sources without competing with those sources in the primary list.
What this means for you: opening Library starts with recognizable material and less generated noise, while deeper projections remain one deliberate switch away.
Graph Still Connects Both Layers
This is a presentation boundary, not the removal of derived knowledge. Graph can still show eligible concepts, entities, source relationships, and optional semantic similarity alongside explicit links. Provenance and confidence continue to explain how a relationship was created.
Generated material also keeps its higher evidence bar. Unsupported or stale derivatives stay out of current knowledge surfaces, while incomplete captures can remain safely available in Library for repair. Your own Notes, annotations, objects, and explicit links remain the durable layer.
The API adds explicit scope=content and scope=derived projections, while an omitted scope retains the previous combined response for existing API clients.
The result is a quieter starting point: your material first, generated structure when you ask for it, and Graph available when the relationship between the two is the question.
See Capture and Library for the current views and filters.