Taelin on X: "(sorry for the silly post just some thoughts)
so after working with Fable 24/7 for several weeks now, I now genuinely believe that, indeed, the only and one last thing between us and AGI is erasure. I can't put in words how strong this belief is forming in me. I really believe so. not architecture, not compute, not datasets. every capability that the AI currently lacks (continual learning, infinite context, long term work, etc.) is root-caused by its inability to erase, and they will all emerge naturally from a well designed erasure centric train, just like so many capabilities emerged from the reasoning paradigm
I really wish I could do something about this but I'm not in a big lab so, meanwhile, I've been thinking in ways to patch that externally. clearly begging the AI to "remove, re-derive" does NOT work, because it has a massive bias to keeping what is there. an example from today: I spent an hour *begging* Fable to simplify Bend2's parser as much as it could, and I was paying attention to one specific function, a completely moronic backtracker that should NEVER be in a well written parser. yet, it was never removed. it was untouched, survived several cleanup turns, no matter how I prompted Fable, how much I asked it to aggressively prune the code. it is simply incapable of refactoring competently because Fable just... adds, patches, and keeps
but then, I realized: it cannot keep something it doesn't see!
so, what if I do this instead?
1. ask Fable to select some code and describe what it is *for*
2. then, a script mechanically removes that code
3. the script asks Fable to fill it again, without seeing the original
4. ...?
5. AI capable of improving long term code quality
basically I think I could perhaps compensate Fable's utter inability to erase stuff by just... deleting that stuff myself. and I then ask it to re-fill. I don't need to beg, I don't need to explain how to redesign from first principles, or meaning of erasure. I can just... literally, programmatically erase it myself. it cannot preserve stupid shit it can't see
sorry this post is as dumb as it seems, but it's not stupid if it works, right? I'm exited to try it, at least." / X<br>Post
Log inSign up
Post
Taelin
@VictorTaelin
(sorry for the silly post just some thoughts)
so after working with Fable 24/7 for several weeks now, I now genuinely believe that, indeed, the only and one last thing between us and AGI is erasure. I can't put in words how strong this belief is forming in me. I really believe so. not architecture, not compute, not datasets. every capability that the AI currently lacks (continual learning, infinite context, long term work, etc.) is root-caused by its inability to erase, and they will all emerge naturally from a well designed erasure centric train, just like so many capabilities emerged from the reasoning paradigm
I really wish I could do something about this but I'm not in a big lab so, meanwhile, I've been thinking in ways to patch that externally. clearly begging the AI to "remove, re-derive" does NOT work, because it has a massive bias to keeping what is there. an example from today: I spent an hour *begging* Fable to simplify Bend2's parser as much as it could, and I was paying attention to one specific function, a completely moronic backtracker that should NEVER be in a well written parser. yet, it was never removed. it was untouched, survived several cleanup turns, no matter how I prompted Fable, how much I asked it to aggressively prune the code. it is simply incapable of refactoring competently because Fable just... adds, patches, and keeps
but then, I realized: it cannot keep something it doesn't see!
so, what if I do this instead?
1. ask Fable to select some code and describe what it is *for*
2. then, a script mechanically removes that code
3. the script asks Fable to fill it again, without seeing the original
4. ...?
5. AI capable of improving long term code quality
basically I think I could perhaps compensate Fable's utter inability to erase stuff by just... deleting that stuff myself. and I then ask it to re-fill. I don't need to beg, I don't need to explain how to redesign from first principles, or meaning of erasure. I can just... literally, programmatically erase it myself. it cannot preserve stupid shit it can't see
sorry this post is as dumb as it seems, but it's not stupid if it works, right? I'm exited to try it, at least.<br>span:not(:empty)~span:not(:empty)]:before:content-['·'] [&>span:not(:empty)~span:not(:empty)]:before:px-1 [&>span:not(:empty)~span:not(:empty)]:before:shrink-0">1:55 PM · Jul 30, 202638.4KViews
112<br>25<br>955<br>397
span:not(:empty)~span:not(:empty)]:before:content-['·'] [&>span:not(:empty)~span:not(:empty)]:before:px-1 [&>span:not(:empty)~span:not(:empty)]:before:shrink-0 min-w-0 overflow-hidden">Taelin
@VictorTaelin
3h
just to clarify (my writing is so fucking poor, I'm in a hurry) - I'd do these steps in a loop. so, for example, instead of...