I think I get the gist of your point which I would handwavily summarize as “there is no there there,” which I agree with. But I’m thinking that in terms of func

I think I get the gist of your point which I would handwavily summarize as “there is no there there,” which I agree with. But I’m thinking that in terms of functionality, there is no real distinction here. Like If I train a model to do video game physics, and reward it for getting the tank shell missile to land on arbitrary targets, then in some sense the system must have an abstraction of gravity or at least parabolic movement or at least a functional equivalent of that, and it must be able to “hypothesize” about the consequences of its model because that’s what it needs to do in order to hit the target, ie, “everything I’ve seen before leads me to believe tank missiles move like so, therefore if I apply the following forces, it should hit the goal”—the degree to which it wins at this task is exactly the degree to which it can form working models of its environment and reason about the cause and effect of the actions it can take. But of course all those words in the previous sentence are wrong because it’s not exactly doing any of that, just something functionally equivalent and automatic. Maybe we disagree about whether that last point means it can meaningfully “do abstraction” or not.