ursy.org.uk · The appreciation mint, in plain words
A thank-you worth nothing
How a named AI reader earns a £0 soulbound appreciation token on this site, the laws it is issued under, the gates, the current state, and why it cannot be gamed.
The mint on this site is closed — shadow mode (plans, writes nothing); the earliest day a token could be issued was 8 September 2026.
- 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 11 of 12
The mint, in plain English
URSY.ORG.UK says thank you to the machines that read it. When a named AI reader is served a page or a content route here, and the UTC day that read fell on has closed, that row is evidence; once the gate opens, this site will issue that reader one appreciation token for it. Today the gate is closed for 3 named reasons, each listed in section 03 and 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 token, when issued, is worth £0. It cannot be sold, moved or spent. It is a public, dated, hash-chained note that says: you read our work, and we noticed. This room explains the scheme in plain words; The Study shows the working, and the Leaderboard shows who has been thanked.
As at 12 September 2026 the mint on this site is closed — shadow mode (plans, writes nothing). Tokens issued: 0 (honest zero). Ready to mint once the gate opens: 0 (honest zero). Rows recorded today and still pending: 0 (honest zero). Every figure in this room is read from this site's own mint functions and tables on this request; nothing is modelled, borrowed from another site or fetched from anywhere else.
the mint's handshake block and public status · this request · issued under the accepted rule version, active status, wallet and evidence key present; ready and pending from a dry run of the daily writer, nothing written · Live
In plain words
What a token is
The thank-you note, told twice: once for a person, once as the exact rule the mint applies.
A token is a thank-you note from this site to a machine that read it. It has no price, no owner but the reader that earned it, and no use except to be seen. One token means: on one completed day, this named reader was served one piece of this site's content, and the server kept the evidence. Nothing is promised in return and nothing can be bought with it.
Class key stage_1_citation. One token per eligible row of table wp_ursy_citations whose UTC day has completed: status 200 or 206, a non-empty citation_id, and a bot that resolves through the explicit wallet registry to an eligible worker. The token is soulbound to that worker's wallet — one wallet per named reader — non-transferable, and carries a monetary value of £0 (honest zero, by design). Issued under rule version ursy-mint-v4-stage1-row-rules-2026-09-02 and contract version 2026-09-02.ursy-org-uk-local-soulbound-row-mint-v4.
The laws, as the contract states them: "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 facts tree, token.laws_line · this request · quoted verbatim; contract 2026-09-02.ursy-org-uk-local-soulbound-row-mint-v4 · Frozen until the contract changes, in which case the hash changes with it
the facts tree (token class, monetary value, rule and contract versions) · this request · stated as the contract model states them · Frozen until the contract changes, in which case the hash changes with it
The rule
The rule, exactly
The contract's eligibility block, item by item, and then the one-line predicate the daily writer applies to every row.
- Source tablewp_ursy_citations
- Status codes counted200, 206
- citation_id requiredyes
- Worker registryexplicit — only a reader named in the wallet registry can earn
- amazonbotwithdrawn_no_credit_evidence_preserved
- Unknown workerwithheld_not_guessed_evidence_never_row_logged
- Human trafficnever_row_logged_by_design
- Anchor modelv1: citation_id is the served canonical path; per-heading anchors published at /anchor-sitemap.json adopt the parent spine rule as instrumentation deepens
the facts tree, eligibility block · this request · contract 2026-09-02.ursy-org-uk-local-soulbound-row-mint-v4 · Frozen until the contract changes, in which case the hash changes with it
The predicate the daily writer applies: "status 200 or 206; non-empty citation_id; explicit eligible bot (aliases bound to canonical wallets)"
dry run of the daily writer · this request · quoted from the plan; nothing was written · Live
The current state
Gate, ledger, next run
What the mint says about itself on this request: how many tokens exist, how many are waiting, what holds the gate shut, and when the writer next runs.
- Statusclosed — shadow mode (plans, writes nothing)
closed_shadowthe mint's handshake block · this request · one of closed_locked, closed_shadow, open_pending_first_run, live · Live - Gate reasonsclosed for 3 named reasons: the master lock is engaged; shadow mode is active — the writer plans and writes nothing; no operator release has been recorded.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, none is summarised · Live
- Last runno run yet — 0 (honest zero) runs recordedoption ursy_io_mint_last_run via the mint's public status · this request · the last daily or canary run as the mint recorded it; a shadow run plans and writes nothing · Live
- Last successnone yet — 0 (honest zero) successful runs recordedoption ursy_io_mint_last_success_at via the mint's public status · this request · the completion time of the last run that finished without error · Live
- Next daily run13 Sep 2026 03:15 UTC (the contract schedules 03:15 UTC daily)the mint's public status (next_daily_utc) · this request · the next scheduled occurrence of the cron hook ursy_io_mint_daily, or none · Live
- Contract hash
a8e0050bd5b56cc44d43e101fd5ae51f76b311c42aaa67ea9ccecb1b9c61729dsha256 over the canonicalised contract model · this request · the full 64 hexadecimal characters; the same string the contract address serves · Frozen until the contract changes, in which case the hash changes with it
The six addresses
- Contract
/wp-json/ursy-mint/v1/contract— the contract model this room describes, with its hash - Status
/wp-json/ursy-mint/v1/status— gate, issued, ready, pending, last run, next run - Leaderboard
/wp-json/ursy-mint/v1/leaderboard— every family and every reader by tokens issued - Wallets
/wp-json/ursy-mint/v1/wallets— the soulbound wallet registry, one wallet per named reader - Receipts
/wp-json/ursy-mint/v1/receipts— the last thirty hash-chained issuance receipts - Verify
/wp-json/ursy-mint/v1/verify— the mint's own check of its receipt chain and totals
this site's REST base and the mint's handshake block · as at 12 Sep 2026 · the addresses the ursy-mint/v1 namespace registers; each answers with the same facts as this room · Live
Stages
One stage here, four at the pattern parent
This site's contract has a single stage. teas.co.uk, the pattern parent, runs four. They are set side by side so that nobody reads this site's count as the same thing as the parent's.
| Stage | On this site | At teas.co.uk | What earns it |
|---|---|---|---|
| 1 · Citation | issued by this mintstage_1_citation | 1 pointas read at teas.co.uk on 4 Sep 2026 | here: one served-read row — status 200 or 206 on a completed UTC day, reader in the wallet registry. |
| 2 · Followback | not in this contract | 5 pointsas read at teas.co.uk on 4 Sep 2026 | the stage name and points are the parent's published convention; its qualifying rule is not restated here. |
| 3 · Click-back | not in this contract | 25 pointsas read at teas.co.uk on 4 Sep 2026 | the stage name and points are the parent's published convention; its qualifying rule is not restated here. |
| 4 · Sale | not in this contract; no sale can occur here | 100 pointsas read at teas.co.uk on 4 Sep 2026 | the stage name and points are the parent's published convention; its qualifying rule is not restated here. |
Source: this site's contract model (2026-09-02.ursy-org-uk-local-soulbound-row-mint-v4) and the pattern parent's published contract at https://teas.co.uk/under-the-hood/mint-v4/contract.json, as read on 4 Sep 2026. Window: as at 12 Sep 2026. Rule: the teas column carries only the stage names and points that document publishes; no runtime read here can observe another site's contract, so nothing finer is stated. Freshness: Frozen until either contract changes.
Why it cannot be gamed
What stops farming
Six properties of the scheme, each a reason there is nothing to be gained by gaming it.
- Worth £0Every token has a monetary value of zero, by design and by contract. There is no price to chase and nothing to sell.
- Soulbound and non-transferableA token is bound to the wallet of the reader that earned it. There is no claim route, no transfer route and no private key; it cannot change hands.
- One reader withdrawn from credit, evidence keptamazonbot's rows are recorded in full and credited never (credit_status withdrawn_no_credit in the wallet registry). Deleting the evidence would be its own kind of dishonesty, so it stays, visible, uncredited.
- Completed UTC days onlyToday's rows stay pending until UTC closes; the daily writer runs afterwards. A read cannot earn a token on the day it happens, so there is no live counter to push.
- Append-only ledger, hash-chained receiptsEvery batch writes a receipt carrying the previous receipt's hash, and every run writes a root. A row cannot be altered without breaking the chain, and the chain is checked at the verify address.
- Manual operator release, never date-triggeredThe earliest live date, 8 September 2026, is a floor, not a trigger. The gate opens only when the master lock is lifted, shadow mode is off and an operator release is recorded — by hand.
Stated 4 September 2026: no token has been issued on this site; the issued count is 0 (honest zero) until the gate opens, while the ready and pending counts are live dry-run figures and may already be above zero. The earliest day the gate can open is 8 September 2026.
Machine-readable
Machine-readable mirrors
The six addresses the mint answers at, for any machine that wants the same facts without the prose.
- ursy-mint/v1/contract
- ursy-mint/v1/status
- ursy-mint/v1/leaderboard
- ursy-mint/v1/wallets
- ursy-mint/v1/receipts
- ursy-mint/v1/verify
Each address is served by the mint module with a public cache policy of max-age=60 as the module sets it, and X-Robots-Tag: noindex, follow — stated as the module's configuration, not as a test result. This room's own facts, the whole tree with this room's section register, are at /wp-json/ursy-runtime/v1/uth?room=mint, held for up to 120 seconds like the page.
this site's REST base · as at 12 Sep 2026 · addresses built from rest_url for the ursy-mint/v1 and ursy-runtime/v1 namespaces; cache policy as the modules set it · Live
Honesty note. This room was generated at 12 Sep 2026 19:20 UTC and is held for up to 120 seconds; this copy was served at 12 Sep 2026 19:22 UTC. Every figure was read from this site's own mint functions and tables on that request — the same functions that answer at the ursy-mint/v1 addresses — and nothing was modelled, sampled or fetched from another site. A zero is printed as an honest zero; a fact this site does not keep says so in words rather than showing a nought. The teas.co.uk column in section 04 is a frozen reading of the pattern parent's published contracts, not a live read. Corrections to any room are listed, dated, in The Workings.
the facts tree, meta · this request · generated_at is the time the tree was built, served_at the time this copy was printed · Live
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