Why summarise each community before answer-time instead of at answer-time?

It moves expensive LLM work offline so query latency stays low.

It is required by the LangGraph spec.

Hierarchical community summaries — Semantic Web Academy

Overview

Summarise each community, then summaries-of-summaries.

Why it matters

Hierarchical summaries let one retrieval step pull in concept-level context instead of just a few chunks.

Where this sits in the stack

Hierarchical community summaries is one of the load-bearing decisions in a KG/RAG/agent system: choices made here propagate to retrieval quality, agent reliability, cost per query, and the on-call burden of whoever ships it. Teams that name this trade-off explicitly ship faster than teams that leave it implicit.

Why this is load-bearing

Hierarchical community summaries is the building-code of this layer. You can ignore building codes on a shed, but the moment you put two storeys on top of the same foundation they decide whether the structure stands or falls. In a KG/RAG/agent stack, the equivalent of 'two storeys' is the second feature you ship on top of this primitive — GraphRAG on top of chunking, supervisor agents on top of state machines, regression CI on top of metrics. The cost of cutting the wrong corner now is paid by every later layer, with interest.

Hierarchical summaries let one retrieval step pull in concept-level context instead of just a few chunks.

Reflect — apply it

Anchor hierarchical community summaries to something concrete in your own work.

›Where have you seen hierarchical community summaries done well? Name one team or product and what they got right.
›Where have you seen it done badly? What was the first symptom that surfaced (latency, hallucination, cost, outage)?
›What is the *cheapest* version of this you could ship in your next sprint, and what single metric would tell you it's working?

Reading in progress · 0 of 3 activities done