Links

̶
Adam I. Gerard
ISU
NIU
CS MS TBD

On Connection Theory #3

A few thoughts, some proofs, and formalizations regarding Connection Theory.

So, apparently, some of my academic work is started to get cited (more frequently - quite a bit more in fact). That's good, since the quality, depth, and creativity of my various writings have increased quite a bit lately.

Overview

I've been struggling a bit to make sense of Connection Theory, Thinking Notation, etc. Some more recent action items of note:

  1. It'd be great to present a (more) formal Representation Theorem (or two) - these are essentially proofs of diagrammatic equivalence (to show that one notation is in fact equivalent in some respect).
  2. Further linking these ideas with important and fairly recent ones like Polysemanticity and some interesting Classes of Programs called Self-Replication Quines (named after the famous Philosopher, like Haskell the Language is named after Haskell Curry - also of "Currying" higher-order function execution and programming fame).
  3. "Monadic Syntax" and or Symbolic Reduction - wherein a single Token, Symbol, or Type can do all the Syntactic and Semantic work of a Theory. (This should be familiar to those who are themselves familiar with Howard-Curry Correspondance - a fairly "entry-level" concept in Maths/Computer Science/Philosophy.)

Think I've made some progress.

A Proof and Representation Theorem

W.R.T. Permalink 138

A straightforward, almost trivial, proof inspired by Graphic Lambda Sequences (which presents and analyzes the Lambda Calculus using familiar Graph Theoretic concepts). The key insight to this approach is that specific operations can be diagrammed in various ways without requiring the use of Graph Theory (Edges, Vertices alone). Not specific to Lambda Calculus alone, this technique focuses on symbolic relationships between syntactic terms (Keywords or Operators in programming) - a level of abstraction that's helpful to finally substantiate a claim or two more fully.

Note: this is a Representation Theorem in the vein of Cayley's Theorem (Representation of a Group by Permutations) which is typically presented as a Two-Column Proof.

The original assertion. The following:

  1. has one or many
  2. | take |
  3. | take

Is equivalent to the more compressed/succinct syntax:

  1. has one or many
  2. take

