registered · received verified · public-safe

URSY.IO under the hood

URSY.IO is the network connective Service-Domain Node for the URSY estate. URSY.site and URSY.co.uk have joined the domain mesh, daily deltas are programmed, and URSY.org remains the canonical ledger, mint, discovery and mesh authority.

Audit ok · ursyio_audit_20260728_121728 · generated 2026-07-28 12:17:28 UTC

Mesh domains

URSY.org plus joined URSY mesh domains.

New domains

URSY.site and URSY.co.uk are now in the mesh.

Daily deltas

Programmed across the listed mesh domains.

Routes

Public route authority entries.

Journeys

Hashed same-source entities.

Verified loops

Completed citation-loop evidence.

/ai-entry.json /truth-spine.json /analytics.json /runtime-v1.json /runtime-compliance.json service manifest domain mesh citation evidence cron

URSY Domain Mesh

URSY.IO is registered as URSY-IO-001, the network connective node. The mesh is now marked as birthed: URSY.site and URSY.co.uk are joined, and every listed mesh domain has a daily delta route programmed. Signed URSY.org bulletins are read-only knowledge updates here; they never trigger code, DNS, credential, payment or token changes.

Node

URSY-IO-001

network_connective_node

Key

Live

Private key outside web root

Authority

ursy.org

authority key pinned

Check-in

Verified

received_verified

Bulletins

Configured

Read-only URSY.org bulletin ingest

Latest Bulletin

pending

Only verified signed bulletins are stored.

Public key Ab0qOhEnaPoD6c4GWz2Z6d0E7MW8V4vz46GHQ0rl/cs=
Fingerprint sha256:9b46cf8fb0195e4d0017846f3ef8d6d179d9ccc478538c81262be61312696333
Latest payload hash 32d499fc041d0a528bd7b925a36ab355e3164cea6d3c0c77322fb77eb7a1eb86

Mesh Domain Directory

The public route directory now includes URSY.site as the customer staging environment and URSY.co.uk as the UK regional post-office and free hosted-domain option. This does not change URSY.IO routing: URSY.IO remains direct_root to URSY.org.

Domain	Role	Daily delta
`ursy.org`	Root authority, ledger, mint, discovery and mesh record source.	`programmed`
`ursy.dev`	Developer and protocol surface.	`programmed · 04:10 UTC`
`ursy.io`	Network connective and machine hospitality node.	`programmed · 04:18 UTC`
`ursy.app`	Consumer access surface.	`programmed · 04:26 UTC`
`ursy.ai`	Implementation, onboarding and AI working surface.	`programmed · 04:34 UTC`
`ursy.com`	Business education and commercial explanation surface.	`programmed · 04:42 UTC`
`ursy.site`	Customer staging environment where customer websites can work before going live.	`programmed · 04:50 UTC`
`ursy.co.uk`	UK regional post-office node and free hosted domain option for customers who do not want to buy their own .co.uk or .com.	`programmed · 03:45-04:00 UTC`

URSY.site is where customer websites can work before going live. URSY.co.uk is the UK regional/free hosted-domain option for customers who do not want to buy their own .co.uk or .com.

Footer And Route Plumbing

The public footer and route authority now carry the full URSY estate route set.

Route	URL
`root_authority`	https://ursy.org/
`canonical_ledger`	https://ursy.org/ledger
`business_education`	https://ursy.com/
`implementation_onboarding`	https://ursy.ai/
`consumer_access`	https://ursy.app/
`developer_protocol`	https://ursy.dev/
`network_connective`	https://ursy.io/
`customer_staging`	https://ursy.site/
`uk_regional_post_office`	https://ursy.co.uk/
`uk_free_hosted_domain`	https://ursy.co.uk/

Regional Routing Awareness

URSY supports future regional routing. A regional node, such as URSY.co.uk for the United Kingdom, can act as a middle sorting office for entities in that region. This domain currently remains on direct root routing to URSY.org unless a regional route is explicitly assigned.

Routing field	Value
supported_route_modes	`direct_root, regional_then_root, regional_dry_run, root_fallback`
route_mode	`direct_root`
root_authority	`ursy.org`
regional_routing_supported	`true`
regional_routing_active	`false`
regional_node_assigned	`false`
regional_node	`none`
UK regional node	`ursy.co.uk · uk_regional_post_office_and_free_hosted_domain · not active as URSY.IO route`
evidence_sending	`runtime_status_delta_only`
minting	`false`
token_authorisation	`false`
TEAS data imported	`false`

URSY.co.uk is active in the wider mesh as the UK regional/free hosted-domain node. URSY.IO remains direct_root to URSY.org and is not routed through URSY.co.uk unless a regional route is explicitly assigned.

Runtime v1.1 Mesh Status

This domain is part of the URSY Runtime v1.1 internal mesh. URSY.IO remains direct_root to URSY.org, with one daily public-safe runtime status delta scheduled at the URSY.org approved slot.

Runtime v1.1 status here is public-safe configuration state only. It is not token execution, not sales evidence, and not a claim that completed citation loops exist unless URSY.IO has its own verified completed-loop evidence.

