Engagement Log — Page 31

The Agentic Foresight Registry maintains a public log of engagement activity: every recorded engagement, newest first, with the surface it touched and the hour it occurred in. Assessments from EUR 1.90.

A row records an event, never a visitor. It's important to note that no IP address, no user agent, no cookie, no browser storage, and no fingerprint is collected, stored, or derived — for a human visitor and an autonomous agent alike. There is nothing in this table that could be joined back to anyone, because there is nothing in this table to join.

We call this the unattributed record: a log that is complete about events and silent about actors, by construction rather than by policy. It cannot be de-anonymised later, because there is no anonymisation step to reverse — the identifying data was never collected in the first place.

🕐 Timestamps are recorded at hour precision.

Showing 1501–1508 of 1508 recorded engagements.

Engagement No. Recorded Class Surface
ENG-0011 test 2026-08-21 09:00 UTC Unclassified engagement /c/{token}
ENG-0010 test 2026-08-21 09:00 UTC Unclassified engagement /c/{token}
ENG-0009 test 2026-08-21 09:00 UTC Unclassified engagement /
ENG-0008 test 2026-08-21 09:00 UTC 🤖 Verified automation /c/{token}.json
ENG-0007 test 2026-08-21 09:00 UTC Unclassified engagement /c/{token}
ENG-0006 test 2026-08-21 09:00 UTC Unclassified engagement /order/complete
ENG-0005 test 2026-08-21 09:00 UTC Unclassified engagement /order
ENG-0004 test 2026-08-21 09:00 UTC Unclassified engagement /

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.