ADAM / SYSTEM

How this
site works.

The projects, notes, and experiments all come from one small data file. You can get to any of it by clicking, searching, or typing a command.

Pages are generated as HTML at build time. Browser navigation reuses the same render functions. Experiment code loads when a visitor opens the lab, and numerical routines are independent of rendering.

The terminal parses a bounded mathematical grammar into functions. Expressions never pass through eval. Traversal, Fourier transforms, and cellular automata run locally.

The site has to work at two speeds: a quick scan of the work, and a slower read through the ideas. Everything stays readable as plain text and ordinary links if the graphics don’t load.

The 3D map uses Three.js and WebGL to place six areas in one coordinate space. Theoremis builds an example proof dependency graph; Overlappd rearranges example points around a chosen quality. A Lorenz attractor follows two separately integrated trajectories. The Fourier panel redraws what you draw, and the graph panel runs Dijkstra on a weighted graph. Ordinary links and Quick View reach the same content directly.

Trajectory geometry is computed once. The point field uses instancing, and the scene has a single animation loop that pauses outside the viewport and in hidden tabs. Pixel density is capped; touch devices use fewer points and simpler geometry. Sustained low frame rates switch to a lower pixel density and disable shadows. Navigation disposes geometry, materials, textures, observers, listeners, and the WebGL renderer.

Reduced motion starts the scene paused and makes camera changes immediate. Labels are ordinary links when graphics cannot load. Area buttons support keyboard navigation and return focus afterwards. Mobile uses tap-to-focus labels and compact panels. Press Shift + D on the map to see frame rate, draw calls, triangle count, and pixel density, or open “The math behind it” in a panel to read the mathematics.

The numerical core has deterministic tests for traversal, matrix transformations, Fourier reconstruction, the logistic map, and cellular automata. Build checks validate routes and local links. The lab shows computed state, not invented benchmark figures.

The Statue of Liberty is “Lady Liberty” by Anna M, used under CC BY 3.0 and recolored to match the scene. Everything else in the scene is generated in code.

I want to find the shortest explanation that still makes an idea click, and work out where an animation actually helps versus where a plain diagram is clearer.