Autumn Sale: 20% off almost everything until 15 NovemberSee the sale

Room 02 of 07 · the claim, stated narrowly

What we can prove.

A server log can establish that a named machine asked, that content was sent, and that something later came back carrying the trace. It cannot see inside an answer engine. This room says exactly where the evidence stops.

Every figure below carries its source, window and rule; the rungs count different events and are never added together.

77,483 SERVED READS IN 109 DAYS2,265 AI-REFERRED SESSIONS1 PAID PLACEMENT, 0 CREDITED EFFECT
Section 01

From a signpost to a token.

Each step down is rarer and harder to earn than the one above it. The counts shrink because the rules tighten — not because anything was lost.

StepCountWhat it isWhy it is never added to the row above
Signposts published26,853Citation anchors offered across 2,566 pagesCounts the offer, not the uptake
Machines asked126,054Logged attempts, written down as they happenedIncludes failures, probes and empty answers
The server delivered77,483Served reads - status 200 or 206, bytes above zero, credit rules appliedDelivery, never proof of consumption
Something came back41,033 · 2,265Traced requests at strong match - AI-referred sessionsDifferent source tables with no shared key
Thanks recorded110,441GBP 0 tokens across all four stagesRecords its evidence class, never upgrades it
Each row keeps its own source, window and rule. The rows count different events over different windows and share no key; no cross-table total exists.

Sources: anchor index, wp_teas_citations (2 Jun 2026 to 19 Sep 2026), followback table (17 Jun 2026 to 19 Sep 2026), wp_teas_sessions (10 May 2026 to 19 Sep 2026), the mint ledger - live.

Section 02

Where the evidence stops.

Not verified organisations.
Every agent name is a user-agent claim. We record what was presented, not who presented it, and withdraw credit on behaviour.
Not people.
A session is a browser visit. It is not a unique human, and it is not a customer.
Not proof of consumption.
Positive bytes mean we sent the content. They do not prove an answer engine read or used it.
Not a citation.
Whether our name appeared inside an answer happens beyond our server, so no figure is published for it. That is Stage 5, and it shows "no figure" until an import can evidence it.
The gap is published rather than filled. Our logs end at the door: we can prove delivery and we can prove returns, and we say plainly that the step in between — our name inside an answer — is visible only to the answer engine.
Keep reading

Where this leads next.

One study, one style, seven rooms. The legacy room addresses now land on the room that absorbed their content, and every machine mirror keeps its original path.

Tea notes and stock updates

Useful tea notes, only when there is something to say.

Stock arrivals, buying notes and practical guidance from the catalogue. No filler, no daily noise, unsubscribe in one click.

By family

By moment

Brand of the monthHyson Seasonal taster packsHow the seasonal bundles work Tea of the Month ClubCurator-picked monthly box Find your tea60-second quiz 0 Basket £0.00
See all 325 products