openflukeEARLIER DESIGNS
Paragon & Loom
Earlier approaches to the AI engine. These designs provided a place to try ideas around neural networks, different numerical representations, and the structure of computation.
A CONNECTED BODY OF WORK
Progress rarely travels in a straight line.
Different names. Different experiments. The same curiosity: where can intelligence and a simulated world become something useful, personal, and alive?
OpenFluke’s projects make more sense as a research journey. There were pivots because each experiment helped answer a question about where the engine fit, and what configuration was worth pursuing next.
The engine thread.
THE ENGINE TODAY · v1.2
Welvet
The engine that carries the work forward. The lessons from Paragon and Loom are part of Welvet’s foundation and continuing direction, from calculation and memory to learning systems, including optional Qualcomm Hexagon HTP on Windows ARM64.
The experience thread.
EXPLORING THE FIT
Primecraft · Biocraft · Birdkit · SoulGlitch
Games and applications that tested where the chaos simulation engine could fit best. Different experiences exposed different needs and suggested new configurations. Their lessons fed into the ALife OS prototype and then ALife: Becoming.
THE PROTOTYPE
ALife OS
A more focused exploration of artificial life: biology and machinery sharing a world. Proto, Kee, and a combined life gave the technology a clearer experiential language.
THE GAME · COMING SOON
ALife: Becoming
Extracted from the ALife OS prototype into a dedicated game about tiny planets, physical automation, bridges between worlds, and Sparks taught by demonstration.
Two threads, one body of work.
Welvet is the AI engine. ALife OS was the prototype. ALife: Becoming is the game. OpenFluke is the independent research practice bringing them together. The earlier names remain part of the explanation of how the work arrived here.