What is in the knowledge graph?
Wiki pages — overviews, detailed content, and the links between them — held in Weaviate for semantic search and Neo4j for graph traversal. Two subsystems feed and read it:- The learning pipeline turns a source into pages (ingestors), then merges them into the existing graph (a hierarchical, sub-graph-aware merge).
- Knowledge search retrieves at campaign time: semantic search, graph traversal, and reranking.
Hosted knowledge: Leeroopedia
The graph is yours to build; Leeroopedia is the hosted layer beside it: a curated knowledge base of ML and AI frameworks that sessions query over MCP with one key in.env and no infrastructure. Ideation asks it how a framework behaves and has its plan reviewed; implementation asks for build plans, documented hyperparameter ranges and failure diagnoses. What each node consulted, and the credits spent, appear in kapso watch --tree and the final summary. See Connect Leeroopedia and MCP gates.
How do I get knowledge into a campaign?
Option 1: Pre-indexed KG
Option 2: Ingest sources
Option 3: Research as context
Search backends
What infrastructure does it need?
Both backends require database infrastructure:Related
Learning Pipeline
Search Backends
Research
Configuration
pip install leeroo-kapso · Every page as plain text: llms.txt.