A halt prover attempts to prove halting and when it
detects that the proof of its input does not form
*a well-founded justification tree within Proof*
*theoretic semantics*
Then it is correct to reject this input as bad data.
*Halting Problem and Proof Theoretic Semantics*
https://www.researchgate.net/ publication/400341134_Halting_Problem_and_Proof_Theoretic_Semantics
This change makes
"true on the basis of meaning expressed in language"
reliably computable for the entire body of knowledge.
A halt prover attempts to prove halting
and when it detects that the proof of its input does not form
*a well-founded justification tree within Proof*
*theoretic semantics*
Then it is correct to reject this input as bad data.
On 04/02/2026 18:47, olcott wrote:
A halt prover attempts to prove halting
To prove that a computation halts is simple. Just show the execution
trace from the start to the halting. The hard problem is to prove
that an execution does not halt.
and when it detects that the proof of its input does not form
*a well-founded justification tree within Proof*
*theoretic semantics*
Then it is correct to reject this input as bad data.
No, that does not follow. That only means that it is correct to reject
the proof. The conclusion of the proof may still be correct.
On 2/5/2026 4:45 AM, Mikko wrote:
On 04/02/2026 18:47, olcott wrote:
A halt prover attempts to prove halting
To prove that a computation halts is simple. Just show the execution
trace from the start to the halting. The hard problem is to prove
that an execution does not halt.
and when it detects that the proof of its input does not form
*a well-founded justification tree within Proof*
*theoretic semantics*
Then it is correct to reject this input as bad data.
No, that does not follow. That only means that it is correct to reject
the proof. The conclusion of the proof may still be correct.
This same system makes
"true on the basis of meaning expressed in language"
reliably computable for the entire body of knowledge.
Proving that it was the right way to do this all along.
On 2/5/2026 4:45 AM, Mikko wrote:
On 04/02/2026 18:47, olcott wrote:
A halt prover attempts to prove halting
To prove that a computation halts is simple. Just show the execution
trace from the start to the halting. The hard problem is to prove
that an execution does not halt.
and when it detects that the proof of its input does not form
*a well-founded justification tree within Proof*
*theoretic semantics*
Then it is correct to reject this input as bad data.
No, that does not follow. That only means that it is correct to reject
the proof. The conclusion of the proof may still be correct.
The way that proofs work in proof theoretic
semantics is that they reject inputs not having
well-founded justification trees as bad data.
Is is the same as a truth predicate rejecting
True("What time is it?") as not truth-apt.
On 2/5/2026 4:45 AM, Mikko wrote:
On 04/02/2026 18:47, olcott wrote:The way that proofs work in proof theoretic
A halt prover attempts to prove halting
To prove that a computation halts is simple. Just show the execution
trace from the start to the halting. The hard problem is to prove
that an execution does not halt.
and when it detects that the proof of its input does not form
*a well-founded justification tree within Proof*
*theoretic semantics*
Then it is correct to reject this input as bad data.
No, that does not follow. That only means that it is correct to reject
the proof. The conclusion of the proof may still be correct.
semantics is that they reject inputs not having
well-founded justification trees as bad data.
On 06/02/2026 17:32, olcott wrote:
On 2/6/2026 3:15 AM, Mikko wrote:
On 05/02/2026 13:28, olcott wrote:
On 2/5/2026 4:45 AM, Mikko wrote:
On 04/02/2026 18:47, olcott wrote:The way that proofs work in proof theoretic
A halt prover attempts to prove halting
To prove that a computation halts is simple. Just show the execution >>>>> trace from the start to the halting. The hard problem is to prove
that an execution does not halt.
and when it detects that the proof of its input does not form
*a well-founded justification tree within Proof*
*theoretic semantics*
Then it is correct to reject this input as bad data.
No, that does not follow. That only means that it is correct to reject >>>>> the proof. The conclusion of the proof may still be correct.
semantics is that they reject inputs not having
well-founded justification trees as bad data.
An example of a valid input is "42". That input has no justification,
well-founded or otherwise. But there is no proof that would reject
"42" as bad data.
It is an element of the set of natural numbers.
True, but non necessarily relevant to tthe proof. But the current
question is whether the proof rejects the input "42" as bad data.
On 2/7/2026 4:15 AM, Mikko wrote:
On 06/02/2026 17:32, olcott wrote:
On 2/6/2026 3:15 AM, Mikko wrote:
On 05/02/2026 13:28, olcott wrote:
On 2/5/2026 4:45 AM, Mikko wrote:
On 04/02/2026 18:47, olcott wrote:The way that proofs work in proof theoretic
A halt prover attempts to prove halting
To prove that a computation halts is simple. Just show the execution >>>>>> trace from the start to the halting. The hard problem is to prove
that an execution does not halt.
and when it detects that the proof of its input does not form
*a well-founded justification tree within Proof*
*theoretic semantics*
Then it is correct to reject this input as bad data.
No, that does not follow. That only means that it is correct to
reject
the proof. The conclusion of the proof may still be correct.
semantics is that they reject inputs not having
well-founded justification trees as bad data.
An example of a valid input is "42". That input has no justification,
well-founded or otherwise. But there is no proof that would reject
"42" as bad data.
It is an element of the set of natural numbers.
True, but non necessarily relevant to tthe proof. But the current
question is whether the proof rejects the input "42" as bad data.
Is the integer 42 a machine description that halts?
Reject.
On 2/7/26 8:08 AM, olcott wrote:
On 2/7/2026 4:15 AM, Mikko wrote:
On 06/02/2026 17:32, olcott wrote:
On 2/6/2026 3:15 AM, Mikko wrote:
On 05/02/2026 13:28, olcott wrote:
On 2/5/2026 4:45 AM, Mikko wrote:
On 04/02/2026 18:47, olcott wrote:The way that proofs work in proof theoretic
A halt prover attempts to prove halting
To prove that a computation halts is simple. Just show the execution >>>>>>> trace from the start to the halting. The hard problem is to prove >>>>>>> that an execution does not halt.
and when it detects that the proof of its input does not form
*a well-founded justification tree within Proof*
*theoretic semantics*
Then it is correct to reject this input as bad data.
No, that does not follow. That only means that it is correct to >>>>>>> reject
the proof. The conclusion of the proof may still be correct.
semantics is that they reject inputs not having
well-founded justification trees as bad data.
An example of a valid input is "42". That input has no justification, >>>>> well-founded or otherwise. But there is no proof that would reject
"42" as bad data.
It is an element of the set of natural numbers.
True, but non necessarily relevant to tthe proof. But the current
question is whether the proof rejects the input "42" as bad data.
Is the integer 42 a machine description that halts?
Reject.
But 42 might well be a machine description that halts, it depend on how
you have defined your encoding of a machine.
On 2/7/2026 8:44 AM, Richard Damon wrote:
On 2/7/26 8:08 AM, olcott wrote:
On 2/7/2026 4:15 AM, Mikko wrote:
On 06/02/2026 17:32, olcott wrote:
On 2/6/2026 3:15 AM, Mikko wrote:
On 05/02/2026 13:28, olcott wrote:
On 2/5/2026 4:45 AM, Mikko wrote:
On 04/02/2026 18:47, olcott wrote:The way that proofs work in proof theoretic
A halt prover attempts to prove halting
To prove that a computation halts is simple. Just show the
execution
trace from the start to the halting. The hard problem is to prove >>>>>>>> that an execution does not halt.
and when it detects that the proof of its input does not form >>>>>>>>>
*a well-founded justification tree within Proof*
*theoretic semantics*
Then it is correct to reject this input as bad data.
No, that does not follow. That only means that it is correct to >>>>>>>> reject
the proof. The conclusion of the proof may still be correct.
semantics is that they reject inputs not having
well-founded justification trees as bad data.
An example of a valid input is "42". That input has no justification, >>>>>> well-founded or otherwise. But there is no proof that would reject >>>>>> "42" as bad data.
It is an element of the set of natural numbers.
True, but non necessarily relevant to tthe proof. But the current
question is whether the proof rejects the input "42" as bad data.
Is the integer 42 a machine description that halts?
Reject.
But 42 might well be a machine description that halts, it depend on
how you have defined your encoding of a machine.
Can't be the shortest one is a single quintuple.
On 2/7/2026 4:15 AM, Mikko wrote:
On 06/02/2026 17:32, olcott wrote:
On 2/6/2026 3:15 AM, Mikko wrote:
On 05/02/2026 13:28, olcott wrote:
On 2/5/2026 4:45 AM, Mikko wrote:
On 04/02/2026 18:47, olcott wrote:The way that proofs work in proof theoretic
A halt prover attempts to prove halting
To prove that a computation halts is simple. Just show the execution >>>>>> trace from the start to the halting. The hard problem is to prove
that an execution does not halt.
and when it detects that the proof of its input does not form
*a well-founded justification tree within Proof*
*theoretic semantics*
Then it is correct to reject this input as bad data.
No, that does not follow. That only means that it is correct to
reject
the proof. The conclusion of the proof may still be correct.
semantics is that they reject inputs not having
well-founded justification trees as bad data.
An example of a valid input is "42". That input has no justification,
well-founded or otherwise. But there is no proof that would reject
"42" as bad data.
It is an element of the set of natural numbers.
True, but non necessarily relevant to tthe proof. But the current
question is whether the proof rejects the input "42" as bad data.
Is the integer 42 a machine description that halts?
Reject.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 59 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 19:27:55 |
| Calls: | 810 |
| Calls today: | 1 |
| Files: | 1,287 |
| D/L today: |
10 files (21,017K bytes) |
| Messages: | 194,198 |