Skip to content

Repository files navigation

The Weaving Void

Visible meaning. Hidden operation. One shared surface.

The Weaving Void is an executable laboratory for artifacts that support more than one reading: prose and program, surface and generator, visible meaning and hidden operation.

The repository began as an archive of esoteric programming languages. Those languages remain as working studies, but the central object is now the weave: the deterministic relation that lets a human-readable surface carry an executable thread.

Start here

  • The Weave defines the operational spine and the boundary of the project.
  • Subtext is the first canonical specimen: ordinary prose deterministically compiles to a Marginalia program and leaves the trace VOID.
  • Marginalia is the first canonical loom, a language of notes, doubt, folding, and verification.
surface --reader/key--> thread --loom/runtime--> trace

The inverse direction is the harder construction problem: given an intended human meaning and a desired program or trace, construct a surface that carries both.

Reproduce the first weave

python3 weaves/subtext/reader.py weaves/subtext/carrier.md --explain
python3 Marginalia/interpreter.py weaves/subtext/extracted.mrg
python3 -m unittest weaves.subtext.test_reader

The carrier, public reader profile, extracted thread, expected trace, and mutation tests are all committed together. The specimen uses visible sentence features only; it is an experiment in dual reading, not secrecy or cryptography.

The archive

The existing languages are retained as studies of different carriers, memory models, and runtimes:

Language Study Implementation status
Distaff Auditory drafts and a bridge from notation to execution Working
Vortex Early cyclic tape-machine and syntax study Working
MandelMemory Spatial and dynamical memory addressing Working
SFract Thread construction through L-system growth Working
Entanglement Linked-state variables and destructive observation Working
Gastronomy Culinary surface vocabulary over a tape machine Working
Clockwork Register-machine computation and synchronization Working
Bloom Constraint-oriented continuous simulation Concept sketch
Marginalia Annotated memory, compression, and verification Working / canonical loom

New languages should be added only when they test a property that the current archive cannot: a new kind of surface, reader, loom, trace, or transformation.

Project discipline

A canonical weave must include:

  1. a meaningful human-facing surface;
  2. a public deterministic reader;
  3. the extracted thread;
  4. an executable loom;
  5. the expected trace;
  6. tests for invariance and structural failure.

Zero-width characters, opaque metadata, appended payloads, and secret binary blobs are outside the canonical scope because the visible and executable readings do not depend on the same material.

Running the archive

Interpreters target Python 3.10+:

python3 <LanguageFolder>/interpreter.py <SourceFile>

Bloom additionally depends on NumPy:

python3 -m pip install -r Bloom/requirements.txt

Run the full archive smoke test with:

python3 scripts/smoke_test.py

Related work

  • systems-and-intelligence holds the broader Trace-to-Generator and construction-versus-deduction questions. This repository is a narrow executable laboratory for them.
  • the-weaving-sound explores generative organization in sound. Distaff is a deliberate bridge, while the projects keep separate runtimes and scopes.

License

MIT License — see LICENSE.

About

An expanding grimoire of esoteric programming languages. Weaving logic, philosophy and bizarre computational paradigms into the void.

Topics

Resources

Stars

Watchers

Forks

Contributors

Languages