Re: The simple essence of Proof Theoretic Semantics
olcott <[email protected]>
| Newsgroups | sci.logic,comp.theory,comp.ai.philosophy,sci.math |
|---|---|
| Organization | A noiseless patient Spider |
| Message-ID | <[email protected]> |
On 7/3/2026 7:10 PM, dbush wrote: > On 7/3/2026 6:37 PM, olcott wrote: >> On 7/3/2026 1:47 PM, André G. Isaak wrote: >>> On 2026-07-03 12:36, olcott wrote: >>>> On 7/3/2026 1:18 PM, dbush wrote: >>> >>>>> If an algorithm takes an input and produces an output, that is by >>>>> definition a mapping. >>>> That only proves that the definition is incoherent. >>>> The coherent way that it actually works is that >>>> inputs are transformed into outputs by applying >>>> finite string transformation rules to inputs to >>>> derive outputs. >>> >>> Apparently you don't understand the difference between a mapping and >>> an algorithm. They are two different things. >>> >>> André >>> >> >> A function that ignores its input and only returns 0 >> is not any sort of halt function. >> > > It is a partial halt decider that correctly reports the halt status of > any algorithm that halts when executed directly and incorrectly reports > the halt status of algorithms that halt when executed directly. > > If you disagree, point out exactly which part of the below requirements > is violated in doing so. If you dishonestly trim this, it will be taken > as your official, on-the-record admission that the below requirements > are satisfied for the subset of algorithms that halt when executed > directly. > > > Given any algorithm (i.e. a fixed immutable sequence of instructions) X > described as <X> with input Y: > > A solution to the halting problem is an algorithm H that computes the > following mapping: > > (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly > (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed directly > A actual halt function must compute the mapping from its actual input according to the operational semantics of this input to the behavior that this input actually specifies. No function can report on the behavior of its caller because it has no idea who its caller is. -- Copyright 2026 Olcott My 28 year goal has been to make "true on the basis of meaning expressed in language" reliably computable for the entire body of knowledge. The complete structure of this system is now defined. The entire body of knowledge expressed in language is comprised of two types of relations between finite strings: (a) *Axioms* Expressions of language that are stipulated to be true. My system bridges the analytic/synthetic distinction by expressly encoding all empirical "atomic facts" in a formal language such as CycL of the Cyc project. (b) *Inference Rules* Expressions of language that are semantically entailed syntactically from (a) and/or (b).