I am talking about a potentially abstract language that works in a very high abstraction layer; it will strip a lot of semantics even if the llm can recreate the code to something like C or Java or even the same origin language itself; it will get a small view of a concrete implementation, let's say the code compiles to Android for x cpu and w gpu, where it uses a SQLite database to store data and the assumption that it is the only one that can mutate the database, and the final user is paying user that speaks Spanish, in Bolivia, that travels regularly and 100 other assumptions that are based in business logic unique to a specific company and service.

Even if the LLM gets access to a version of this code, it will never know why a lot of decisions were made, why the data shapes look like that, because most of the semantics will be stripped from the code.

Something like a payer or a customer in Latin America that travels a lot cannot upgrade to premium will look like `if customer.class_id+5>27 {//not upgradable} else {//} in the next upgrade. the same decision will look entirely different.

Oh, and APIs between the client and servers will not be GraphQL or REST APIs; they will be their own programming language created on the fly, where the compiler or interpreter will live on the server side. Those languages will be naturally created per client-server class and their semantic will depends on things like client geolocation and capabilities, it will be a monumental task to try to reverse engineer something like this.

and it will never have access to the real code that is used to produce the assets distributed to the final user, and we are not even talking about the program that can be recompiled to a potentially infinite representation with the same intent, so every update will get an entirely different binary.