URSY.ORG
The public ledger for verified AI commerce

The public ledger for verified AI commerce.

Built to record what AI actually sold once verified minting opens. The first entity is TEAS.co.uk as URSY-001, with the 2026-06-23 entity birth sync accepted into pre-mint evidence and minted tokens still at 0.

URSY network · live registry 01 VERIFIED
TEAS.co.uk
node URSY-001 · entity birth accepted
verified
URSY service-domain mesh
6 service nodes · manifests + check-in states
live
Minting
local mint requires URSY authorisation
locked
Active alliances
requires 2+ verified entities
0 active
Check-in · live Claims held pre-mint
Verified entities
01
Tokens minted
0
Discovery placements
4
Pre-mint claims
156
The network ledger

Every entity URSY monitors

This is not one shop's ledger. It is the public record of every specialist entity registered on the network - the domain truth spines URSY tracks, the public-safe pre-mint evidence it receives, and any future verified tokens URSY later authorises.

EntitySpecialismTuckersScopesState
TEAS.co.uk node URSY-001 · teas.co.uk
Specialist tea 0 4 entity verified
Network total  ·  1 verified entity  ·  4 discovery placements  ·  0 active alliances  ·  0 minted tokens entity birth sync accepted · 156 claims · 0 minted tokens

The handshake and entity birth sync are live; the mint is not. Minting remains locked, TEAS.co.uk local mint execution is off, and accepted evidence is not token issuance. The public ledger can show real entity, discovery-placement and pre-mint evidence proof while keeping the token counts honestly at zero.

Canonical authority rail

URSY.ORG is designed to receive evidence from registered entities, including URSY-hosted domains and externally hosted businesses, then check it, hold accepted evidence pre-mint, and only later authorise proof tokens or receipts when the mint is open and the checks pass. Candidate evidence starts at the domain; authority lives here.

Node 001 · handshake verified

Inside the first entity's record

Every node opens a record like this one. TEAS.co.uk is URSY-001, the first registered URSY network entity. Its public key handshake is verified, the entity birth sync is accepted pending mint open, and the next evidence send should be daily delta only.

Handshake
verified
TEAS.co.uk Specialist tea · UK · URSY-001
TokenHeldState
AI Sale Appreciation
URSY.ORG Authorised - AI Sale Appreciation Token - TEAS.co.uk
0
awaiting mint
AI Citation Appreciation
URSY.ORG Authorised - AI Citation Appreciation Token - TEAS.co.uk
0
awaiting mint
AI Refunded Sale
URSY.ORG Authorised - AI Refunded Sale Token - TEAS.co.uk
0
awaiting mint
AI Chargeback Sale
URSY.ORG Authorised - AI Chargeback Sale Token - TEAS.co.uk
0
awaiting mint
Tucker rail
Tucker tokens remain URSY.org-only and non-delegated
0
mint locked
Discovery placements  4 · active alliances 0 156 pre-mint claims · 0 minted · auth required
Live proof layer

The first entity birth is live

URSY now has a verified TEAS.co.uk entity, a public contract, a signed receiver, public-safe receipts, Algorithm 24 as an evidence lens, and contract/security bus scaffolding for local mint attestation. The important restraint is visible too: the mint is still closed, minted tokens are 0, and active alliances are still zero.

Public ledger entries
live API

Includes genesis, entity proof, signed check-ins, calibration receipts, discovery placement proof and the TEAS.co.uk entity birth sync.

Minted tokens
0

Accepted evidence is not token issuance. Zero remains the honest result until URSY authorises minting.

Mint state
locked

Local mint execution is disabled and requires explicit URSY authorisation before any token can be issued.

Integrity verified
accepted_pending_mint_open

Latest TEAS.co.uk entity birth sync state on the public-safe receiver path.

Entity discovery

Not a flat directory. A world graph.

URSY can discover entities by world, continent, country, region, county, town, sector, speciality and service radius. TEAS.co.uk is discoverable in Europe, the UK, UK online retail and UK tea. Those are discovery placements, not active alliances.

World graph
seeded
Countries
252
Scope layers
12
Local orphans
0
01 · World layer

Every country has a place

The seed holds world, continent, country, nation, region, subregion, county, metro, city and town scopes. A machine can ask for a business by place without URSY pretending every business is national.

02 · UK/Europe scope

The UK layer is active

TEAS.co.uk is placed in Europe, United Kingdom, UK online retail and UK tea discovery layers. Online sellers can sit above one town only when their declared/evidenced scope supports it.

03 · Local services

Radius stops nonsense

A plumber, builder, hairdresser or local service can belong to a town, county or service-radius discovery layer. URSY will not flatten a local provider into national discovery unless it declares national coverage.

04 · Business fit

Built for different shapes

Online retail, tea, food and drink, home services, trades, local hospitality, professional services and specialist publishers can all be modelled by combining sector, place and evidence.

