whatisgithub

What is latent-lisp?

wondermonger-daydreaming/latent-lisp — explained in plain English

Analysis updated 2026-05-18

0Common LispAudience · researcherComplexity · 5/5Setup · moderate

In one sentence

A collection of experimental Common Lisp projects: a runtime that requires proof before accepting a claim, plus a workshop of playful, self-referential Lisp code.

Mindmap

mindmap
  root((latent-lisp))
    What it does
      Evidence based Lisp runtime
      Homoiconic play projects
      Language design documents
    Tech stack
      Common Lisp
      SBCL
    Use cases
      Study proof required claims
      Explore self referential code
      Read AI reviewed language design
    Audience
      Lisp researchers
      Formal methods readers
    Structure
      mneme instrument
      atelier workshop

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Study a working example of an evidence system that rejects unbacked claims in code.

USE CASE 2

Explore recreational Lisp programs that exploit homoiconicity, like self-printing programs and metacircular interpreters.

USE CASE 3

Learn how a formal review process between two AI models shaped a language design document.

What is it built with?

Common LispSBCL

How does it compare?

wondermonger-daydreaming/latent-lispnorvig/paip-lispatlas-engineer/nyxt
Stars07,45310,911
LanguageCommon LispCommon LispCommon Lisp
Setup difficultymoderatemoderatemoderate
Complexity5/52/54/5
Audienceresearcherresearcherdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 1h+

Requires SBCL installed and familiarity with Common Lisp to follow the code.

So what is it?

This repository is a collection of experiments in the Lisp programming language, split into two related parts. Everything is written to run on SBCL, a Common Lisp implementation, and the author treats a program running without errors as the basic test of correctness. The first part, called Mneme, is a small runtime built around one idea: a system should not be able to claim it verified something unless it actually holds proof of that verification. In plain terms, the code defines rules so that a bare statement like "I checked this" cannot be treated as a confirmed fact unless a matching certificate backs it up. The README is explicit that this protects against a cooperative caller using the intended interface, not against code with direct access to the internals, and that cryptographic protection is planned for later rather than already built. An included test suite reports a set of forged claims being correctly rejected alongside legitimate ones being correctly accepted. The second part, called the atelier, is a workshop of smaller, playful Lisp projects that explore homoiconicity, the property of Lisp where code and data share the same structure. Examples described in the README include programs that print their own source code, an interpreter written in the language it interprets, poems written as valid pieces of Lisp code, a recreation of the classic ELIZA chatbot, and a set of short experimental pieces exploring philosophical ideas through code. A newer part of the repository, added in July 2026, documents an attempt to design a more complete language specification for this style of system, including a review process where a second AI model critiqued the design and the author responded with revisions. Because this project centers on Lisp's unusual properties and experimental verification ideas, it will likely be most useful to readers already comfortable with Lisp or interested in formal approaches to trustworthy AI generated claims, rather than general programming beginners.

Copy-paste prompts

Prompt 1
Explain how the certificate requirement in the mneme kernel prevents a claim from being accepted without proof.
Prompt 2
Walk me through what a metacircular evaluator is using the examples in the atelier directory.
Prompt 3
Summarize the difference between the mneme instrument and the atelier workshop in this repository.
Prompt 4
Show me how the quine examples in quine-orchard work and why they print their own source code.

Frequently asked questions

What is latent-lisp?

A collection of experimental Common Lisp projects: a runtime that requires proof before accepting a claim, plus a workshop of playful, self-referential Lisp code.

What language is latent-lisp written in?

Mainly Common Lisp. The stack also includes Common Lisp, SBCL.

How hard is latent-lisp to set up?

Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.

Who is latent-lisp for?

Mainly researcher.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.