Is there a logical concept or some sort of &#x27;phrase&#x27; that describes the &#x27;inside and outside of box&#x27; problem? My vocabulary is lacking.<p>In computing, we know quite well that a system&#x27;s inputs and outputs don&#x27;t have to be coupled as well as they seem.<p>I can produce a program &#x27;&#x2F;bin&#x2F;sha256sum&#x27; which drops the sha256sum of a file onto stdout, unless said file is a JPEG image depicting a Shiba Inu, in which case it puts &#x27;such file&#x27;.<p>In computing this is really kind of an obvious result. If we have a debugger or a disassembler we might be able to find that behaviour without actually encountering it. But if it&#x27;s a HTTP API, we really have no way of knowing what&#x27;s going to happen.<p>We can gather lots of empirical evidence, but we have no reason to believe that 5M results or 25M results or 50M results increase our certainty that it &#x27;always does X&#x27;. (Simply, it&#x27;s not provable).<p>It seems to me to be tautological to say that &#x27;reality may not be what it seems&#x27;, in that sense, because we know that we cannot be certain that it even acts the same way at t=t and t=t+1.<p>Even if we found some sort of &#x27;higher state&#x27; - if we found the source code to the program that actually runs all there is - what&#x27;s above that? Turtles all the way down!