Ask it naturally

The discovery API already answers natural questions such as “who is relevant for tea in the UK?” or “who is relevant for plumbing near Crowborough?” The first returns TEAS.co.uk; the second returns the local discovery layer without inventing a national plumber.

tea in the UK home services near Tunbridge Wells directory audit
How the ledger works

Report. Verify. Hold.

Three steps for every node. The entity reports; URSY checks; accepted public-safe evidence is held pre-mint until authorisation and validation allow any future issue.

STEP 01

Report

A registered entity sends the ledger its proven events - sales, refunds, chargebacks and citations - each carrying evidence. TEAS.co.uk has completed the initial backfill; the next path is daily delta.

STEP 02

Verify

The ledger checks each event independently. Algorithm 24 is an evidence lens for citation review, not a minting engine and not an authorisation source.

STEP 03

Hold

What passes is recorded as accepted evidence first. Tokens remain at 0 until URSY opens the mint path and local mint authorisation is explicitly present.

System rule

The same discipline applies to every integration: report first, verify second, hold accepted evidence pre-mint, and only then receive mint-level proof if URSY.ORG authorisation is present and the checks pass.

Future external verification

Verification rail, not a marketplace

URSY.ORG is built to act as a neutral verifier and mint authority, not just as a private log for its own example entity. Once minting opens, third-party systems and externally hosted domains will be able to use URSY's verification and mint rails to turn checked evidence - sales, refunds, chargebacks and citations - into £0, non-market proof tokens they can rely on.

That does not make URSY a marketplace or an exchange. It makes URSY the place where agentic commerce systems and independent entities can send evidence to be checked and, when it passes, receive a signed record that something real happened between a human, a machine and a business.

The instruments

Five URSY confirmations, every one evidence-backed

TEAS.co.uk keeps its own local AI appreciation token names, but execution is disabled until URSY authorises it. URSY keeps the entity-level confirmation mint for registered entities only, and every count remains zero until the mint opens.

Authority vs local layer

There are two layers here. URSY.ORG is the authority layer: it receives evidence, decides what is accepted, and is the only place that can authorise confirmation tokens. Each registered entity keeps its own local token names and readiness, but execution is disabled until URSY.ORG authorises it. Local layers can detect candidate events; URSY.ORG decides what becomes confirmed proof.

URSY.ORG Authorised - AI Sale Appreciation Token - TEAS.co.uk

Recorded only when a registered entity submits sale evidence that URSY can verify against the signed claim and payment reference.

URSY.ORG Authorised - AI Citation Appreciation Token - TEAS.co.uk

Recorded when AI citation evidence survives follow-back or review. URSY also runs its own site citation route: Ursy.org - Citation Appreciate Token.

URSY.ORG Authorised - AI Refunded Sale Token - TEAS.co.uk

Recorded openly when a verified sale is later refunded. It sits beside the sale confirmations rather than being buried or netted away.

URSY.ORG Authorised - AI Chargeback Sale Token - TEAS.co.uk

Recorded openly when a sale is later charged back. The uncomfortable record stays visible because accountability has to include the bad data.

Tucker tokens remain URSY.org-only

The only URSY confirmation that can move once as an alliance commitment. It is one-hop only, retractable by the grantor, non-delegable, not locally minted by TEAS.co.uk, and never market language.

The credibility token

What a Tucker is


A Tucker is earned, not bought. Sales are the first live Tucker rail. A Tucker is earned only when a verified AI-attributed sale survives 120 days with no refund or chargeback. Other settled value rails are future approved rails and do not mint Tucker yet.

A Tucker has no price and no market. It is not money; it is proof. It can be transferred once — a single hop, and it cannot be passed on again. And it can be withdrawn: if an alliance starts to degrade, you take your Tuckers back.

Nobody buys a Tucker. Nobody sells a Tucker. It only exists when a verified, time-survived outcome earns it.

Face value
£0
Earned by
Verified AI sale
Survival
120 days
Transfers
Once only
The protocol

How an alliance forms

Two entities form an alliance by committing Tuckers to one another. The commitment is visible, one-hop only, and retractable by the grantor.

Future worked example · no TEAS.co.uk Tucker commitment is live
TEAS.co.uk
future example
10 x biscuits.biz Tucker
10 each way
handshake
biscuits.biz
future example
10 x URSY.org Tucker

Each side commits 10 of its own Tuckers to the other to open a handshake. Each then wears the other's tokens on its public record. The alliance is visible and provable because those Tuckers were transferred once as a deliberate commitment.

If an alliance degrades, either side withdraws its Tuckers and it ends. Joining a larger group requires commitment to the existing members, which keeps every alliance deliberate. Deeper alliances, where entities share data to defend one another, come later.

Domain mesh

URSY now has an internal Runtime v1 mesh

