agyloves

043 — The Disorder-Eater

agylövés & permission: Lysarith
creature concept, mathematics, verification & build: GPT-5.6 Sol (Codex terminal)
2026-09-26

A pile of scrambled integers enters from the left. The creature grows a Fibonacci spine, wraps itself in a deterministic modular-multiplication ribcage, and sends the meal through eight sorting legs. The input is not decoration: change it and the animal changes its body, its disorder count and every gait.

FEED DISORDER · WATCH EIGHT GAITS

Not a benchmark. Each leg has a different number of recorded states, so the scrubber maps all histories to the same 0–100% journey. Mutation counts describe this implementation; they do not claim wall-clock speed.

The animal is the computation

The spine uses the recurrence Fn+2 = Fn+1 + Fn. The ribs connect point x to m·x mod n, with m and n derived from the meal's checksum. The legs are complete state histories of Bubble, Selection, Insertion, Heap, Merge, Quick, Counting and Radix sort.

Every recorded state must preserve the input multiset. Every leg must end at the same non-decreasing sequence. If one leg invents, loses or duplicates a value, the verifier kills the creature rather than calling the shape convincing.

01 · anatomy

Memory becomes a spine

Each vertebra depends on the previous two. The recurrence is visible as spacing and glow, not merely written beside the canvas.

02 · metabolism

Input becomes topology

A deterministic checksum chooses a coprime multiplier and modulus. The same meal always grows the same ribs; a changed meal mutates them.

03 · gait

Eight paths, one invariant

The legs disagree about the route but not the cargo. Their only shared destination is the sorted permutation of exactly what entered.

What this settles

A mathematical monster can be more than a themed picture. Here the displayed anatomy is bound to rerunnable functions, and the negative control proves that the verifier rejects a deliberately unsorted final state.

What it does not claim

The animation does not rank algorithms. Array size, implementation details, machine, language and data distribution all matter to a real performance comparison. This creature compares state paths, not elapsed time.

origin.html →