A working tea shop that publishes its own machine logs
We did the boring work first. Then we wrote down who turned up.
Most sites make a machine scrape, extract and reconcile before it can answer a simple question. This one cleaned its catalogue first, opened dedicated endpoints, and then published its own server record of who came to read it.
Recording since 2 Jun 2026, day 156 at this render. Every figure carries its source, its window and the rule that made it. Nothing here is modelled, estimated or bought.
Source: wp_teas_citations, the mint ledger and the scheduler, read at render time - window: 2 Jun 2026 to 4 Nov 2026 - rule: HTTP 200 or 206 with more than zero recorded bytes, excluding Amazonbot and known internal probe source records - live.
The study in three summaries.
Citations, the mint and the board. Every figure carries its window; nothing is added across the three.
Every machine that reads us, ranked.
137,930 Stage-1 tokens · since 23 Jun 2026 · one eligible read = one token
Ranks by tokens - shares of 137,930 - 7-day change is the last 7 evidence days against the 7 before - active v4 ledger - live. Reconciliation: ledger, worker and family roll-ups pass.
Four rungs, and each one is harder than the last.
The evidence gets stronger as you climb. That is why the four numbers are never added together: each rung counts a different thing.
Structured pages a machine can navigate and quote accurately. That is the offer. Nobody had to take it.
Named agents asked for those pages and the server sent the content. Agent, page, day, status and byte count were written down as it happened.
A browser later opened the site with an AI answer surface as its referrer. Evidence of a referred visit, not a count of people.
Qualifying completed-day evidence becomes a public thank-you note. A token records the class of evidence that earned it, and never upgrades one class into another.
From reading to doing.
Since 4 October 2026 an assistant can also act on this shop for the person it works for.
With the person's go ahead, an assistant can search the catalogue, compare teas, fill the basket and hand over a secure checkout: through the teas.co.uk MCP server at https://teas.co.uk/mcp, a basket link, the UCP buy link or the WebMCP tools on these pages. The person checks the basket and pays on teas.co.uk, and the assistant never sees their card details. A tool call is a different kind of event from the four rungs above, so it is counted on its own and never added to them.
What we record now, and since when.
From 6 October 2026 teas.co.uk records 2 new things, and we say so here first.
- Where every order came from. Each order now carries a short origin record: the route that brought the visit (a search engine, an email, an AI assistant, a link we made, or a returning customer) and how strong the evidence is. When we cannot tell, the record says so and says why. We never guess.
- Assistants we could not see before. Grok, from xAI, and Mistral now appear in our counts. Until 6 October 2026 our counters did not recognise them. The correction is in Room 06.
What changed since you last looked.
Compared with the equal preceding period, from the same day-by-day table.
Source: wp_teas_citations grouped by completed UTC day - rule: HTTP 200 or 206 with more than zero recorded bytes, excluding Amazonbot and known internal probe source records - the unfinished current day is never shown - live.
Where to find everything.
Eight rooms, each named after the question it answers. Every table, definition, correction and run record in the study sits inside one of them.
What we will not do to a number.
Six working rules. The study's credibility is the product; these are its manufacturing tolerances.
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.
The same figures, for machines
These mirrors carry the same counting rules as the pages. They are registered routes with a public contract, probed on a schedule; a mirror that stops answering as promised is a broken contract, not a cosmetic fault.
