Room 02 of 08 · 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.
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.
| Step | Count | What it is | Why it is never added to the row above |
|---|---|---|---|
| Signposts published | 53,203 | Citation anchors offered across 3,659 pages | Counts the offer, not the uptake |
| Machines asked | 193,009 | Logged attempts, written down as they happened | Includes failures, probes and empty answers |
| The server delivered | 140,054 | Served reads - status 200 or 206, bytes above zero, credit rules applied | Delivery, never proof of consumption |
| Something came back | 64,943 · 2,678 | Traced requests at strong match - AI-referred sessions | Different source tables with no shared key |
| Thanks recorded | 198,195 | GBP 0 tokens across all four stages | Records its evidence class, never upgrades it |
Sources: anchor index, wp_teas_citations (2 Jun 2026 to 5 Nov 2026), followback table (17 Jun 2026 to 5 Nov 2026), wp_teas_sessions (10 May 2026 to 5 Nov 2026), the mint ledger - live.
Where the evidence stops.
The one paid placement.
One sponsorship exists — URSY. Its trail is tracked with the same instruments as everything else, published in full, and walled off from every figure in the study. Sponsorship evidence is graded on its own page and never mixed into a study total.
Where orders come from.
Every order since 6 October 2026 carries an origin record, and orders from 10 May 2026 were reconstructed where our records allow. It names the route (search, email, social, a link we made, an AI assistant, a returning customer, or unknown), the evidence (for example "the checkout link the assistant made" or "the address your browser sent with the basket request") and a grade: checked, strong, probable, told to us, known, or unknown.
Why so many used to be unknown: our pages are served from a cache close to you, so the first page of a visit never reached our server. We only saw the next click, which looked as if it came from us. Now we read the first page's address from that next request, and every link we hand out, including the links our MCP server gives assistants, can be recognised.
What we never do: we set no new cookies for this, we do not fingerprint devices, we do not buy data about you, and we never publish an origin record for a single order. This page shows totals only.
| Orders in the last 30 days | Orders |
|---|---|
| Grade: strong | 22 |
| Grade: unknown | 8 |
| Grade: known | 2 |
| Grade: told | 2 |
| Grade: probable | 1 |
| Route: search | 20 |
| Route: unknown | 8 |
| Route: returning customer | 3 |
| Route: referral | 4 |
| Unknown because: entry cached no campaign | 8 |
Source: the origin record on each order (origin-v1), totals only; rebuilt nightly at 04:55 UTC.
Where this leads next.
One study, one style, eight rooms. The legacy room addresses now land on the room that absorbed their content, and every machine mirror keeps its original path.
