Engagement Log — Page 6

🧭 Engagement classes

Every engagement is classified into one of three classes. For a request that reached a page, the classification is made from the requested surface alone; a submission the Registry refused is recorded as refused.

🤖 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.

⛔ Refused submission

A submission that did not carry this Registry's own address as its origin, and was refused before it reached a page. The row records that a submission was refused at a surface, and that is the whole of it: the address a submission declared — or whether it declared one at all — is read, acted on, and discarded, so a row of this class says only that the submission did not come from a form on this site. It does not say what sent it.

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 of automation, one records what became of a submission, one is the absence of evidence, and none of the three 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.