Independent research laboratory

Other ways
to compute.

Lathilda explores other ways computers can be built, programmed and experienced.

Foundation established. First flagship not yet selected.

01 / The question

Computers are not finished objects.

Most software assumes the same arrangement: silicon executes instructions, state moves forward, and the machine stays politely invisible.

We treat that arrangement as one possibility among many. What happens when voltage, yarn, mechanical motion or a collective of small robots becomes part of the computational idea? What changes when programs reduce as graphs, run backwards, handle effects explicitly or identify themselves by content?

Lathilda builds concrete answers: languages, runtimes, machines and public instruments. The result should not only be unusual. It should reveal a capability, constraint or experience that conventional computation hides.

Not a catalogue of exotic technologies
Not a rebrand of existing engine work
Always a mechanism you can build or experience

02 / Two axes

Two doors into
the same strange room.

The axes intersect, but neither is a list of favored tools. A project earns its place by asking a real question about the medium or the way execution works.

Axis APhysical medium

Computational substrates

When the material does part of the thinking.

Voltage, movement, yarn, chemistry or collective behavior is not incidental hardware. Its physics becomes an operation, a memory, a constraint or a language.

  • analog circuits
  • mechanical systems
  • textiles
  • robot swarms
  • neuromorphic media
Axis BProgram behavior

Alternative execution models

When running a program means something else.

Evaluation can be lazy, parallel, reversible, effect-aware or content-addressed. Different rules change what can be expressed, optimized, inspected and composed.

  • graph reduction
  • interaction nets
  • reversible execution
  • algebraic effects
  • content-addressed code

03 / A recurring practice

Make the mechanism tangible.

A public computational instrument is not a third research axis. It is how a real substrate or execution model becomes something people can touch, hear, steer or understand.

The instrument may be a browser experience, a game, a physical machine or an interactive proof. Its public appeal never substitutes for technical substance.

mechanisminstrumentunderstanding
Reduction grovestep 00

Touch a node. Watch the graph find another shape.

04 / Candidate register

Possibilities,
not promises.

No flagship has been selected. These cards are candidates awaiting a tournament on mechanism, contribution, feasibility and public experience.

Candidate · not active

Reversible debugger

Step through computation in both directions and expose which operations genuinely lose information.

Execution model
Candidate · not active

Analog equation room

Patch equations into a live, visible circuit and feel numerical behavior as a continuous physical process.

Substrate + instrument
Candidate · not active

Parallel reduction lens

Make interaction-net reduction inspectable enough to compare what parallelism gives and what it complicates.

Execution model
Candidate · not active

Programmable textile

Build a textile whose topology, touch and deformation participate in the computation rather than merely housing it.

Substrate

Selection tournament

  1. 01 Is there a real mechanism?
  2. 02 Can we make a contribution?
  3. 03 Can we build the smallest honest artifact?
  4. 04 Does the public experience reveal the mechanism?

Familiarity with Haskell, WebGPU or an existing project gives no automatic advantage.

05 / Preserved systems

Built before.
Still real.

The new identity does not rewrite the past. These systems keep their own histories, questions and review states.

06 / Open laboratory

There are more kinds
of computer to discover.

We are building the foundation now. Follow the work, inspect the systems, or return when the first candidate survives selection.

Explore Lathilda on GitHub