We published our research in December and told Chroma's CEO Jeff. 4 months later, Chroma republished it without citing it. We think this sets a pretty bad precedent:
Is there a reason to prune individually instead of introducing a tombstoning approach like kimi?
Most of my harnesses around agentic retrieval wind up implementing the poor man’s version of this via isolated context windows and recursion. But it seems like an entire trajectory is more likely to be erroneous than its docs, and you could just rewrite true positives in poor trajectories as the summary?
When the context gets edited and compressed enough,
it sometimes stops behaving like something that needs to be managed,
and starts reconstructing what it needs automatically.
At that point, the system feels less like search + filtering,
and more like a single process that’s continuously re-forming its own context.
https://x.com/maxrumpf/status/2037365748973384154
Most of my harnesses around agentic retrieval wind up implementing the poor man’s version of this via isolated context windows and recursion. But it seems like an entire trajectory is more likely to be erroneous than its docs, and you could just rewrite true positives in poor trajectories as the summary?
When the context gets edited and compressed enough, it sometimes stops behaving like something that needs to be managed, and starts reconstructing what it needs automatically.
At that point, the system feels less like search + filtering, and more like a single process that’s continuously re-forming its own context.