To everyone out there listening. This is a first of many to come by @Elationate with a little bit of my help.
Exact Running Times of the Busy Beaver Records for BB(6), BB(7) and BB(3,4): a Lean 4 Formalization with Their Last 200 Digits
More math and large numbers to come.
Breakthroughs in compression, LITM, hallucination suppression (what we call at @HypernymAI "coherent refusal"), and breakthroughs in recall, when combined, solve this. This curve inverts. The fix already exists, it’s just not evenly distributed - yet.
Persistent memory has been one of AI’s longest-standing challenges, but practical breakthroughs in context compression and inference are making reliable recall achievable.
Persistent memory recall at incredibly fast speeds has already been achieved at Hypernym. I think 4-8 weeks before an actual system that largely solves long-running memory is production ready.
Total recall remains the ultimate endgame @HypernymAI
@Altimor Pulled the trigger today and switched 100% of Lindy traffic to @HypernymAI , churning from vanilla models. Saves us millions of $ and we're actually seeing an *increase* in context performance on many core use cases. Transformative for the business.
The common belief today is that once models exceed 256k tokens, context performance falls off a cliff.
At Hypernym, we’ve internally proven this widely accepted “fact” is false.
It’s not a technical limitation — it’s simply the result of an industry moving too fast.
No matter which model we apply our infrastructure to, LITM drastically improves — among many other things.
More to come. 🚀
@josephweinberg@elonmusk Wait until they see Modulum, the next evolution of inference and long context persistent memory enhancements. It would put @spacex on steroids.