Even with GraphRAG, the agent gets lost without a memory contract
Pessoal, o agent puxou um trecho bonito. Similaridade alta. Confiança alta. Estava no stub errado. Não foi “RAG fraco”. Foi porta errada. Índice caro, lixo na entrada. O post anterior foi sobre consultar o grafo de código : token cai quando o agent pergunta ao mapa, não quando o gitignore está certo. Aqui é a outra conta. Vector, GraphRAG, híbrido: como recuperar . Contrato: o que pode ser…
An article discusses the use of vector and GraphRAG indexes in agent retrieval. The author questions which index to use, suggesting that the choice between vector, graph, or a hybrid approach depends on the type of inquiry. The debate in the market is between lookup and synthesis, with vector typically winning in lookup and GraphRAG in synthesis, but being costly to maintain.
The author emphasizes the importance of having a contract, or a set of rules, for how the agent retrieves information, including a canonical source, scopes, and rules for what is prohibited as input. The author provides a list of 9 questions to consider when setting up a memory contract for an agent.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.