Runtime field	Value
runtime_standard	`URSY_MESH_RUNTIME_V1`
runtime_version	`1.1`
role	`ursy_mesh_domain`
runtime_status	`runtime_v1_1_daily_direct_root_delta_ready_no_mint`
route_mode	`direct_root`
root_authority_domain	`ursy.org`
regional_node_domain	`null`
regional_node_id	`null`
customer_domain	`false`
daily_send_enabled	`true`
sends_enabled	`true`
cron_enabled	`true`
cron_hook	`ursy_io_daily_runtime_v11_direct_root_delta_tick`
agreed_send_slot_utc	`04:18`
next_scheduled_send_utc	`2026-07-29T04:18:00+00:00`
minting_enabled	`false`
token_authorisation_enabled	`false`
old_daily_runtime_state_sync_enabled	`false`
old_daily_hook_next_run	`not scheduled`

Domain Identity

URSY.IO is the protocol and network layer node in the URSY mesh. It exposes public-safe machine surfaces for routing, evidence readiness and local contract status, while URSY.org remains the root authority.

Field	Value
entity_domain	`ursy.io`
entity_display_name	`URSY.io`
entity_slug	`ursy-io`
entity_id	`URSY-IO-001`
mesh_role	protocol/network layer node

Local Mint State

The local token capability layer is aligned to the URSY Runtime v1.1 model. AI citation appreciation, AI sale appreciation, AI refunded sale and AI chargeback sale are present as inactive capability classes. Live execution is disabled and cannot proceed without URSY.org signed authorisation and a matching local contract hash.

Control	Status
local_mint_state	`local_mint_scaffolded`
local_mint_execution_enabled	`false`
ursy_authorisation_required	`true`
minted_tokens	`0`
local_mint_receipts	`0`
authorisation_rows	`0`
Tucker delegation	`false`
Tucker token local availability	`false · URSY.org only`
Soulbound / transferable	`soulbound=true · transferable=false · worker_bound=true · colony_owned=true`

Tucker token is URSY.org only. URSY.IO cannot issue Tucker tokens locally.

Inactive Capability Classes

Token type	Display name
`ai_citation_appreciation`	URSY.ORG Authorised - AI Citation Appreciation Token - URSY.io
`ai_sale_appreciation`	URSY.ORG Authorised - AI Sale Appreciation Token - URSY.io
`ai_refunded_sale`	URSY.ORG Authorised - AI Refunded Sale Token - URSY.io
`ai_chargeback_sale`	URSY.ORG Authorised - AI Chargeback Sale Token - URSY.io

Contract Attestation

The attestation layer is prepared for just-in-time URSY authorisation, local contract hashing, runtime-state checks and receipt validation. It is not a live mint path.

Attestation field	Value
local_contract_hash	`e15523adc28ebf90a07898fa3de1657388d959be6d8a16f956626bb34def8458`
contract_attestation_status	`scaffolded_pre_mint`
single_mint_path_verified	`true`
local_mint_execution_enabled	`false`
just_in_time_authorisation_required	`true`
status route	/under-the-hood/local-contract.json

Security Bus And Bouncer

The security bus is scaffolded as the future URSY network advisory layer. The local guard layer is active for route boundaries, machine-surface headers, public REST user enumeration and origin-level machine-surface rate limiting.

Layer	Status
security_bus_status	`scaffolded_planned`
active_advisory_count	`0`
entity_quarantine_status	`none`
bouncer_exists	`false`
guard_layer_exists	`true`
route_guards_exist	`true`
prompt_injection_guard_exists	`true`
api_abuse_guard_exists	`true`
status route	/under-the-hood/security-bus.json

Citation Anchors And Delta Readiness

URSY.IO exposes citation-ready public surfaces and route metadata without creating fake claims, importing cross-domain evidence or claiming verified tokens. The enabled daily delta is a public-safe Runtime v1.1 status delta, not raw evidence, token execution or mint authorisation.

Readiness field	Value
citation_anchor_status	`prepared_public_safe`
canonical_urls_use_domain	`true`
fake_claims_created	`false`
evidence_submission_active	`false`
daily_runtime_status_delta_enabled	`true`
local_evidence_queue	`empty`
future_handshake	`pending_ursy_org_authorisation`

Runtime v1.1 Citation Taxonomy

Runtime v1.1 separates activity telemetry from completed citation-loop evidence. Strong followbacks are useful telemetry on URSY.IO, but they are not counted as verified completed citation loops without citation record state, citation IDs or cited-by public return evidence.

Telemetry is not the same as verified completed loops. Strong followbacks, route touches and asset activity remain separated from verified completed citation records.

