The image is the proof

Look at a banknote in good light and tilt it. The fine, interwoven line-work that loops around the numbers is not decoration. It is a security device called guilloché, drawn by a machine called a rose engine, and it has been on currency, passports, and stock certificates for about two hundred years. It is hard to forge for a simple reason: it is one continuous line, milled with a precision a counterfeiter cannot reproduce by hand or by photocopy. The picture is the proof.

That idea is the whole reason the Field Guide looks the way it does.

We could have built a table

Most references to what runs on a computer look like spreadsheets. A filename, a status, a CVE number, a link. Useful, and forgettable, and built for people who already know what they are looking at.

The Field Guide is built for the gamer who does not, and who deserves a real answer anyway. So we made a different choice. Every inhabitant of the guide wears a generated mark, and the mark is made only from what the thing provably is. Same identity, same image, forever. Nobody draws them one at a time. The design is the algorithm, so it scales to a million entries with no new artwork, and not one of them can be faked, because faking the picture would mean faking the record it was drawn from.

There are three kinds of inhabitant in the guide, and each one wears a different mark, because each one is a different kind of thing.

A driver presses a seal

A kernel driver's whole story is the signature. Modern Windows loads a driver because a company Microsoft vouched for once signed it. That signature is the gate. The uncomfortable truth the Field Guide exists to explain is that the gate never checked whether the driver was good, only that it was signed, so a signed old build keeps loading for years after the world learns it is dangerous.

So a driver wears the oldest authentication device there is: a seal, pressed in wax. The vendor is the signet. Every MSI driver carries the same maker's mark, every ASUS driver its own, so kin look like kin at a glance. The seal is pressed from the driver's own record, and its verification fingerprint is milled into the rim, the same way a coin carries its serial. The status never changes the wax. A driver flagged on the public list is not a scarier object. It is the same family's seal, with a hairline crack across it: amber for vulnerable, red for the rare malicious one. We describe what the record says. We never recolor the thing into an accusation.

A game strikes a coin

A game is not a family. It is a single, singular thing, with a single decision attached to it: how much of your machine does it ask for? Some ask for nothing unusual. Some load a kernel driver at boot, before you have launched anything, and keep it resident as long as Windows is running.

So a game wears a singular artifact: a struck coin, the kind of mark people have always made when they needed something that could not be forged. The guilloché rosette at its center is the real anti-forgery device. The coin is struck from the game's verifiable record, its title, its publisher, its engine, its anti-cheat, its year, so the image is self-verifying. Change one fact and the whole figure re-strikes, down to the reeded edge. The mint mark at six o'clock reads the trust ask: a sealed, double-ringed core asks the most of your machine; an open one asks the least. We do not tell you whether that ask is acceptable. That is your call. The coin just makes it possible to make with your eyes open.

A process is mounted as a specimen

Drivers come from a public list. Games come from research. Processes come from life: the actual programs Vera observes running across real sessions, the launchers and anti-cheats and capture tools and quiet background services that make up a working gaming PC. That is the literal conceit of a field guide, so a process wears a naturalist's specimen card. The organism is seen through a lens, mounted on a labeled plate with corner registration ticks and a scale bar, with its fingerprint filed into the bar. Its body plan is its kind: an energetic many-armed star is a game, a connected lattice is a launcher or the anti-cheat that guards it, a quiet seed-head is the system substrate that recedes into the background. A process only ever appears after it has been seen on more than one machine, so nothing peculiar to a single person is ever published.

Metal, wax, life. Three kinds of inhabitant, three kinds of mark, one hand.

The guide now wears its own seal

There is a new thing on the front door, and it is the piece we are proudest of. The Field Guide now has a master seal of its own: a single large guilloché medallion, struck from the whole catalog's record. How many drivers are catalogued, how many carry written field notes, how many games and processes are curated, and the date the public list was last refreshed. All of it is milled into one figure, with the catalog's fingerprint around the rim like the inscription on a coin.

It means the front page is honest by construction. The seal is the census, made visible. As the guide grows, the seal re-strikes to match it. The reference that argues the picture should be the proof finally carries its own.

The half you do not see

The art is the half people notice. The other half is the writing, and it took longer.

Behind the marks are hundreds of curated entries, written one at a time. Every kernel driver on the public LOLDrivers list gets a page, four hundred and thirty-five of them, and more than two hundred carry field notes that explain in plain words which hardware the driver ships with, what its vulnerability actually allows, why the signed old build still loads after the vendor patched it, and which named public incidents documented its misuse. Dozens of games are written up the same way, sourced to each publisher's own anti-cheat documentation and to named reporting, never to an angry forum thread. The processes are described only from real signals, never invented specifics.

Two rules hold the whole thing together, and we did not bend them for coverage. Describe, never condemn: presence on a list is evidence on the public record, not a verdict about a person, and a true fact framed as an accusation is still a lie about someone. And ground truth or silence: where we cannot vouch for something, we say so plainly and point you to the canonical source, rather than dress a guess as a fact. A guide about honest records cannot cut corners on its own.

Who it is for

There is a real gap on the internet. The honest answers to "what is this thing on my computer, and should I care" live in dry security blogs, vendor PDFs, and academic papers written for people who already speak the language. The thoughtful gamer who just wants to understand their own machine was never the audience for any of it.

That gamer is the entire audience for this. We think the long-term answer to the trust crisis in competitive gaming is not a bigger shield bolted onto your system with no explanation. It is legibility: people who can actually see what is running on the computer they are sitting in front of, and have the words to ask their own questions. The Field Guide is one piece of that, and we made it beautiful on purpose, because the people who never get the reference made for them should get one that respects them.

Come wander it. Touch a seal and watch its family light up. Read why the driver reading your GPU temperature is on the same list as a tool used in real break-ins. The record is already there, drawn into every mark, waiting for you to look.

Open the Field Guide: veraproject.xyz/field-guide

The Vera Team