Skip to main content
Library is OneLamp’s structured knowledge layer. Where context memory holds discrete facts, the Library turns whole documents — articles, notes, transcripts, pages from your other tools — into an interlinked set of pages your tools can navigate and query.

​
How it’s built

When you ingest a source, OneLamp doesn’t just store the raw text. It compiles it: a durable background pipeline reads the source and writes (or updates) interlinked pages — entities, concepts, sources, and overviews — with [[Library links]] between them. The raw source is kept immutable; the compiled pages are what you read.
1

Ingest

In the OneLamp web app, add a source (paste text or a URL) from the Library or Data Sources page. OneLamp stores the raw source and kicks off a durable compile in the background; the page returns immediately.
2

Compile

The pipeline integrates the source into your existing pages — creating new pages, updating related ones, and adding cross-links. This runs in the background and is typically ready within the hour. On Pro and Enterprise, the optional real-time updates add-on compiles each source the moment it arrives.
3

Read

Search the compiled Library or open any page (with its cross-links) from the Library page in the web app.
Synthesis happens on the write path, at ingest. The read path is pure retrieval of already-compiled pages — consistent with OneLamp’s principle of retrieval, not generation on queries.

​
Querying

From the Library page, semantic search returns the most relevant page bodies (with slugs and cross-links) to read over. Two options go further:
  • Synthesize — return a written answer grounded in those pages, with citations.
  • File back — save that synthesized answer as a new overview page, so an exploration compounds into the Library instead of evaporating.

​
Keeping the graph healthy

Because the Library is a graph, it can be linted. The Library’s lint view reports:

Orphan pages

Pages with no inbound links — disconnected from the rest of the graph.

Dangling links

[[links]] pointing at pages that don’t exist yet.

Thin pages

Pages missing a summary.

Contradictions

Recently flagged conflicts between sources.
Use it to decide what to ingest or clean up next.

​
When to use the Library vs. context memory

Context memory is the MCP/chat surface your tools call (save_context / get_context). The Library — ingesting, searching, and browsing compiled pages — is managed in the OneLamp web app, not through agent tools.