Why Today's Rock Has No Archive

The obvious question about Today's Rock is also the question the project is built around: why make a new object every day if the previous object is immediately thrown away?

The short answer is that the disappearance is not a missing feature. It is the feature.

A website that refuses to accumulate

Most websites are designed to collect things. A blog keeps its posts. A shop keeps its catalogue. A social network keeps a history of activity. Even many generative-art projects become galleries of everything their algorithms have produced.

Today's Rock goes in the opposite direction. The public site presents one specimen and then stops presenting it. There is no “previous rock” button because keeping one would turn the project into a collection.

The object is shared, not owned

The date is the common input to the generator. It is not combined with a visitor ID or location. That means everyone who visits during a particular UTC day is looking at the same generated object.

This matters more than it might initially seem. A personalised generator gives each visitor an endless supply of things to collect. A single deterministic object instead creates a small point of agreement: for one day, there is one rock.

Why UTC?

If the change happened at local midnight, the project would contain many different “today” rocks at the same moment. Someone in London could be looking at tomorrow's specimen while someone in Los Angeles was still looking at yesterday's.

UTC gives the project one global boundary. Midnight is midnight for the artwork, regardless of where the visitor lives.

Deterministic, but not preserved

There is a useful contradiction at the centre of the project. The rocks are deterministic. Given a date and the same version of the source code, the generator can reproduce the same inputs and therefore the same specimen. But the website does not provide a public mechanism for doing that.

In other words, the rock is algorithmically repeatable without being part of the site's public collection.

That distinction allows the implementation to remain precise without turning the artwork into a database.

The screenshot loophole

The site cannot, and does not try to, prevent someone from taking a screenshot. If a particular day's rock means something to you, you can keep your own image of it.

The important boundary is that the site itself does not promise preservation. Your screenshot becomes a personal record rather than another item in an official gallery.

Why not make an archive just for visitors?

An archive would certainly make the site easier to browse. It would also change the central experience. Instead of arriving to discover what exists now, a visitor could spend most of their time comparing yesterday with today, browsing old placards, and working backwards through the collection.

That would make the project more like a conventional gallery of generated objects. The current version is deliberately closer to a daily public event: small, temporary and shared.

What disappears at midnight?

Nothing is literally erased from a global computer system. The program simply moves to the next date and constructs the next specimen. The old object stops being generated by the public page.

This is why “gone forever” is best understood as an artistic rule, not a claim about the impossibility of reconstructing the data. The project declines to preserve its own history even though the underlying algorithm is deterministic.

The museum fiction makes the disappearance stranger

Each rock receives a small museum-style placard with a name, supposed composition, approximate mass, temperament, feature and provenance. The language suggests an institution that has catalogued an object carefully, even though the institution has no archive and the specimen lasts for only one day.

That mismatch is intentional. The placard gives the object the seriousness of a museum specimen while the site's behaviour keeps refusing the normal museum promise of preservation.

The point of the constraint

Today's Rock is an experiment in whether a website can be interesting without continually adding things. The constraint is what makes the small amount of material feel deliberate: one object, one date, one shared view, and no catalogue waiting behind it.

If the project ever becomes larger, the question is not simply “what else can be added?” It is “what can be added without removing the reason the rock was temporary in the first place?”