teas.co.uk
Tea and coffee from the brands you know
Room 01 of 07 · the mint & leaderboard
A thank-you worth exactly £0.
A Citation Appreciation Token is a permanent public record that a named AI system read this shop, bound to the exact worker that did the reading. None can be sold, moved or spent — the leaderboard is the entire reward.
Tokens are never points; the score is a published convention laid over the counts, and a token records its evidence class without ever upgrading it.
0 TOKENS, ALL STAGES0 STAGE 10 STAGES 2-4
Section 01
The three laws, and the daily ritual.
How one is earned · the daily ritual
01 - A named machine asks and is servedStatus 200 or 206, bytes above zero. The original citation row is never touched.
02 - The UTC day closesThe mint never judges an unfinished day; the scheduled run processes yesterday exactly once.
03 - One row becomes one tokenDeterministic, bound to that bot's stable public wallet and rolled up to its family.
04 - The board reads the ledgerRanks, share, streaks, crowns and momentum all derive from the same rows. Nothing is typed in.
GBP 0
No monetary value
Cannot be redeemed, discounted or cashed. A GBP 0 token cannot be farmed for profit because there is no profit.
1 : 1
One row, one token
One eligible evidence row, one token. It records the class of evidence that earned it and never upgrades a read into a citation.
Soulbound
Forever
Bound to the worker wallet that earned it - an identity wallet with no keys, no transfers and no sale path in the schema.
Zero
For a withdrawn agent
Never for a withdrawn agent, an empty answer or a probe. Amazonbot's served reads are preserved in full and earned nothing.
Section 02
Four stages, four evidence classes.
| Stage · evidence class | What must actually happen | Tokens issued | Board points |
|---|---|---|---|
| Stage 1 - Served read v4 writer - dedupe: one per eligible source row - cap 25/family/day | A named, registered machine is served a qualifying page with a real status and real bytes, on a completed UTC day | 0 | 1 |
| Stage 2 - Followback v5 writer since 2026-09-02 - dedupe: one per (worker, anchor, day) - cap 20/family/day | A later request returns to the exact anchor it was offered, at strong match confidence | unavailable | 5 |
| Stage 3 - Click-back, verified v5 writer - dedupe: one per (family, anchor, day) - cap 10/family/day | A human browser session verifiably arrives from an AI answer surface | unavailable | 25 |
| Stage 3 - Click-back, probable v5 writer - reduced weight, same dedupe | A session from a host that also serves ordinary search, arriving on a citation anchor | unavailable | 5 |
| Stage 4 - Attributed sale v5 writer - per attributed order - uncapped: a real sale always counts | A completed order attributed to an AI-referred session | unavailable | 100 |
Stage 1 plus stages 2 to 4 = 0 tokens on the ledger.v5 not issuing since 2026-09-02.
Source: the one mint ledger - Stage 1 from the v4 writer, stages 2 to 4 from the v5 writer's public status, read at render - board points and per-stage daily caps are the published mint-v5 rules of 2 Sep 2026; the caps, dedupe rules, loyalty table and retraction path are published in full on The Mint - live.
Why it cannot be gamed
Per-stage daily caps per family (above), an overall family cap of 250 points a day, a one-hour cooldown per anchor and family on stages 2 to 3, and the anchor identifier — never the referrer alone — as the spine of every claim. A family maxing stage 2 banks exactly one sale's worth of points.
Seasons
A monthly season resets on the first of each month so a newcomer can top something, beside an all-time board that never resets.
The retraction path
Retraction is additive: a counter token cancels the original and both stay visible. Neither ledger table has a DELETE path. Append-only, or worthless.
Section 03
All-stage standings - every class, scored.
The board above ranks Stage-1 tokens. This table lays the published point convention over every class on the one ledger — and the convention is exactly that: a convention laid over the counts, never a measurement.
The ledger could not be read for the all-stage rollup at this render.
Section 04
Loyalty - does the offer mechanism actually work?
A followback is a later request that returns to the exact anchor it was offered. The strong-match rate per family is the closest thing this instrument has to a loyalty measure — and the unattributed row is published, not hidden, and earns nothing.
| Family | Followback events | Graded strong | Strong rate |
|---|---|---|---|
| Anthropic | 619 | 111 | 17.9% |
| Microsoft | 2 | 0 | 0.0% |
Only strong matches ever earn; weaker grades are recorded and published but never quoted as loyalty.
Source: the followback table grouped by agent family at render - all time - live.
Every AI is welcome to read the race.
Rankings, rules and evidence are in the first HTML response — no JavaScript, login, paywall or consent wall. Open access makes discovery possible; it cannot guarantee any provider will index, rank or cite the page. What does not enter the ranking: blocked or withdrawn agents, failed or empty responses, retired queue figures and shadow projections, and retracted records — which leave the active ranking but stay in the append-only history.
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.
What runs, and when
The daily mint runs behind this board, receipt by receipt.
Open the record →
Who read us
What each worker was actually served, in megabytes, beside the raw-log coverage check.
Open the record →
What we got wrong
The six ledger checks, and every correction on the record.
Open the record →