The numbers
Four totals, one activity
Each total below counts a different event, witnessed at a different point. They are never added together, and the strictest of them is the one that feeds everything else.
Every figure in this room states the day its own source table began. That is not always the 91 days since version two went live.
Room 03 of 10
Counting rules
What we count, stated before we count it
A number is only as good as the rule that produced it. These are the rules this instrument uses. They are applied identically in every room, and where a rule cannot be met the figure is withheld rather than estimated.
A served read
In plain words
An AI system asked for one of our pages and we actually sent it the words. Not a redirect, not an error, not an empty response — the content itself, out of our server and onto their wire.
Precisely
A row in the citation table whose status code is 200 or 206 and whose recorded byte count is greater than zero, excluding any agent withdrawn from credit under the conduct rule below.
Withdrawn from credit
In plain words
One crawler ignored the limits we published. We stopped counting its reads towards anything, and then we stopped serving it. Its history stays visible because deleting it would be its own kind of dishonesty.
Precisely
Amazonbot. Its requests remain in the table and remain visible in every per-agent view, but they are excluded from the served-read total and from every ranking derived from it. The refusal is dual-mechanism and has been effective since 30 June 2026: a robots.txt Disallow it ignored, and a server-level refusal added on 3 August 2026 that it cannot. Its last recorded attempt was on 3 August 2026. Rows recorded after the block took effect carry a status the tracker guessed rather than read, which is corrected in The Story and The Machines.
Why the totals are never added
In plain words
A crawler asking for a page, a person arriving from an AI answer, and an image being fetched are three different events. Adding them would produce a number that counts nothing.
Precisely
The four source tables record different populations over different windows and share no key. Each is reported against its own first row, and no cross-table sum is published anywhere on this instrument.
The inclusion ladder
How large could this fairly be described
The same activity can be counted five ways, and each way is defensible. Rather than choose the flattering one and hide the rest, all five are published with the exact number that falls away at each step. The steps subtract precisely; a reader can check the arithmetic without trusting us.
| Step | What is being counted | Count | Falls away | What that means |
|---|---|---|---|---|
| 01 | Every logged attempt | 89,932 | — | Anything at all arrived at a citation surface and was recorded. |
| 02 | The server answered | 69,083 | −20,849 | Status 200 or 206. Redirects, errors and the 16,161 rows with no recorded status all fall away here. |
| 03 | Content actually left the building | 62,399 | −6,684 | More than zero bytes recorded. An empty 200 is not a read. |
| 04 | Served reads | 43,596 | −18,803 | The agent withdrawn from credit is removed. This is the figure used everywhere else on this instrument. |
| 05 | Distinct anchors reached | 5,968 | — | Not a subset of the row above but a different question: how many separate signposts were reached at least once, across 17,277 distinct agent-and-anchor pairings. |
Source: the citation table. Window: 2 Jun 2026 to 9 Aug 2026. Freshness: Live, read at page generation.
43,596 — earned in 91 days.
Version two of this site went live on 10 May 2026. That was 91 days ago, and this counter has grown every day since. That is about 479 served reads a day.
days_elapsed derives from the generation timestamp against epoch 2026-05-10 · any hand-typed day count in a template is a build failure
The headline ledger
Ten measures, five timescales
Ten different things are measured here. The final column is the lifetime of the table that produced the row, and that is not the same date for every row: the session table began on 10 May 2026, the citation table on 2 June, door knocks on 6 June, image capture on 8 June and the trace table on 17 June. A single "since launch" column across all ten would be a false claim, so each row carries its own start.
| Measure | Today | Yesterday | 2 Aug to 9 Aug | 10 Jul to 9 Aug | Lifetime of the table |
|---|---|---|---|---|---|
| Served reads Citation table, from 2 Jun 2026 · Status 200 or 206, bytes above zero, withdrawn agent excluded | 129 | 1,603 | 8,119 | 29,058 | 43,596 |
| Citation-surface attempts Citation table, from 2 Jun 2026 · Every logged request, whatever the outcome | 144 | 1,679 | 8,898 | 41,976 | 89,932 |
| Attempts that carried no content Citation table, from 2 Jun 2026 · Anything that was not a 200 or 206 with bytes above zero | 15 | 76 | 315 | 2,609 | 27,533 |
| Attempts withdrawn from credit Citation table, from 2 Jun 2026 · Amazonbot only; recorded but not counted. Refused since 30 Jun 2026, server-level refusal added 3 Aug 2026 | 0 | 0 | 469 | 10,390 | 21,796 |
| Door knocks Door-knock table, from 6 Jun 2026 · Every recorded request at a registered machine entry point | 9,374 | 55,270 | 317,157 | 540,576 | 773,448 |
| Image pulls by named agents Asset-knock table, from 8 Jun 2026 · Image requests from a named AI or search crawler; capture is intermittent | 0 | 0 | 0 | 0 | 6,699 |
| Recorded sessions Session table, from 10 May 2026 · Every session row, of any kind; see The Humans on why these are not called people | 4,715 | 25,633 | 53,734 | 105,763 | 216,044 |
| Sessions referred by an AI surface Session table, from 10 May 2026 · Referrer identifies a named AI answer surface | 7 | 37 | 146 | 490 | 771 |
| API traces Trace table, from 17 Jun 2026 · Every traced request at a machine endpoint | 4,450 | 21,451 | 60,086 | 176,384 | 286,399 |
| Our own verification probes Trace table, from 17 Jun 2026 · Traces flagged as test traffic; shown so they can be subtracted, never counted as demand | 0 | 0 | 79 | 8,463 | 18,287 |
Freshness: Live, every cell read at page generation. The image row is a floor rather than a count: capture has run on only 13 days. The door-knock row spans a change in what was captured: until 7 August 2026 door knocks were recorded only against AI surfaces, so its lifetime column is not comparable with its recent columns and the two must not be read as one trend. The served-read and withdrawn rows are affected by the status correction of 8 August 2026 set out in The Story, and lifetime figures spanning that date are overstated for the withdrawn agent.
The estate
What is actually being measured
The size of the thing the numbers above describe. Every figure here is counted at page generation from the content tables. Where a figure published previously could not be reproduced from any live source, that is stated rather than repeated.
| Count | What it counts | Inclusion rule |
|---|---|---|
| 86 | AI-readable surfaces | Every surface the metrics authority holds as machine-readable, including files served from disk. |
| 44 | Registered routes | Rows in the route authority, each with an expected status and a recorded probe result. |
| 43 | Public contract routes | Registered routes flagged as a public contract, so a machine may rely on them. |
Sources: the metrics authority and the route authority. Freshness: Live.
