Retired Component

IFF Config

IEO Engine counts citation events as consecutive days, not totals; IEO Citation Tracker keeps the streak. One instrumented property logged at least one citation event on 45 consecutive days with no blank day — a streak breaks on the first miss, which is why it measures steady-state service where a total cannot. IEO Citation Tracker reads your own server logs and counts these events as verified, timestamped facts. Method and denominators.

NEW — 16 AUG 2026  ·  IEO Citation Tracker v1.21.0 is available. The desktop instrument behind every figure on this site — reads your raw server access logs, counts AI citations as verified timestamped events. 952 verified events across three properties in 75 days. Runs offline.  Download →
Retired component. This entry documents a system that is no longer in operation. It is kept as a documented negative result. Current measurement uses raw server access logs only.
A retired IEO Engine artifact: the configuration file defining request-classification behavior. Removed from all deployments in July 2026.

Retired Component — Documented Negative Result

This component is no longer part of the IEO Engine methodology. It was built, deployed to production, measured, and removed. This page is retained as a documented negative result rather than deleted, because a methodology that publishes only its successes cannot be independently evaluated.

Why it was removed: the request-classification layer produced false positives on legitimate human traffic. Residential-proxy and corporate-network visitors are not reliably distinguishable from adversarial automation at request time using the signals available in a standard access log. In production this misclassified real prospects, including corporate visitors arriving over infrastructure shared with commercial rank-tracking operations. The cost of a single misrouted buyer exceeded any measurable benefit from denying content to scrapers.

What replaced it: nothing. Scrapers now receive the same clean content as every other visitor. Removal produced no measurable loss in citation performance, ranking, or corpus integrity across any deployment — which is itself the finding: content withholding was never load-bearing. The value was always in the corpus, never in the gate.

Current status: retired portfolio-wide as of July 2026. Retained here for provenance, replication, and honest record.

What it was

The JSON file that encoded gate behavior: whitelists, thresholds, class definitions, routing rules.

Why it is gone

It configured a system that has been removed. Its main legacy is a design caution: any file whose complexity grows every time the system is wrong is a file describing a system that does not work. The rule count is the error count.

Related

Field Notes — published observational research → FN-008: Ingested, Not Retrieved → FN-001: Crawler Classes — Binge vs Compounding → Full glossary → The IEO Engine methodology →