ursy.recipes · The story, and the line it cannot see across
What a citation actually is
A citation, as people use the word, is our name inside an answer. What this server can see is smaller and firmer: a named AI reader asked for a page or a content route, and the server sent it. This room keeps the two apart — the delivery URSY.RECIPES can prove, the use it cannot — and says which side of that line every figure sits on.
Across 1 UTC calendar days the measurable served-read side averaged about 45 a day.
- 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 02 of 12
In plain English
When a machine reads a page on URSY.RECIPES, this server sees exactly one thing: a request arrived from a named AI reader, and the server answered it with content or did not. That row — the served read — is the whole of what this site can prove about delivery. Since 12 September 2026 it has recorded 45 credited served reads out of 48 logged attempts.
table wp_ursy_citations · lifetime of the table, first row 12 Sep 2026 14:49 UTC · status 200 or 206, readers withdrawn from credit excluded · Live
What the server cannot see is the other half of the word: whether URSY.RECIPES was then named inside an answer, and whether a person followed that name back here. Nothing on this instrument infers either from its own logs. This room walks the measurable side from a signpost to a token, marks the line where measurement stops, fixes one meaning to each word it uses, and lists the corrections we have published.
no source · as at 12 Sep 2026 · answer use and return visits are not observable from this server and are not inferred · Frozen until an independent witness is imported
The two ladders
Two questions that sound the same and are not
"Did they take it?" and "Did it bring anyone back?" are answered from different places. The first is a row in a table on this server. The second would need a referrer this site does not record. Ladder one is counted below; ladder two is named and left honestly empty.
Ladder one — what they took (served reads)
In plain words
A named AI reader asked this server for a page or a content API route, and the server sent it. Each such answer is one served read. It is evidence that material was delivered; it is not evidence that the material was used.
Precisely
Rows in table wp_ursy_citations with status 200 or 206, readers withdrawn from credit excluded: 45 credited served reads since the table's first row on 12 September 2026; 45 from 14 August 2026 to 12 September 2026 (30 UTC days including today); 45 in the last 7 days from 6 September 2026. 0 (honest zero) served rows from the reader withdrawn from credit (amazonbot) are recorded in full and not credited.
table wp_ursy_citations · lifetime of the table, first row 12 Sep 2026 14:49 UTC · status 200 or 206, readers withdrawn from credit excluded · Live
Ladder two — what came back (AI-referred sessions)
In plain words
A person reads an AI answer that mentions this site and comes here. That arrival is what the second ladder would count, if it could be seen.
Precisely
not counting yet. This site records no referrer and keeps no session table, so a browser arriving from an AI answer cannot be told from any other visitor here. No figure is shown because none is measured. The runtime would need a referrer-class column in its traffic ledger before this ladder could carry a number; when it does, the number will start at 0 (honest zero) on that day and this sentence will be revised, dated.
no source · as at 12 Sep 2026 · no ledger on this site stores a referrer; the traffic ledger keeps only the class of the user-agent, the API ledger a salted hash of the address · Frozen until a referrer class exists in the traffic ledger
The evidence ladder
From a signpost to a token
Five steps, five sources, five windows. Each row is read from its own table and none is added to the one above it; the ladder is a sequence, not a sum, and it stops at the last thing this server can see.
| Step | What it means | Figure | Window | Source |
|---|---|---|---|---|
| 01 · The signposts we put up | What we offered: published pages and posts, and the machine files that tell a reader where they are. This counts what was put up, not what anyone took. | 50 (honest zero) pages and posts + 5 machine files | as at 12 Sep 2026 | table wp_posts and the ai-surfaces file map |
| 02 · Requests at a content surface | Every logged request by a named AI reader at a page or a REST content route, whatever the server answered. | 48 | lifetime of the table, first row 12 Sep 2026 14:49 UTC | table wp_ursy_citations |
| 03 · The material actually reached them | Requests the server answered with content — status 200 or 206 — from readers not withdrawn from credit. The served read. | 45 | lifetime of the table, first row 12 Sep 2026 14:49 UTC | table wp_ursy_citations, status 200 or 206, withdrawn excluded |
| 04 · A machine came back through a door | A named AI caller used one of the machine doors — Nicola, MCP or a public API namespace. A different table, a shorter window. | 29 | 14 Aug 2026 to 12 Sep 2026 (30 UTC days including today) — 30 days | table wp_ursy_api_log, caller class beginning ai: |
| 05 · An appreciation token was issued | One served-read row on a completed UTC day earned a named reader one £0 soulbound thank-you on this site's mint ledger. | 0 (honest zero) | all time | table wp_ursy_mint_ledger, through the mint's handshake block |
Source: table wp_posts and the ai-surfaces file map (row 01); table wp_ursy_citations (rows 02 and 03); table wp_ursy_api_log (row 04); table wp_ursy_mint_ledger through the mint's handshake block (row 05). Window: as at 12 Sep 2026 for row 01; lifetime of the table, first row 12 Sep 2026 14:49 UTC for rows 02 and 03; 14 Aug 2026 to 12 Sep 2026 (30 UTC days including today) for row 04; all time for row 05. Rule: each row is read from its own table under its own rule and none is added to another; an absent ledger prints its absence words, never a zero. Freshness: Live.
The gap
Where the evidence stops
Every row above sits on this server. The thing people mean by "citation" — our name inside an answer — happens somewhere else, and no log this site keeps can reach it.
What we cannot see
Between a machine reading our words and our name appearing inside an answer, there is a space no website can see into.
Every figure on this instrument sits on one side of that line.
Engine-observed citations — whether an answer engine named URSY.RECIPES, and how often — belong to somebody else's telemetry. This instrument has imported none, and it never infers a citation count from its own logs: a served read is evidence that material was delivered, not that it was used.
If an outside measure is ever imported, it will appear in its own section with its own provenance, labelled as a witness, and it will never be added to any figure on this side of the line.
no source · as at 12 Sep 2026 · nothing observed outside this server is imported and nothing about answer use is inferred from inside it · Frozen until an independent witness is imported
What the words mean
One word, one meaning
Nine words this room leans on, each with the one thing it means here and the one thing it does not. The Dictionary carries every term; these nine are read from the same list, so the two rooms cannot drift.
| Term | Means | Does not mean | Rule and source |
|---|---|---|---|
| Logged attempt | One row in the citations ledger: a named AI reader asked for a page or a content API route, whatever the server answered. | It does not mean content was sent; an attempt answered 404 or 429 is still an attempt. | every row of table wp_ursy_citations, any status code, page and rest surfaces alike · The Numbers, the inclusion ladder, step one · The Machines, the visitors' book. |
| Served read | A logged attempt the server answered with content: status 200 or 206, from a named AI reader, at a page or a content API route. | It does not mean anyone read it, understood it or named this site anywhere; and this recorder stores no byte count, so answered but empty cannot be separated here and is not claimed. | status_code 200 or 206 in table wp_ursy_citations; every named reader, including the one withdrawn from credit, until the credited step takes it away · The Numbers, the inclusion ladder, step two · The Machines · The Evidence. |
| Withdrawn from credit | A named reader whose rows are recorded and shown in full but excluded from credited totals and from the mint — on this site, amazonbot, as the wallet registry's credit_status says; the shared package intends the same everywhere, and this page can vouch for this host only. | It does not mean blocked; the runtime does not refuse the reader, it declines to thank it — whether anything in front of this host refuses it is not observable from here and is not claimed. | credit_status withdrawn_no_credit in the mint wallet registry, applied after alias binding; where the mint is not running the rule is applied by the literal name amazonbot and the provenance line says so · The Machines, withdrawn · The Numbers, counting rules · Leaderboard, kept off the board. |
| Knock | One request recorded by the traffic ledger, in any class and any bucket, on the UTC day it arrived. | It does not mean a page view by a person, a basket, an order or a purchase; a knock is a request. | one count per URL bucket per visitor class per UTC day in option ursy_io_traffic; machine means every class except human · The Evidence, knocks by class · /wp-json/ursy-runtime/v1/knocks. |
| AI API call | One request to a machine door on this site — Nicola, MCP or a public API namespace — from a caller whose user-agent names an AI reader. | It does not mean a page read, and it is never added to served reads; the two come from different tables and share no key. | one row in table wp_ursy_api_log whose ua_class begins ai:; the IP is stored as a salted 24-character hash, never as the address · The Doors, what the doors recorded · Home, stage three. |
| Human knock | One request recorded in the human class after the consent bar was accepted. | It does not mean a person, a visitor or a session; it is a floor on requests from browsers, never a head count. | class human in option ursy_io_traffic, written only when cookie ursy_consent is yes (or always, where the site shows no consent bar) · The Humans, the floor broken into days · The Numbers, the headline ledger. |
| Lookup | What was typed into a search, a tool or Nicola, defanged, with injection phrases replaced by [FLAGGED], stored with the tool slug and the mode. | It does not mean who typed it; no IP, account or cookie is stored with a lookup. | one row in table wp_ursy_lookups, recorded whether or not the consent bar was accepted, as the published policy says · The Humans, what they asked. |
| Citation token | A soulbound, non-transferable record on this site's mint ledger thanking a named AI reader for one row of served-read evidence on a completed UTC day; one row earns one token, and every token is worth £0 by contract. | It does not mean a purchase, a payment, a reward with monetary value, or proof that this site was named inside an AI answer. | class key stage_1_citation; one active row in table wp_ursy_mint_ledger per eligible row of wp_ursy_citations, under the accepted rule version, with a wallet and an evidence key; nothing before 8 September 2026 · The Mint · The Study · Leaderboard · Home, stage four. |
| Our own probe | A request made by this site's own operator or build checks to test a surface. | It does not mean a qualifying machine read. The original citation recorder has no independent probe flag; the separate sponsor ledger supports server-verified probe flags. | 11 September 2026 correction: this zero describes only the citation ledger, whose recorder has no independent probe flag. The separate append-only sponsor ledger retains verified probes and excludes them from its production totals when sponsor evidence and probe recognition are enabled · The Story, what the words mean. |
Source: the dictionary room's one fixed array (ursy_estate_uth2_dictionary_terms), read by this room and The Dictionary. Window: as at 12 Sep 2026. Rule: definitions identical in every room and in the JSON twin. Freshness: Frozen until the dictionary changes.
The correction
What we got wrong
Every mistake we have found is listed here with its date. A figure whose meaning changed is never quietly replaced; the old reading stays in the sentence that corrects it.
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.
Revised 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.
No further correction has been needed on this site — 0 (honest zero) — and this sentence will change the day one is.
estate correction list and config uth_corrections · as at 12 Sep 2026 · every correction that names this room or every room, dated, newest first; 0 (honest zero) site-specific rows · Frozen until a correction is added
Every figure in this room was read at page generation on 12 Sep 2026 18:41 UTC and is held for up to 120 seconds; this copy was served at 18:42 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 — an AI-referred session, a citation inside an answer — says so in those words and never becomes a number. 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.recipes/wp-json/ursy-runtime/v1/uth?room=story.
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