Skip to content

Instantly share code, notes, and snippets.

@navicore
Created November 25, 2025 01:17
Show Gist options
  • Select an option

  • Save navicore/946327e6d42ceb98e6e9c27cd215614b to your computer and use it in GitHub Desktop.

Select an option

Save navicore/946327e6d42ceb98e6e9c27cd215614b to your computer and use it in GitHub Desktop.
The Patch Manifesto

The Patch Manifesto

The Patch Languages are a small family of embeddable languages designed to co-exist without collapsing into a single compromised “one language to rule them all.” Each Patch language is intentionally tiny, opinionated, and good at exactly one thing.

Patch consists of three cooperating cores:

  • Patch Seq – a concatenative execution language
  • Patch Qed – a logic and proof-search language
  • Patch Lisp – a meta-programming and macro language

Together they let programs be written, run, and justified without any one language doing work that belongs to the others.

1. Philosophy

Small languages beat big ones

Large languages accumulate features until their semantics blur. Patch flips the problem: each language stays small by refusing to own concepts better handled elsewhere.

Boundaries matter Patch

Seq does not prove things. Patch Qed does not do I/O or mutation. Patch Lisp does not become a runtime everything-machine.

Interop is the shared center

Patch languages share:

  • a common value representation (numbers, symbols, lists, maps)
  • a small IR vocabulary
  • explicit calls across boundaries

Tools, not empires

Patch is not a monolithic language. It is a rack of small modules—like a modular synth.

2. The Three Cores

Patch Seq A tiny concatenative language:

  • stack-based evaluation
  • words as building blocks

Patch Qed A tiny logic/proof-search core:

  • facts, rules, clauses
  • goal solving + entailment

Patch Lisp A tiny Lisp dialect:

  • macros and code generation
  • AST transformation

3. Design Rules

  1. Seq owns execution.
  2. Qed owns reasoning.
  3. Lisp owns metaprogramming.
  4. No contamination.
  5. Interop is explicit.

4. The Patch Promise

Patch languages will remain small, clear, inter-operable, and exploratory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment