Skip to main content
The knowledge graph is Kapso’s imported memory: what other people have written, drawn from repositories and research and searchable during a campaign. It is the counterpart to the lesson bank, which holds what Kapso measured itself.

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.

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:

Learning Pipeline

How knowledge is extracted and merged

Search Backends

Hybrid search implementation

Research

Web research for knowledge acquisition

Configuration

YAML config for knowledge search
Related pages: Learning Pipeline · Search Backends · Research · Configuration Kapso is an open-source framework by Leeroo that builds software toward measurable goals through experiment campaigns. Source code: github.com/Leeroo-AI/kapso · Install: pip install leeroo-kapso · Every page as plain text: llms.txt.