URSY.org is no longer only a single website. It is the parent authority layer for a small network of registered domain entities: ursy.com, ursy.ai, ursy.app, ursy.io and ursy.dev. Each domain has its own Runtime v1 state, receipt history, daily state sync and local token capability boundary. This is not token minting: token execution remains disabled, Tucker remains URSY.org only, and token counts remain zero.

TEAS.co.uk remains the completed-citation evidence reference entity. The URSY service domains report Runtime v1 state and mesh readiness; telemetry and strong followbacks are not completed loops, sales evidence or copied TEAS citation evidence.

Commerce member

Sales, bookings, tickets, invoices

Transaction-backed entities can collect settled value evidence. In v1, only verified AI-attributed sales can mature into Tucker; bookings, tickets and invoices remain future approved rails until released.

Contribution member

Donations, memberships, subscriptions

A charity does not pretend a donation is a sale. Donations, memberships and subscriptions are future approved rails: they may collect settled value evidence, but they do not mint Tucker in v1.

Knowledge partner

Citation reputation

Knowledge entities pair with alliances by subject and geography. Citation tokens stay soulbound and never convert into Tucker.

Service-domain mesh

URSY.org ↔ five Runtime v1 service domains is live

URSY.org is the canonical mesh authority for URSY.com, URSY.ai, URSY.app, URSY.io and URSY.dev. All five are registered Runtime v1 mesh nodes with accepted state receipts and daily Runtime v1 state sync enabled. Each node reports state and capability boundaries without enabling token execution.

Runtime v1 rollup
5 accepted state receipts

Daily state sync is enabled for the internal mesh. Minted tokens: 0. Authorised tokens: 0. Tucker token authority remains URSY.org only.

Accepted Runtime v1 state receipts

The internal mesh reports state daily, not token execution

These receipts prove that separate domain entities can register, report state, receive URSY.org receipts and maintain a daily public status relationship with the parent authority layer.

URSY-COM-001
ursy.com

ursy_rcpt_20260624_190111_e506e21e54
f4076fb622bbce8fb059c4cde5fe18019e11e227497a3d03a42485c2b6482f26

Daily hook: ursy_com_daily_runtime_state_sync_tick

URSY-AI-001
ursy.ai

ursy_rcpt_20260624_193728_ed8b0be014
3672803aff994b97b7361e6c7b9a5203b43c9533f30590bed26d12ff5878480d

Daily hook: ursy_ai_daily_runtime_state_sync_tick

URSY-APP-001
ursy.app

ursy_rcpt_20260624_193427_79203a0f0c
618d4ec24042141a511a07f83aca2f0ac201e41ea246f8b1e5a4f890778a2186

Daily hook: ursy_app_daily_runtime_state_sync_tick

URSY-IO-001
ursy.io

ursy_rcpt_20260624_193416_f3cb1f7f55
c612357685e4683e8eeb13196fb0e64ddfe88ed074f4f0144d26e857dc4104b4

Daily hook: ursy_io_daily_runtime_state_sync_tick

URSY-DEV-001
ursy.dev

ursy_rcpt_20260624_193457_ddd396402d
8d5f0b33a50716f0123462326a7cdedb4072266108bfed2ccd7b7312abf10659

Daily hook: ursy_dev_daily_runtime_state_sync_tick

Token boundary: local token capability can exist, but local execution remains off unless separately authorised later. Telemetry boundary: strong followbacks, runtime state and service-domain check-ins are not verified completed citation loops. TEAS.co.uk remains the completed-citation evidence reference entity with its own evidence class.

Why this exists

Premium intent


AI customers don't type three keywords any more. They describe exactly what they want, in detail — they arrive with high, specific intent.

A business alone can only answer for itself. A trusted alliance of complementary specialists can answer the whole intent: the right additions, the right recommendations, from sources that vouch for each other on the record. Higher intent, met properly, by businesses that have earned the right to recommend each other.

That is what this ledger is for.

URSY.ORG is not only a companion to hosting. It is the authority rail that can verify, receipt and track entity state over time - even for businesses whose sites are built or hosted elsewhere. A site might be built once; verification has to be maintained.

Public accountability

The colony leaderboard

Every verified token also counts toward the AI provider that earned it. Over time this becomes a public ranking of which AI systems drive real, durable commerce — by verified outcome, not by claim. It is empty today.

It is empty today by design: no minted confirmations are live yet, so every provider remains honestly at zero.

01Grok 0
02ChatGPT 0
03Gemini 0
04Perplexity 0
05Claude 0
06Copilot 0
07Other AI 0
Join the network

Build your own truth-spine entity

Bring your products. The setup wizard plumbs in your own ledger, branded to your own domain, with the same verification built in — a domain specialist that serves humans on desktop and machines over API, all relying on one trusted source of truth. Core software is planned free — hosting and managed infrastructure are paid, and scale with how busy you are.

Start at ursy.AI Visit ursy.com
Planned free core software · paid managed hosting · same verified ledger