Eski ProjectsCODE · MATH · MEDIA · SYSTEMS
My software project index

I use each project as a different test surface.

These projects overlap on purpose. I move related ideas into different technical contexts so I can observe what changes, what survives and what becomes measurable when I translate the same concepts into another system.

Mathematician's Groovebox

What I'm trying to validate: mathematical input can remain reproducible through several media.

I built Groovebox as a deterministic generative music, visual and game engine driven by mathematical seeds. Notes, rhythm, synthesis, audiovisual graphics, imported media and procedural game worlds all become downstream observations of one input state.

What I test: repeat a seed; compare audio-only and audiovisual exports; change one canonical contribution and inspect the result; save/load a project and compare it with live playback.

Tabletime

What I'm trying to validate: social relevance can be represented as transparent numeric/topic relationships.

I designed Tabletime so tags can carry values, signs, comparisons and arithmetic rather than acting only as labels. I also extend it through independent hosts that can exchange public/global content while keeping private data local.

What I test: numeric tag parsing, signed relevance, search/index behavior, bounded database cleanup, independent node setup and host-to-host exchange.

EQR

What I'm trying to validate: mathematical relationships should be executable and inspectable.

EQR is one of my deliberately small test surfaces. I put mathematical relationships into shell computation so I can run them, render their results and compare behavior directly.

sCode & sOS

What I'm trying to validate: the project vocabulary can survive below the application layer.

sCode gives me a native language/runtime direction and sOS wraps system profiles, boot/install tooling and project applications around it. I keep runtime-tested targets separate from targets that only have scripts or planned support.

GOAVA

What I'm trying to validate: one algorithm can organize audiovisual generation as a coherent object.

GOAVA is my generative optimized audiovisual algorithm. It sits between my standalone mathematical work and Groovebox's larger deterministic media engine.

Pre-2019 software

I keep my earlier work available because it shows the path into the current systems.

Catwalker, WaveBricks, CS Figures, Bananadine and historical server material preserve my earlier game, generative audiovisual, mathematical visualization and networking experiments. The larger originals live in my dedicated pre-2019 GitHub repo; selected small artifacts are also mirrored on this site.