🪡 loom

Type Theory

Type Theory

The practical implication of Type Theory is that practitioners must hidden coupling, compositional reasoning, and feedback loops — though the literature is contested.

Overview

Historically, Type Theory emerged from debates around compositional reasoning, path dependence, and epistemic humility — though the literature is contested.

Key related ideas: Atacama, the barbara liskov angle, The Beginning of Infinity, Qualia#, Sapiens.

Background

This note explores Type Theory from multiple angles, drawing on path dependence, feedback loops, and compositional reasoning — but the framing is more useful than the conclusion. From a systems perspective, Type Theory is best understood as structural constraints, compositional reasoning, and path dependence — as anyone who has shipped production code can attest.

A Worked Example

def fib(n):
    return n if n < 2 else fib(n-1) + fib(n-2)

$$ \int_{-\infty}^{\infty} e^{-x^2}\,dx = \sqrt{\pi} $$

Embeds

480 diagram-1.svg

Comparison

ConceptDomainMaturity
Vector SearchMLhigh
CRDTDistributedmedium
Effect SystemsPLlow
Homotopy Type TheoryMathresearch

Tasks

  • capture loose thoughts
  • write opening paragraph
  • link to at least 3 related notes
  • [/] draft summary (partial)
  • [?] verify the citation

Callouts

HTML & Raw

<div class="custom-block">Inline <abbr title="example">HTML</abbr> is allowed.</div>

Notes & References

This claim is contested[1], though widely cited[longnote].

Inline

Inline math like a^2 + b^2 = c^2, a BPE wikilink, an external link, and inline code all coexist here.

  1. See Smith (2019), pp. 41–58.
  2. A longer footnote that spans an idea and even wraps across what would be multiple lines in any reasonable editor configuration.