diff --git a/blog/2023/03/01/computable-solomoff/index.md b/blog/2023/03/01/computable-solomoff/index.md index 2a0d1a5..94fd65c 100644 --- a/blog/2023/03/01/computable-solomoff/index.md +++ b/blog/2023/03/01/computable-solomoff/index.md @@ -54,6 +54,9 @@ This can easily be fixed as follows: - Repeat step 2 until you have one program which has predicted past bits within your compute budget. Eventually this program must exist, since the Turing machine which is producing your trail of bits is by construction computable and non-halting[^3]. 4. Observe the next bit, purge the machines from your set which don't predict it. If none predict it, go to 2. +It is not clear to me whether all Turing machine models require this epicycle. + +