24.04.26
Memory and Retrieval Boundary
We clarified the boundary between conversation memory, retrieved evidence, and answer synthesis in the Agentic RAG runtime.
Alper YilmazFounder & CEO
Osman HomekCTO
Updates: Retrieval
Product releases, platform milestones, and important changes across the Cortagent stack.
10.03.26
Datasource Routing Work
Datasource routing work was added so retrieval can target relevant sources instead of searching every corpus the same way.
Alper YilmazFounder & CEO
Osman HomekCTO
06.03.26
Keyword Retrieval Path
Keyword retrieval work gave the RAG layer a lexical path for exact terms, identifiers, and phrases.
Alper YilmazFounder & CEO
Osman HomekCTO
03.03.26
Retrieval Stitching Work
Retrieval stitching work was added to join evidence from multiple retrieval paths without losing source boundaries.
Alper YilmazFounder & CEO
Osman HomekCTO
17.02.26
Reranker Selector Work
Reranker selection work was added to keep evidence ordering separate from initial retrieval.
Alper YilmazFounder & CEO
Osman HomekCTO
10.02.26
Language Routing Work
Language routing work was added so multilingual queries can be handled without treating language as a knowledge silo.
Alper YilmazFounder & CEO
Osman HomekCTO
06.02.26
Graph Retrieval Path Added to the Retrieval Surface
Graph retrieval modules were added so relationship-oriented evidence can become a selectable retrieval path.
Alper YilmazFounder & CEO
Osman HomekCTO
06.01.26
Vector Integrity Contract
Vector integrity checks were added to catch invalid retrieval state before it leaks into answer synthesis.
Alper YilmazFounder & CEO
Osman HomekCTO
30.12.25
Lineage and Retrieval Event Logging
RAG event journals and lineage artifacts were added so retrieval behavior can be inspected after a run.
Alper YilmazFounder & CEO
Osman HomekCTO
19.12.25
Pronoun Resolution Pass
A pronoun resolution path was added to reduce failures on follow-ups like 'what about that' and 'what was her role'.
Alper YilmazFounder & CEO
Osman HomekCTO
16.12.25
Conversation Context Becomes a Retrieval Input
Conversation context handling was added so follow-up questions can reuse prior state instead of being treated as isolated prompts.
Alper YilmazFounder & CEO
Osman HomekCTO
28.11.25
Complexity Gates for Decomposition
We added query complexity logic so decomposition can be based on explicit signals instead of defaulting every request into a heavy path.
Alper YilmazFounder & CEO
Osman HomekCTO
26.11.25
Retrieval Routing Baseline
A retrieval router baseline was introduced to make vector, keyword, graph, and swarm-style paths selectable instead of implicit.
Alper YilmazFounder & CEO
Osman HomekCTO
24.11.25
Query Structure Parsing Enters the RAG Path
Early work moved query handling toward explicit structure parsing so retrieval could respond to intent and complexity.
Alper YilmazFounder & CEO
Osman HomekCTO