@Voxyz_ai It’s like a state of constraints. Fred your agent direction of domain. It’s not rocket science. Pattern recognition with more pattern recognition will not solve drift.
@karpathy It does have great long thinking and taking it to a surprisingly further than anticipated. I don’t have context issues, I compress knowledge graphs, so it’s dope
@cjzafir This works - routing cuts spend per task. The other 10X: cut the tokens themselves. Stop re-deriving context every session -- compile it one into a graph the agent reads instead of re-searching. Measured: 11x few tokens than RAG....free ckgs if you want them
@karpathy Nailed the pattern. LLM as a bookkeeper solves who maintains the wiki.
Next layer: compile it into a graph. Typed edges, confidence scores, deterministic retrieval, no re-reading 200 pages per query. Built CKG - 3.8 X F1, 11X fewer tokens vs. RAG.
@trq212 Those harnesses are not good enough. I structure knowledge and don't harness my mustang...maybe folks should start looking at domain vs. a series of bloated SWDLC constraint-based systems.
@elonmusk yeah, but ultimately when I inquire, the hardware or whatever other BS is just regular speeds, and if not, please show me something as I'm building things
@elonmusk my experience with Grok has been very positive. That is definitely a rocket ship...problem is, I get throttled back. I'm not a car guy, but aren't I supposed to take a German car on the autobahn?
@tensor_rotator and why can't we measure intentionality with all these terminal button clicks, quality of input, length of input, time iterating input? Like you care, like you want a better output kinda thing.