The knowledge library
What the library is and the words it uses.
The Library turns documents into a topic wiki: every document gets a verified source wiki (a standalone page written from it and checked against it), and approved source wikis are compiled into topics: pages by subject (a product, a policy, a process) that cite their sources, backed by atomic claims with exact quotes and linked to each other by typed relationships. Every layer is chunked, embedded and searchable by meaning and by words: the original text, every source wiki version, every topic version, the claims, the topics' identities and the relationships. It lives in collections, so what is known about HR, support playbooks or public product documentation never mixes. Nothing you add to the Library ever changes the ontology. Design notes: docs/design.md.
The words
| Term | Meaning |
|---|---|
| Collection | The unit of isolation. Documents, passages, topics, statements, links, vocabulary and jobs all belong to exactly one collection, and nothing is ever combined across collections. |
| Source | One document in a collection: an uploaded file, a captured web page or an interview. It has a status (waiting, working, ready, failed). |
| Source wiki (source page) | A standalone, factual page a model writes from the source, checked against it claim by claim. Every version is kept and indexed. |
| Topic | A page by subject, written from the full verified source wikis of one or many sources. Two documents about the same subject end up on one topic. Pages cite their sources as [source: …] chips. |
| Claim (statement) | One atomic fact of a topic, with its quote copied word for word from a source wiki, the source, the wiki version and the wiki passage it sits in. Claims are the provenance layer; they are superseded, never deleted. |
| Relationship | A typed link between two topics (governs, depends on, part of, replaces...) with why they relate. |
| Vocabulary | The topic types (with their meaning and page template) and relation types (with their inverse) a collection uses. Every collection starts from a rich starter ontology. |