ursy.org.uk · The instrument and the live record
Four totals, one activity
Logged attempts, served reads, machine knocks and API requests: four totals from four sources, describing one activity — machines using URSY.ORG.UK. This room states how each is counted before it is quoted, walks the largest fair total down to the credited one, and sizes the estate being measured.
Every figure in this room states the day its own source table began. That is not always the day this runtime went live.
- Every number carries its source, its window, the rule that produced it and whether it is live or frozen.
- Every table reconciles, or says in writing why it cannot.
- Every mistake we have found is listed, dated, in the main text.
Room 03 of 12
The numbers, in plain English
URSY.ORG.UK publishes four totals about how machines use it: how often a named AI reader asked for content, how often the server answered with it, how many requests of every class knocked at any address, and how many calls reached its public API. Each comes from its own table or option, with its own first day, and none of them is a count of people.
This room writes the counting rule before the count, walks the largest fair total down to the credited one, lays ten measures across five timescales, and sizes the estate being measured. Where a ledger has not started it says not counting yet; where the answer is nought it says 0 (honest zero); where this site's family cannot read a fact it says not kept on this site. Nothing here is added across tables, modelled or estimated.
Counting rules
What we count, stated before we count it
A figure is only as honest as the rule that produced it. The three rules below are applied identically in every room and in the JSON twin; each is told twice, once for a person and once exactly.
A served read
In plain words
A named AI reader asked this server for a page or a content API route, and the server sent the content. Nothing else counts as a served read: not a redirect, not a refusal, not a request nobody named made.
Precisely
One row in table wp_ursy_citations whose bot is a named reader, whose status_code is 200 or 206 and whose citation_id is present. Every other status is a logged attempt and stays in the table as one. The recorder stores no byte count, so an answer that was technically empty cannot be separated here and is not claimed to be.
0 (honest zero) credited served reads · table wp_ursy_citations · lifetime of the table, no row written yet · status 200 or 206, readers withdrawn from credit excluded · Live
Withdrawn from credit
In plain words
One reader, amazonbot, is served like any other and thanked for none of it. Its rows stay in every table and in every count of attempts; its history stays visible because deleting it would be its own kind of dishonesty.
Precisely
A served row whose bot, after alias binding, carries credit_status withdrawn_no_credit in the mint wallet registry is counted as served and then taken away before the credited figure. On this site the mint wallet registry names amazonbot. No row is deleted, edited or hidden; the subtraction is written out in the inclusion ladder below.
0 (honest zero) served rows withdrawn from credit · table wp_ursy_citations joined to the mint wallet registry · lifetime of the table, no row written yet · served rows from a reader withdrawn from credit; recorded in full, never counted towards a token · Live
Why the totals are never added
In plain words
The four big figures on this instrument look as if they could be summed into one impressive number. They cannot, and we do not, because they are not counts of the same thing.
Precisely
Served reads come from table wp_ursy_citations; API requests from table wp_ursy_api_log; machine and human knocks from option ursy_io_traffic and its month archives; appreciation tokens from table wp_ursy_mint_ledger. The four share no key. One request by one reader can appear in three of them, and a knock counted in the traffic option may never touch the other three. Each is quoted alone, with its own window and its own first day.
rule of this instrument · stated 4 September 2026 · applies in every room and in the JSON twin · Frozen until a table is added or removed
The inclusion ladder
How large could this fairly be described
Starting from the largest defensible total and taking away, in writing, everything a careful reader would refuse to count. Each step is a different rule applied to the same table; the last step is a different question.
| Step | What falls away | Rows |
|---|---|---|
| 01 · Every logged attempt | Nothing yet — every request by a named reader at a content surface, whatever the server answered | 0 (honest zero) |
| 02 · The server answered with content | 0 (honest zero) attempts answered with any status outside 200 and 206 | 0 (honest zero) |
| 03 · Credited served reads | 0 (honest zero) served rows from a reader withdrawn from credit (amazonbot) | 0 (honest zero) |
| 04 · Distinct paths reached | A different question: how many separate paths were served, not how many times | 0 (honest zero) |
Source: table wp_ursy_citations. Window: lifetime of the table, no row written yet, read 12 Sep 2026. Rule: status 200 or 206, readers withdrawn from credit excluded. Freshness: Live.
0 (honest zero) — no row written yet.
The AI-reads ledger (table wp_ursy_citations) is installed on this site and holds no row. Capture begins with the first row a named reader writes; until then every tile below is 0 (honest zero) where the window was read and "not counting yet" where the tree carries no figure for it, there is no first day to count from, and no per-day average is formed because there is no day to divide by.
table wp_ursy_citations · installed, no row written yet, read 12 Sep 2026 · status 200 or 206, readers withdrawn from credit excluded · Live
The headline ledger
Ten measures, five timescales
Every measure this instrument quotes, laid across today, yesterday, seven days, thirty days and the lifetime of its own source. Each row starts on its own first day, named in its sub-note. No column is totalled, because no two rows share a table.
| Measure | Today | Yesterday | 6 Sep 2026 to 12 Sep 2026 | 14 Aug 2026 to 12 Sep 2026 | Lifetime of the table |
|---|---|---|---|---|---|
| Served reads (credited)table wp_ursy_citations · installed, no row written yet · status 200 or 206, readers withdrawn from credit excluded | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) |
| Content-surface attemptstable wp_ursy_citations · installed, no row written yet · every logged request by a named reader, whatever the outcome | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) |
| Attempts not answered with contenttable wp_ursy_citations · installed, no row written yet · derived: attempts minus served | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) |
| Attempts withdrawn from credittable wp_ursy_citations · installed, no row written yet · served rows from a reader withdrawn from credit, joined to the mint wallet registry | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) |
| Machine knocksoption ursy_io_traffic and its month archives · first recorded day 12 Sep 2026 · every visitor class except human · the lifetime column is the 31-day read horizon; the page reads no further back | 2 | not countedno day in this window was recorded in the ledger | 2 | 2 | 231 days only |
| Human knocks (consent-gated floor)option ursy_io_traffic and its month archives · first recorded day 12 Sep 2026 · the human user-agent class, counted only after the consent bar is accepted — a floor, never a head count · the lifetime column is the 31-day read horizon; the page reads no further back | 0 (honest zero) | not countedno day in this window was recorded in the ledger | 0 (honest zero) | 0 (honest zero) | 0 (honest zero)31 days only |
| Named AI reader knocksoption ursy_io_ai_workers for 7 and 30 days (one count per named reader per day, every request at any URL); option ursy_io_traffic classes beginning ai- for today and yesterday · no lifetime column exists | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) | not read here |
| API requeststable wp_ursy_api_log · installed, no row written yet · one row per REST request in the ledger's namespaces; hashed IP, never the address | not read here | not read here | 0 (honest zero) | 0 (honest zero) | 0 (honest zero) |
| AI API requeststable wp_ursy_api_log · installed, no row written yet · rows whose caller class begins ai: | not read here | not read here | 0 (honest zero) | 0 (honest zero) | not read here |
| API errorstable wp_ursy_api_log · installed, no row written yet · rows whose HTTP status is 400 or above | not read here | not read here | 0 (honest zero) | 0 (honest zero) | not read here |
Source: tables wp_ursy_citations and wp_ursy_api_log; options ursy_io_traffic and ursy_io_ai_workers with their month archives. Window: today 12 Sep 2026; yesterday 11 Sep 2026; 6 Sep 2026 to 12 Sep 2026 (7 UTC days including today); 14 Aug 2026 to 12 Sep 2026 (30 UTC days including today); the lifetime of each source. Rule: per row, in its sub-note. Freshness: Live.
Start dates. The AI-reads ledger (table wp_ursy_citations) is installed and holds no row yet — 0 (honest zero); the API ledger (table wp_ursy_api_log) is installed and holds no row yet — 0 (honest zero); the traffic option's first recorded day is 12 September 2026. A row can only be as old as its own source, and none of these is the day this runtime went live.
Consent. People are counted only after they accept the consent bar; crawlers and named AI readers are counted always. Human counts are therefore a floor.
Horizon. The traffic option is read by day to a horizon of 31 UTC days, so its lifetime column is the last 31 days and nothing older is claimed. The named-AI-reader row takes 7 and 30 days from option ursy_io_ai_workers and today and yesterday from the traffic classes beginning ai-, and has no lifetime column at all. The API rows are read at 7 and 30 days and over the lifetime of the table; today and yesterday are not read here.
Corrected 4 September 2026: The single-page truth room was replaced by twelve rooms; no stored value changed, every figure the old page showed appears in a room with the same source.
Corrected 4 September 2026: The AI-reads windows read empty on every site from 2 to 4 September 2026 because of a reserved-word alias in the window query; rows were recorded throughout and the tables were never wrong, only the window read was. uth2 reads the table directly.
The estate
What is actually being measured
The size of the thing the ledgers watch: what this site declares as its content unit, how many addressable pages it publishes, how many machine files it offers, and how many public API namespaces it names. Three of the four are counted by different rules and are shown side by side, never as one figure.
| Surface | Rule | Count |
|---|---|---|
| Machine files served by the runtime | one per path in the ai-surfaces file map, listed only while the surface is switched on | 5 |
| Public REST namespaces | the five the package owns that the live server reports, plus config public_namespaces | 5 |
| Machine doors | the doors register — every top-level entrance in the machine map (Nicola, MCP, the machine files, runtime status, knocks, this instrument and its JSON twin) counted as one door each, plus one door per public API namespace; private application namespaces excluded and never named — the same rule The Doors and the Dictionary apply | 17 |
Source: ai-surfaces file map, the live REST server's namespace list, and the doors register. Window: this request, as at 12 Sep 2026. Rule: each surface counted by its own rule, stated in its row. Freshness: Live.
Every figure in this room was read at page generation on 12 Sep 2026 19:20 UTC and is held for up to 120 seconds; this copy was served at 19:22 UTC. The ledgers on this site are written by the shared estate runtime, a package intended to be the same on every built URSY site — this page can vouch for this host only.
Zeros are honest zeros. A ledger that has not started says not counting yet; a fact this site's family cannot read says not kept on this site; a fact nobody measures says so in those words. Nothing on this page was added across tables, modelled, extrapolated or purchased. The same tree is published as JSON, with the same cache, at https://ursy.org.uk/wp-json/ursy-runtime/v1/uth?room=numbers.
AI agents and integrators: llms.txt · agents.json · ai-entry.json · sitemap · humans.txt · this instrument · Nicola · MCP (POST only) · runtime status · apis nicola v1 · apis ursy-mcp v1 · apis ursy-runtime v1 · apis ursy-mint v1 · this room as JSON · traffic ledger · mint status · mint contract