Re: Minimal Logics in the 2020's: A Meteoric Rise

On 7/6/24 10:51 PM, olcott wrote:

On 7/6/2024 9:16 PM, Richard Damon wrote:

On 7/6/24 9:56 PM, olcott wrote:

On 7/6/2024 8:32 PM, Richard Damon wrote:

On 7/6/24 9:06 PM, olcott wrote:

On 7/6/2024 6:28 PM, Richard Damon wrote:

On 7/6/24 6:41 PM, olcott wrote:

On 7/6/2024 5:22 PM, Richard Damon wrote:

On 7/6/24 6:08 PM, olcott wrote:

On 7/6/2024 4:02 PM, Richard Damon wrote:

The problem here is you logic doesn't actually allow for the necessaery references in it.
>

Not at all. My logic is simply smart enough to reject
non-truth-bearers AKA expressions that are not valid
propositions. It does not stupidly falsely assume that
every expression is a valid proposition.\

>
Logic isn't "Smart", it follows its rules.
>
Your rules are just inconsistent.
>

>
When-so-ever true means provable and false means not provable
the meaning of these words proves that such a system cannot
get stuck in pathological expressions.

>
And such a definition requires the system to be keep simple or it becomes inconsistant.
>

>
LP := ~True(LP) has a cycle in the directed
graph of the elements of the expression related
to each other that Prolog and MTT detects.
>

>
So, what value does True(LP) return?
>

>
True(L,x)  means x is true.
~True(L,x) means x is untrue which includes false and not a proposition.
>
True(L,~x) means x is false.
~True(L,~x) means x is unfalse which includes true and not a proposition.
>
True(L,LP) is false and True(L,~LP) is false which means LP
is not a proposition.

>
And if x is defined in L as ~True(L,x) means that True(L, x) is false, then x being the negation of that result is a true statement.
>

*That is not the way it works in my system or Prolog*
~True(L, x)  means x is either false or not a proposition
~True(L, ~x) means x is either true or not a proposition
>
Try reading those two lines 150 more times and maybe it will
break through your ADD. Alternatively you are simply a liar.
>
It is something like trivalent logic {true, false, incorrect}
~true is false or incorrect.
~false is true or incorrect.
>

>
So if x is defined in L as ~True(L, x)
>
what value does True(L, x) have?
>

 then True(L,x) evaluates to false ultimately meaning
that x is incorrect.

But doesn't ~false evaluate to True?

 We can't know for sure that x is incorrect until
we see that True(L,~x) also evaluates to false.
 

And thus you system just blew up in a mass of flaming inconsistancy.
Since there is no requirement to check True(L, ~x) and it can't affect the value of ~True(L, x) you logic just doesn't work.
You need to go back and study how logic works, but my guess is you have wasted too much time on your other projects to do anything with this, and you have poisioned you reputation with all you lies so no one is going to look at this.
Pity, if you spent the last 20 year looking at this and seeing if you can work out the problems, it might have made an viable alternate form of logic, but we will never know since you killed it by lying about halting and incompleteness and Tarski.