Engagement Log — Page 17

🧭 Engagement classes

Every engagement is classified into one of two classes, and the classification is made from the requested surface alone.

🤖 Verified automation

A request for a machine-readable endpoint that a browser does not fetch on its own: /pricing.json, /llms.txt, or a certificate's JSON twin. Fetching one of these is treated as evidence of automation, because that is what it is.

Unclassified engagement

Every other recorded surface. The Registry does not know, and does not attempt to determine, what made the request — no user agent is read and no identifier is derived, so there is nothing to classify it with. Unclassified is the honest label, and it is applied by default.

In summary: one class is evidence, the other is the absence of evidence, and neither is a guess.

🔒 What a row can contain

The Surface column holds a normalised route pattern, not a raw request path. A certificate address is reduced to /c/{token} before it is stored, query strings are discarded entirely, and any path the Registry does not recognise is recorded as /other. A probed path therefore cannot inject text into this public log.