The evidence file that holds

01Two kinds of files

When a name is abused, the first instinct is to collect. Screenshots pile up in a folder: the infringing listing, the copied logo, the lookalike page. Months later, when the matter reaches a registrar, a marketplace, or a tribunal, that folder turns out to be worth very little. Nobody can say with certainty when each image was taken, from where, by whom, or whether it has been altered since. The other side does not need to prove the captures false. It only needs to observe that no one can prove them true.

The second kind of file looks similar from a distance and is a different object entirely. Every item in it answers four questions before anyone asks: what exactly was captured, when, from where, and how it has been kept unaltered since. The difference between the two files is not effort at the end. It is discipline at the beginning.

02What a capture must carry

A defensible capture is a record of an observation, not a picture. It carries the full address of what was observed, the date and time of the observation to a standard a third party can rely on, the method by which it was taken, and a fingerprint of the file itself, a cryptographic hash computed at capture, so that any later alteration is detectable by anyone. Where the observation matters commercially, it is repeated over time: a single capture proves a moment, a series proves conduct.

None of this is exotic. What is rare is doing it as routine, before there is a dispute, on material that may never be needed. The habit feels wasteful right up to the day it is decisive.

03Continuity is the argument

In a fight over a name, the deciding question is usually not who filed a form first, but who can show the longer, denser, more consistent record of actually using the name and defending it. Registrations matter, and filings matter, but they sit on top of something more fundamental: continuity. A domain held without interruption, pages published year after year, services offered under the name and documented as they were offered. A record like that cannot be assembled after the fact, which is precisely why it is persuasive.

This is also why volume is the wrong goal. A thousand undated screenshots lose to thirty captures spread across five years, each one dated, hashed and consistent with the rest. The tribunal is not weighing paper. It is weighing whether the story could have been fabricated. Density over time is what makes fabrication implausible.

04Built before the fight

The file that holds is assembled while things are quiet. The name is watched across marketplaces, social networks and registrars; when something appears, it is captured the day it appears, not the month the client notices the damage. Takedown requests are prepared on the platform's own terms, because a request that cites the right policy clause is processed and a complaint that vents is ignored. And everything, the abuse, the capture, the request, the platform's response, goes into one chronology, so that the matter can be read end to end by someone who was never in the room.

That reader is the point. Files of this kind are read years after they are written, by an examiner, a panel, or a court, and they are read cold. The file must not need its author standing next to it, explaining. It must hold on its own.

05Where the file goes

Mulium prepares the record; it does not argue it in court. Filings, appearances and formal legal steps belong to the client's own licensed counsel, and the file is built so that counsel can stand on it without reservation: every capture attributable, every date verifiable, every exhibit traceable to its source. In practice, the quality of that handover decides how much of the record survives contact with the proceeding. A file that holds makes the lawyer's argument shorter, and the opponent's options fewer.