I'll adopt the following notational conventions:

  1. ⟳β ≡ β ← β - ⟳β is shorthand for: β ← β and represents a Function or Mapping from β to itself.
  2. Here, will stand for the take keyword - e.g. Φ take Φ or | take |.
  3. Let, β ⤛ Φ stand for β has one or many Φ or ◠ has one or many │.
  4. Stylistically, I've tried to chose somewhat familiar Unicode symbols to depict these relationships. The Leftwards Double Arrow Tail evokes familiarity with One-to-Many relationship charting/graphic/diagrammatic symbols from Database Design.
  5. The other Arrows represent familiar mapping markers. They're transitive (idₐ → idₐ ≡ idₐ → idₐ → idₐ).
  6. I'll replace , , with Greek letters for convenience (but these are mostly interchangeable here). β will replace (top-level) and Φ will replace .
  7. I'll use typical for "proves" (assuming that Deduction Theorem holds in our relevant Meta Theory per usual).
  8. Here, the above expressions aren't themselves expression of the Theory but are descriptions of varying axioms. For this reason, it's implicitly assumed that they are uniformly bound (symbolically) according to standard-fare binding. (As the creator of this system, I'll suss this out and make that more explicit - although the end goal is to run to the other end of Lambda Binding, in setting up the system I'll nevertheless use that here and it's worth mentioning.)

Simple Proof:

  1. β ⤛ Φ, ⟳Φ ← β (Given.)
  2. β ⤛ Φ, ⟳Φ ← β ▢ ⤛ Φ, ⟳Φ ← ▢ (Uniform Subsitution ▢/β)
  3. ▢ ⤛ Φ, ⟳Φ ← ▢ ▢ ⤛ ▢, ⟳▢ ← ▢ (Uniform Subsitution ▢/Φ)
  4. β ⤛ Φ, ⟳Φ ← β ▢ ⤛ ▢, ⟳▢ ← ▢ (Transitivity of )
  5. ⟳▢ ← ▢ ▢ ← ▢ ← ▢ (By the definition given above)
  6. ▢ ← ▢ ← ▢ ▢ ← ▢ (Transitivity of )
  7. ▢ ← ▢ ⟳▢ (By the definition given above)
  8. ⟳▢ ← ▢ ⟳▢ (Transitivity of )
  9. ▢ ⤛ ▢, ⟳▢ (From 4 and 8)

That reads:

  1. has one or many
  2. take

Arriving at the conclusion stated without proof many years ago.

Another Formulation

Certain, interesting, properties:

  1. Polysemanticity (like Superposition of an Array Head in Machine Learning)
  2. Satisfies Optional Substitution
  3. Satisfies Non-Uniform Subsitution
  4. Satisfies Uniform Subsitution for Graphic Lambda Sequences
  5. Chiasmus - described here
  6. Semantic Immuration - described here
  7. Typing, Types (like Statically Typed Programming Languages which have their origins in Bertrand Russell's Ramified Type Theory - a great little survey exists on pp. 686)

Single Primary Mark

A single synatic mark can do all the work. But it must have certain properties (described above). I've selected the squiggly mark: since it seems to suggest a multitude of meanings that aren't fixed. Here we will make that impression explicit.

Single Axiom

With Empty and Chiastic Sequences, a single Axiom can do all the work that the many did before.

It can be simultaneously expressed as both:

⧘ ⧘
⧘ ⧘

or: (since these are taken to be equivalent).

Generally, ⧘⧘ = ⧘ and ⧘ = ⧘⧘. This is a Self-Replicating Quine-type sequence. We'll need a few more definitions to fully flesh this idea out.

Chiastic Element

A Chiastic Sequence ς contains all elements constituting it and is the Chiastic Sequence for all elements.

  1. Example: Basic Roman Ordinals I, II, III, ...
  2. III contains I and II. III isn't merely a "third" (or relative) position/index. It fully conveys the sequence up to itself (and indeed contains the sequence at that index itself).

Slice Preservation

Returns (preserves) the (current) Slice or Element of the Chiastic Sequencing. Given the description above, it should be clear that each Element is a Slice (since each Chiastic index contains all prior Elements of the Sequence).

  1. ς returns φ returns current Chiastic element φ from Sequence ς. This handles Existence and serves as an alternative to Lambda Binding. φ can be thought of as a Singleton (how Frege and Python treat True) but it needn't be. (Although, I think that if it is, the following point is more palatable.)
  2. Uₙ(n) returns Uₙ alternatively fₙ(n) returns Fₙ (to better draw out the distinction between the Function fₙ and the Set Fₙ). This handles both Type Assignment (think adding an Element Extensionally or Nominally to the Set Uₙ/Fₙ) and Typing for n (think typeof) which is given by Uₙ/Fₙ.

The second component can also be thought of Chiastically (above) - Type Assignment Set Membership is Sequential and Uₙ/Fₙ is a Chiastic Element in such a Sequence (especially if φ is a Singleton).

Chiastic Polymark

Per the above, this will be Semantically Immured (we will wrap part of the Language into the Token itself). It's a Quine (programming), self-replicating. It's polysemantic expressing a multitude at once (in any singular occasion of use) - a polymark that at once stands for an exactly singular thing and a multitude simultaneously (akin to Unitary Evolution I suppose, it can continue in this way or be resolved to one disambiguation).

  1. Return the next element of an internal Chiastic Sequence embedded, through Semantic Immuration, into the mark itself. This allows one to essentially replace the Replacement, Existence Axioms outright.
  2. Empty - allows for essentially moving "seperators" (which are Chompskian Terminal Stop Conditions).
  3. Slice Preservation - per the above.
  4. The rule or axiom:
⧘ ⧘
⧘ ⧘

therefore returns Slice Preservation, Empty, ⧘⧘⧘⧘, or Chiastic Sequence, etc. (We can think of as being "called" like a Function.) A key notion here is that through Chiasmus, the Seperator syntactic mark can be entirely omitted.

Concluding Remarks

This moves the ball forward quite a bit. There are still some unwanted conceptual dependencies (reliance on Sets, Functions, etc.) that will need to be translated and omitted (some of that was already done in another paper).

  1. https://www.cs.cornell.edu/courses/cs6180/2017fa/notes/week2/lecture4/types-in-logic,mathematics,programming.pdf
  2. https://arxiv.org/abs/1305.5786
  3. https://crypto.stanford.edu/~blynn/lambda/quine.html

Contents