The "transaction" which contains the input data for a script, can be set by any external entity. How do you propose to require that the bits & bytes of that input data declares its dependencies when it is impossible to force the external entity to declare where the data came from? You seem to not understand some basic facts about modularity and type systems in programming. Even if you could force the external entity to declare the full lineage of the input data (i.e. 100% dependently typed), that would require that the scripting can't be programmable, i.e. the external I/O capability would be eliminated...
Note I hedged that above statement (your quote of me above) as follows...
Even if someone argued against my upthread point that strict partitions can't exist for scriptable block chains wherein I claimed this is due to uncontrolled external chaos due to external I/O, there is another unarguable reason that strict partitions can't exist for a scriptable block chain. That is because the gas (currency) transfers must be atomic with the script block confirmation (i.e. if they are orphaned and chain reorganized then they must be done together) so they must be in the same partition. But if the currency for a partition is a static set of UXTO or account balances (i.e. no cross-partition spending), then the system can not function properly.
Yet we also explained above (and even monsterer agrees on this point fwiw) that cross-partition spending breaks the Nash equilibrium.
Thus I continue to maintain my point that Ethereum can not scale with decentralized validation.