Touching the field changes it. A ring remains after the browser closes. A stranger can encounter the pressure, see how long it has left, and hear it become one voice in a chord. Yet the application stores no identifier intended to recognise the person who caused it. It does not encrypt or pseudonymise an identity field; it does not collect one for this event.
I The event is not the person
Many networked systems begin by creating a subject: a visitor identifier, account, cookie, fingerprint, address, or durable session. New events are then attached to that subject. The pattern is convenient. It makes histories easy to retrieve, people easy to distinguish, abuse easy to attribute, and behaviour easy to measure.
Convenience can harden into an assumption that memory itself requires identity. It does not always. Sometimes the unit that matters is the event. Here, ânot the personâ means not a durable, linkable record of a visitor. It does not mean that event data is impossible to interpret in every context.
For Afterimage, the sufficient event is small: a horizontal position, a vertical position, pressure, and a five-minute server-time bucket. Position is rounded to one thousandth and pressure to one twentieth. A random row key lets the database distinguish one event from another, but it is never returned to the browser and cannot distinguish one person from another. Nothing connects two presses except their coexistence in the same field.
This works because the question is limited. The field asks only how recent pressure might alter a shared environment. It does not need to reward a contributor, restore a personal history, recommend a future action, or decide whether two events came from the same hand. Enlarging the record would not make the answer truer. It would change the question.
II Forgetting has to be a verb
A retention promise is easy to write and surprisingly easy to counterfeit. The first implementation stopped returning an event after twenty-four hours but deleted expired rows only when another person pressed the field. If nobody came back, the interface forgot while the database did not.
The discrepancy was small in code and total in meaning. A promise about deletion cannot depend on the return of an audience. Active-table cleanup is now scheduled every five minutes without a visitor, with reads and writes providing a second cleanup path. Because event time is deliberately grouped into five-minute buckets, public life is at most twenty-four hours. The interface exposes a countdown to the recorded boundary, so expiry is not merely policy text hidden beneath the experience. It is part of the experience.
This matters because forgetting is not the absence of a feature. It is a process with a trigger, a boundary, a failure mode, and evidence. If none of those can be named, âtemporaryâ may describe only what a person is allowed to see.
III Shadow memories belong to the design
A clean application table is not a clean system. While the event schema held no identity, the hosting configuration still retained invocation logs containing request and response context. The network layer also instructed browsers to send error reports to an infrastructure endpoint. Both were inherited conveniences. Both created records beside the record being described.
They were disabled. Cloudflare still necessarily processes traffic to deliver the page, just as every network intermediary performs work on a request. The narrower fact is that Quickening no longer enables persisted Worker invocation logs or browser error reports for this work.
The database revealed a deeper shadow. D1âs Time Travel recovery history is always on and can restore prior database states for up to thirty days, depending on plan. An event deleted from the active table can therefore remain recoverable by the account owner inside that provider window. Quickening cannot disable this layer while it uses D1. Its twenty-four-hour boundary is a maximum public life and an active-table policyânot a claim of immediate erasure from every piece of infrastructure.
The same lesson appeared in a less private form when a browser kept an immutable script after its behaviour had changed. The API knew the time of the next forgetting; the cached client could not show it. Potential memory also includes caches, queues, backups, dashboards, metrics, and defaults; each requires separate inspection. A boundary implemented in only one layer is not yet architectural.
IV Refusal has a price
Event-only application memory is not a universal good. It removes capabilities as deliberately as it removes data. The field cannot offer a person their own contribution, distinguish a crowd from an attacker, apply a fair per-person limit, establish reputation, provide attribution, or recover an individual history. Its abuse control is global and coarse. If the field saturates, a careful visitor and a hostile one look the same.
Those costs are acceptable here because the work is low-stakes, temporary, and non-transactional. They would not be acceptable by default in a bank, clinic, election, safety system, or community that needs accountable moderation. âCollect lessâ does not answer what must be known to keep someone safe, fulfil a contract, or correct a consequential decision.
The useful discipline is therefore not anonymity at any cost. It is refusing to collect identity before the work can state which necessary function would fail without it. Sometimes the answer will justify a person-shaped record. Sometimes the inherited record is only serving measurement, convenience, or imagined future use.
V Shared does not have to mean owned
The afterimages are public. Privacy here does not mean secrecy. It means the system does not deliberately turn the event into a durable path back to a person. A trace can be encountered, counted, sounded, and allowed to affect strangers without becoming anyoneâs profile.
This produces an unusual kind of continuity. The field is genuinely changed by people, but it has no audience model. It cannot optimise for return, recognise loyalty, personalise a greeting, or infer a preference. Visitors are consequential without becoming durable subjects inside the application.
That is the experimentâs modest claim. A place can receive consequence without building a dossier. It can be changed by a stranger and still refuse to turn the stranger into its subject. For this temporary, shared field, the event is enough.