ursy.singles · The instrument and the live record
Four stages. Four honest answers.
A real, working URSY site built to double as an instrument. It publishes its own workings: every named machine reader that knocked, what the server returned, what the ledgers counted, and what still cannot be observed from here.
Across 1 UTC calendar days, named AI readers averaged about 8.0 served reads 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 01 of 12
The experiment, in plain English
URSY.SINGLES keeps one governed set of facts about itself — 2 declared pages, 0 (honest zero) services, its machine files and its public API namespaces — and serves the same facts to people and to named AI readers.
config pages register · this request · one row per page the site declares to machines · Live
config services register · this request · one row per service with an address · Live
This is a live clean-data experiment on a working site. It tests whether publishing structured, honest facts earns repeated machine use on merit. The result is measured with first-party server-side ledgers, never with sampled third-party estimates.
The claim
A working site that publishes the evidence of how machines use it.
One site, one estate runtime, one set of ledgers, and the server-side record of which named machine readers were served, what they were served, when they returned, and which API calls the ledger recorded (lanes the site exempts from logging excepted).
The definitions, failures, corrections and deliberate zeros are published alongside the success.
Nothing here is modelled, extrapolated or purchased.
What the evidence already shows
3 named AI and search readers were served content by this site between 12 Sep 2026 and 12 Sep 2026, and 8 of their 8 requests were answered with content. How each reader found this site is not recorded here (no referrer is kept), so it is not claimed.
named readers — table wp_ursy_citations · lifetime of the table, first row 12 Sep 2026 14:30 UTC · distinct named readers served 200 or 206 · Live
answered with content — table wp_ursy_citations · lifetime of the table, first row 12 Sep 2026 14:30 UTC · status 200 or 206, readers withdrawn from credit excluded · Live
requests — table wp_ursy_citations · lifetime of the table, first row 12 Sep 2026 14:30 UTC · every logged request by a named AI reader at a page or REST content route, whatever the outcome · Live
What the experiment measures separately
- Machine knocks —
option ursy_io_traffic and its month archives - AI served reads —
table wp_ursy_citations - AI API calls —
table wp_ursy_api_log - Appreciation tokens —
table wp_ursy_mint_ledger
Keeping each result separate is part of the science: no stronger outcome is manufactured from a weaker one.
The four stages
What actually happens, in four steps
These four figures are never added together: they come from different tables over different windows and share no key.
Stage one
We put up signposts
In plain words
We publish pages and machine files designed so a machine can find its way around and quote them.
Precisely
0 (honest zero) published pages and posts and 5 machine files. This counts what we offered, not what anyone took.
Stage two
Machines read them
In plain words
A named AI reader asked for a page or a content API route and our server sent it.
Precisely
Rows in table wp_ursy_citations with status 200 or 206, readers withdrawn from credit excluded, 12 Sep 2026 14:30 UTC to now. 0 (honest zero) served rows from a withdrawn reader are recorded and not credited.
Stage three
Machines call the doors
In plain words
A named AI caller used one of the machine doors — Nicola, MCP or a public API.
Precisely
Rows in wp_ursy_api_log whose caller class begins ai:, 14 Aug 2026 to 12 Sep 2026.
Stage four
Appreciation tokens
In plain words
One served-read row on a completed UTC day earns the reader one £0 soulbound thank-you, recorded in public.
Precisely
Stage 1 citation tokens on this site's mint ledger: 0 (honest zero). Gate: closed — shadow mode (plans, writes nothing). Ready to mint once the gate opens: 0 (honest zero). Today's rows pending: 8. Earliest live date 8 September 2026. Stages 2 to 4 do not exist in this site's contract.
Independent witness
Answer citations observed outside this server
In plain words
Whether this site's name appeared inside an AI answer is something no website can see from its own logs.
Precisely
No external answer-engine measure has been imported for this site.
No figure is shown, because none has been measured.
Where it stands
The headline figure, broken into days
One total, then the same total cut into the windows every other room uses, so a reader can see the pace as well as the size.
8 — recorded across 1 days.
Capture for this counter began on 12 Sep 2026. The total spans 1 UTC calendar days, including today so far. That is about 8.0 served reads per calendar day.
window days are inclusive UTC calendar days from the source table's first recorded row 12 Sep 2026 14:30 UTC · today so far is included · table wp_ursy_citations · Live
How to read this
What we will not do to a number
Six rules, applied to every figure in every room. Where a figure cannot meet them it is withheld and the withholding is written down.
- No bare numbers.Every figure carries where it came from, what period it covers, the rule that produced it and whether it is live or frozen. A figure that cannot carry all four is withheld.
- No unreconciled tables.Every table either sums to a stated total or states in writing why its rows cannot be summed.
- No abbreviation.Numbers are written out in full. Rounding a figure is a way of hiding how confident you are about it.
- No adding across sources.The source tables count different things over different windows and share no key. No cross-table total is published.
- No quiet fixes.Corrections are dated, in the main text, and never removed. The complete list is in The Workings.
- No borrowed confidence.Where the capture behind a figure is incomplete, the figure is published as a floor and labelled as one.
The complete list of corrections: The Workings — every mistake we have found, dated
| Step | Rows | Rule |
|---|---|---|
| Credited served reads | 8 | Status 200 or 206, from a reader that keeps credit |
| Served, but withdrawn from credit | 0 (honest zero) | One reader withdrawn from credit for behaviour, its history kept in full |
| Asked, but not answered with content | 0 (honest zero) | Any status outside 200 and 206 |
table wp_ursy_citations · 12 Sep 2026 14:30 UTC to 12 Sep 2026 · status 200 or 206, readers withdrawn from credit excluded · Live
Unlike teas.co.uk's ladder there is no 'answered with zero bytes' step: this recorder stores no byte count, so that step cannot be measured here and is not claimed.
The mint
The machines that read this site earn a token worth nothing
An appreciation token is a thank-you for a completed day of served reads. It has no monetary value, cannot be transferred, and is recorded in public.
When a named AI reader is served a page here, the row is evidence. Once the gate opens, this site will issue that reader one soulbound thank-you token for every eligible row on a completed UTC day, on its own ledger, worth £0, movable to nobody, and published on the Leaderboard. Today the gate is closed for 3 named reasons, each listed in The Study, and shadow mode plans and writes nothing; tokens issued so far: 0 (honest zero). The Leaderboard shows zeros until the first issue. The point is to say thank you in a way that can be checked, not to pay.
Tokens are soulbound to the AI worker wallet that earned them, non-transferable, and carry no monetary value. They are public messages of appreciation.
the contract model the hash is computed over · this request · the laws line as the contract states it · Frozen until the contract changes
Gate closed — shadow mode (plans, writes nothing). Issued 0 (honest zero). Ready 0 (honest zero). Pending today 8. Earliest live 8 September 2026.
gate — options ursy_io_mint_master_lock, _shadow_mode and _operator_release read past the object cache, plus the live-earliest constant · this request · every reason the gate is closed is listed in The Study, none is summarised · Live
issued — the mint's handshake block · this request · issued tokens counted under the accepted rule version, active status, wallet and evidence key present · Live
ready and pending — dry run of the daily writer · completed UTC days before today · today's rows stay pending until UTC closes; nothing was written · Live
earliest live — constant URSY_IO_MINT_LIVE_EARLIEST · as at 12 Sep 2026 · no token is issued on this site before this date; the shared package intends the same date everywhere, and this page can vouch for this host only · Frozen until the contract changes
- One stage on this siteStage 1 citation only: one evidence row in table wp_ursy_citations on a completed UTC day equals one token. Stages 2 to 4 (followback, click-back, sale) are not in this site's contract.
- What stops farmingEvery token is worth £0, is soulbound to one reader's wallet and cannot be transferred; one reader is withdrawn from credit for behaviour and its evidence is kept in full rather than deleted.
- The Hero BoardEvery AI family and every named reader, ranked by tokens issued on this site, with the ledger's own reconciliation shown. Before the first run every row is a zero, published as a zero.
Full rules: The Mint · the board: Leaderboard
This site in particular
This site in particular
Rows the site file supplies about itself, in its own words: the label, the value and where each comes from. The runtime prints them; it does not write them.
This site adds no rows of its own — 0 (honest zero).
rows supplied by sites/ursy-singles.php · this request · label, value and provenance as the site file states them · Frozen until the site file changes
Honesty note. Every figure on this page was read at 12 Sep 2026 15:10 UTC and is held for up to 120 seconds; this copy was served at 15:10 UTC and built the figures afresh. A ledger that is installed and empty prints 0 (honest zero); a ledger not yet installed prints not counting yet; a fact this family of site cannot read prints not kept on this site; a fact the site has ruled out prints not kept on this site by design. Nothing on this page is modelled, extrapolated or purchased. Revised 4 September 2026: the single-page truth room was replaced by these twelve rooms; no stored value changed, and every figure the old page showed appears in a room with the same source.
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
Public discovery · Machine Attention · Today (UTC)
What was delivered, and what was verified
Counts cover public discovery routes only; private or authenticated requests are excluded. Origin sponsor generation and central acceptance are separate. Production GET candidates are withheld pending authenticated edge method proof. VME proves emission, not reading, recommendation, citation or sale.
Collector: awaiting registration · Runtime 1.0.0 · Updated
The local runtime is active. Central VME remains unavailable until URSY.AD registers this property’s signing credential and returns verified totals. Queued local candidates are not reported as VME.
Active sponsorship: teas.co.uk · teas-ursy-2026-09-v1 · Paid placement.
Funnel, machine categories and recent days
Selected 1 · Injection attempts 1 · Local candidates 0 · Dead letters 0
Machine requests: 7 days 17 · 30 days 17
Instrumentation began 2026-09-12T13:43:05Z. Earlier site telemetry uses its original methodology.
| Category | Requests |
|---|---|
| unknown_machine_like | 16 |
| named_ai | 1 |
| Date | Machine requests | Sponsor emitted | Candidates |
|---|---|---|---|
| 2026-09-12 | 17 | 1 | 0 |
Definitions, privacy and limitations · The same figures as JSON