Essays
The thinking behind the answers.
The collector’s library answers questions: how to insure a collection properly, what an executor will need, how to document provenance so the record survives. This is the other half — why those answers are what they are, and what building an archive for them taught us about the problem.
A closed set, written once and kept. Not a blog, not news, and not a running commentary on a product. Each piece argues a position a reasonable person could dispute, and each is written to leave you with something you can act on today whether or not you ever install anything.
The record, and what it is for
Why every heirloom deserves its own story
Everything else about a watch can be reconstructed by a stranger with a loupe. Why it was kept cannot, and it leaves when its owner does.
Why every watch deserves its own record
Collections are recorded as lists. No serious question about a watch is ever a question about the list.
What spreadsheets eventually forget
Not rows — rows are safe. Everything that never became a column, quietly overwritten by somebody being conscientious.
Owning, and documenting
Owning is a fact about now. Documenting is the ability to still support it later, to somebody with no reason to believe you.
The quiet cost of an undocumented collection
Nothing fails loudly. The cost is charged at a claim, at a sale and at probate, and none of it is ever reported back to you.
Why provenance outlives market value
Valuations decay and can be rebuilt in an afternoon. Provenance compounds and cannot be rebuilt at all.
What a collection asks of the person holding it
Stewardship versus ownership
Nobody is the last owner of a good watch. Everybody is a middle owner, and that settles arguments ownership cannot.
What begins after the purchase
Every guide addresses the moment before buying. Everything determining what the watch is worth in twenty years happens after it.
Preparing a collection for the next generation
The hard part is not deciding who gets what. It is that they will decide well only with information nobody left them.
Why the software is shaped this way
Designing for the person who inherits
The reader who matters most has never opened the application, does not collect, and will give the record one attempt.
Designing for collectors, not accountants
Most collection software is a portfolio tracker with watch-shaped fields, and it decides the cheapest watch is the least significant.
The number we took out
An inflation-adjusted gain is arithmetically correct and quietly dishonest. Why it was removed rather than improved.
What an executor's document taught us
Building for a reader who does not care about watches revealed which fields a collection record is missing entirely.
When it stopped being about watches
The feature that changed what the software was for had no financial value and would never have survived a roadmap.
Where the data lives
Why local-first still matters
Not nostalgia. The useful question is not how well a record is protected, but how many copies of it exist.
The wrong shape for a collection
Cloud architecture solves collaboration, access and device loss. A private inventory of valuables needs none of the three.
What a record owes the truth
A record that can say I don't know
An empty field means either nobody got to it, or somebody looked and the answer is gone. Only one of those is a task.
Every number on a screen is a claim
Computation confers authority exactly where it is least deserved: a total of guesses looks more reliable than the guesses.
"I'll remember"
Memory does not produce blanks. It produces confident wrong answers, which is worse, and it does it on the details that later matter.
A collection nobody is optimizing
Most real collections are a residue of reasonable decisions, not a curated set. A value-only record calls that a series of errors.
What cannot be undone
Condition is spent, not held
Case metal is a finite quantity that only decreases — and most of it is spent by owners trying to improve the watch.
The paperwork outlives the service
A service protects the watch for five years. Its invoice protects the value for the rest of the watch's life, and costs nothing.
Document the one you would never sell
Documentation effort follows value, which puts it on the pieces least likely to still be there when somebody reads the record.
Wanting belongs in the record
"Excluded from every total" and "not recorded at all" were collapsed into one rule, and the research from a long hunt was thrown away with it.
What the architecture is really for
What encryption changes about what people write
The interesting effect is not on the attacker. People record different, more honest things when certain nobody else can read them.
Your software will not outlive your collection
A watch bought today may be read about in 2090. No application will still run. The record has to survive the tool that made it.
Where this started
Why this exists came before the section had a name: how a dive boat, an inherited Seamaster and a battered dive computer turned into an argument about which objects outlive their owners — and why that argument ruled out the cloud, the password reset and every other convenience that would have made the software easier to sell. The philosophy behind Watch Vault Archive sits beside it: the same reasoning turned toward how a collection is actually used, once it is safely on your own computer.
Four subjects that began as essays are in the library instead, because they have factual answers rather than positions: posting a collection online, how thieves identify collections, photographing watches and paperwork, and why cloud storage is not a backup.
The same contract as the library — useful whether or not you buy anything
Watch Vault Archive appears in these pieces wherever it genuinely solves part of the problem being discussed, because pretending otherwise would be its own kind of dishonesty. It appears alongside what it does not do, for the same reason. A tool described without its limits is being sold rather than explained.