Turing machine HHH is not allowed to report on the behavior of the directly executed DDD()

On 6/30/2025 3:05 AM, Mikko wrote:

On 2025-06-29 13:17:19 +0000, olcott said:

>
When it is required that a Turing Machine halt decider is to
report on the behavior of another directly executing Turing
machine this requirement is incorrect.

 No, it is not.

When we know that no directly executing Turing machine
D can possibly be an input to another Turing Machine H
this means that H cannot possibly compute the mapping
from D to the behavior of D.
Not one computer scientist noticed this truism in 90 years.
They always falsely assumed the the machine description of
such a machine is a valid proxy for the behavior of this
machine. I proved that they are wrong.
The input to HHH(DDD) does in fact specify non-halting
behavior and the directly executed DDD() halts.
HHH cannot possibly compute the mapping from the directly
executed DDD() because it cannot possibly be an input to
HHH then this dirctly executed DDD() is outside of the
domain of HHH.
Copyright 2025 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer