# A filename that reads like a changelog

> ep07.v2.fixed-timing.720p.mkv — six dot-separated segments, each one a decision somebody made and wanted the next person to see before opening the file.

August 21, 2026 · https://justog.club/stories/the-quality-note-in-the-filename

One line, large monospace, across the chest: `ep07.v2.fixed-timing.720p.mkv`.

Six segments, split by dots, each in its own shade so the eye reads it as parts rather than one
long word.

Nobody wrote a sentence here. They wrote a record of what happened to the file before it reached
you.

## What does each segment actually say?

Read left to right and it's a small report.

`ep07` says which one. `v2` says which attempt — not the first pass, a correction of it.
`fixed-timing` says what the correction was, specifically, rather than a vague "improved."
`720p` says how much detail survived. `mkv` says what kind of container the whole thing sits in.
None of it is decoration. Every segment answers a question the next person opening the file would
otherwise have to guess at.

## Why do 'v2' and 'fixed-timing' matter so much?

Because together they're an apology and a receipt, in four words.

`v2` alone would just mean *a second copy exists* — unhelpful, maybe even a warning sign. Paired
with `fixed-timing`, it becomes something specific: the first version had a problem, someone
noticed, and this file is the correction, not a duplicate to be ignored. That's the same instinct
that leaves
[a subtitle deliberately timed a few frames ahead of the speech it translates](/stories/the-subtitle-that-arrives-early) —
timing is the kind of error that's invisible until it's wrong, and worth naming the moment it's
been fixed.

## Why not just rename it to something tidy once it's finished?

Because the messy name is doing a job a tidy one can't.

A file called simply `episode-7.mkv` tells a future viewer nothing about its own history — whether
it's the corrected pass, what got corrected, or how it compares to a copy already sitting on their
drive. The dotted, ugly version keeps that history attached to the object itself instead of a
separate note that could get lost or go unread. It reads exactly the way
[a scan keeps the shadow of the book it was pressed from rather than smoothing it away](/stories/the-scan-with-the-gutter-shadow) —
evidence of process, left in on purpose because it answers a question before anyone has to ask it.

## Can I use a filename from a real release?

If a specific real file's exact name is the point, that name was chosen by whoever produced and
distributed that file, and copying it that precisely is really about that release rather than the
format.

The name on this shirt names nothing that exists — an invented episode number, an invented fix, a
resolution and a container that describe a category rather than a copy. The dot-separated structure
itself isn't owned by any one release; it's a convention that grew up across an entire community of
people solving the same problem the same way.

## Does the idea work for something that isn't a video file?

The structure — short tags, dot-separated, ordered from the most specific to the most general —
shows up anywhere something gets handed off with its history attached: an archive, a document, a
run of scans. It's the same accounting instinct behind
[a grid marking which stretches of a season are considered filler](/stories/the-episode-that-is-filler) —
both are somebody converting a judgement call into a compact, legible mark, for the benefit of a
stranger they won't meet.

## Does it print well?

Yes, and monospace is exactly the right choice for it — every character holds the same width, so
the segments stack into clean, even blocks rather than drifting type that's hard to parse at a
glance.

Two to three inks are enough: a base tone for most of the string and one or two accent tones on the
segments that matter most, `v2` and the resolution. Keep the type large — this depends on being
readable across a room, and small monospace on cotton tends to fill in at the counters of letters
like `e` and `o`.

## How do I get one made?

Describe the file at [JustOG](/) — what happened to it and in what order the segments should run.
Pick a direction, drag the crop frame, see it composited on the real garment, and it's made to
order and shipped.

Designs other people have published are in the [shop](/shop).

Six words, none of them the title. All of them true about the file.