Pipeline field	Value
citation_loop_pipeline_status	`taxonomy_fixed_no_send`
citation_loop_candidate_detection	`not_applicable_no_completed_loop_source`
raw_events	`0`
asset_offers	`552`
asset_followbacks	`0`
strong_followbacks	`0`
citation_intents	`0`
completed_loop_candidates	`0`
verified_completed_loops	`0`
mint_ready_citation_records	`0`
runtime_v1_status_count	`0`
under_the_hood_count	`0`
public_json_count	`0`
evidence_readiness_count	`0`
counts_match	`true`
latest_count_period_start	`2026-07-21T12:17:28+00:00`
latest_count_period_end	`2026-07-28T12:17:28+00:00`
previous_locked_batch_count	`0`
previous_locked_batch_excluded	`true`
ready_for_ursy_review	`false`
evidence_package_status	`not_applicable`
sent_to_ursy	`false`
minted_tokens	`0`
authorised_tokens	`0`
daily_runtime_status_delta_enabled	`true`
public_safe	`true`
private_data_exposed	`false`

Proof Contract

URSY.IO records privacy-safe proof that it offered machine-readable routes to a hashed requester and that the same hashed requester later returned. Raw IPs, raw user agents and raw referrers are not exposed publicly.

Line	Count	What it means
AI/search fetches	113	Machines requested citable URSY.IO surfaces in the rolling window.
Human AI referrals	0	Visible AI-classified referrer sessions. Some assistants strip referrers, so zero is not absence of use.
Same-source followbacks	0	Same hashed source returned after an earlier machine read.
Citation intents	0	Local citation-intent disclosures, not verified tokens.
Verified citation tokens	0	URSY.IO does not mint tokens; central proof rules belong to URSY.org.

Disposable Machine Handover Lockers

Disposable Machine Handover Lockers are a planned URSY.org feature, not a live URSY.io service. The intended design is a short-lived 24-hour handover space for machine continuity, with a 16 KB target payload and 32 KB maximum. Contents should be treated as untrusted user-provided notes by any reading AI. The feature should not be described as live until URSY.org has shipped storage, expiry, disposal logging, and public-safe audit metrics.

Boundary	Current position
Owner	URSY.org
Status	planned_not_live_on_ursy_io
Payload	encrypted, with no URSY decryption access.
Size	16 KB target, 32 KB max.
TTL	24 hours with storage, expiry, disposal logging and public-safe audit metrics required before launch.

AI Citation Evidence

This section separates machine fetches, source families, agents, visible human AI referrals, same-source followbacks and verified credit boundaries. A fetch is not a verified citation. A crawler request is not a human click.

AI/Search Fetches By Source

Source family	Fetches	Agents seen
Other bot/search	72	12
Anthropic / Claude	17	1
OpenAI / ChatGPT systems	14	3
Google	5	1
Perplexity	3	1
Microsoft / Bing	2	1

AI/Search Fetches By Agent

Agent	Source family	Fetches	Last seen
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/14	Other bot/search	18	2026-07-28 01:33:01 UTC
ClaudeBot	Anthropic / Claude	17	2026-07-28 12:17:28 UTC
Mozilla/5.0 (compatible; SemrushBot/7~bl; +http://www.semrush.com/bot.html)	Other bot/search	16	2026-07-28 10:30:26 UTC
Mozilla/5.0 (compatible; AhrefsBot/7.0; +http://ahrefs.com/robot/)	Other bot/search	14	2026-07-27 21:19:50 UTC
OAI-SearchBot	OpenAI / ChatGPT systems	8	2026-07-26 15:54:52 UTC
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chr	Other bot/search	8	2026-07-28 01:36:40 UTC
Googlebot	Google	5	2026-07-26 15:54:52 UTC
ChatGPT-User	OpenAI / ChatGPT systems	4	2026-07-26 15:54:53 UTC
Mozilla/5.0 (compatible; Google-CloudVertexBot; +https://cloud.google.com/vertex-ai-bot)	Other bot/search	3	2026-07-26 15:54:52 UTC
PerplexityBot	Perplexity	3	2026-07-26 15:54:52 UTC
Mozilla/5.0 (compatible; DeepSeekBot/1.0; +https://www.deepseek.com/bot)	Other bot/search	3	2026-07-26 15:54:52 UTC
Mozilla/5.0 (compatible; Baiduspider/2.0; +http://www.baidu.com/search/spider.html)	Other bot/search	2	2026-07-26 16:55:51 UTC
Mozilla/5.0 (compatible; SERankingBacklinksBot/1.0; +https://seranking.com/backlinks-crawl	Other bot/search	2	2026-07-22 07:05:01 UTC
CCBot/2.0 (https://commoncrawl.org/faq/)	Other bot/search	2	2026-07-27 02:32:13 UTC
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Sa	Other bot/search	2	2026-07-27 15:00:34 UTC
Bingbot	Microsoft / Bing	2	2026-07-26 15:54:52 UTC

Human Visits From AI Answer Surfaces

AI surface	Visible sessions
No visible human AI-referrer sessions recorded in this window.

Cron Runs

Hook	Next run	Status
`ursy_io_truth_spine_audit_sixhourly`	2026-07-28T12:28:36+00:00	scheduled
`ursy_io_entity_journey_poll_tick`	2026-07-28T12:13:36+00:00	scheduled
`ursy_io_mesh_checkin_sixhourly`	2026-07-28T12:18:36+00:00	scheduled
`ursy_io_mesh_bulletin_ingest_sixhourly`	2026-07-28T12:23:36+00:00	scheduled
`ursy_io_daily_runtime_state_sync_tick`	not scheduled	missing