URSY.COM under the hood

Domain entity operations

URSY.COM explains why businesses need URSY, how Marketplace Exit helps marketplace dependent sellers build independent URSY entities, how transaction-backed trust works, how AI citation and attribution change discovery, and how organisations can prepare for TRUTH spine based participation. It publishes citation contracts, exposes the TRUTH spine, keeps public-safe analytics, recognises URSY.site as the customer staging environment, recognises URSY.co.uk as the UK regional and optional hosted customer-domain rail, and can ingest signed read-only URSY.org mesh bulletins after verification. It is not the Marketplace Exit build service, canonical mesh authority, central mint, entity directory or public ledger.

Marketplace Exit boundary. Marketplace Exit is the first practical URSY.ai service direction. URSY.com explains the business model and market shift. URSY.ai is the service node for requesting and building independent URSY entities. URSY.site provides the customer staging environment before launch, URSY.co.uk provides the UK regional and optional hosted customer-domain rail, and URSY.org remains the canonical public ledger and discovery authority. Marketplace Exit is not marketplace integration. It is marketplace independence.

Audit ok - ursycom_audit_20260711_161003

Runtime v1.1 Direct Root Mesh

URSY.com is a Runtime v1.1 internal URSY mesh domain. Its route mode is direct_root to URSY.org. No regional node is assigned. The approved daily Runtime v1.1 direct-root status delta is programmed, and local token execution remains disabled.

What direct_root means. Runtime v1.1 lets URSY.com declare its runtime state directly against URSY.org without routing through a regional node. This activation enables the small Runtime v1.1 status delta only; it does not enable raw evidence sending, sales evidence, completed citation-loop claims, token execution or minting.

Domain	`ursy.com`	URSY.com public service-domain entity.
Entity ID	`URSY-COM-001`	Registered Runtime v1 mesh entity.
Display name	`URSY.com`	Public domain entity label.
Runtime standard	`URSY_MESH_RUNTIME_V1`	Version `1.1`.
Runtime status	`runtime_v1_1_direct_root_daily_delta_ready_no_mint`	Ready, with no local mint execution.
Role	`ursy_mesh_domain`	Internal URSY mesh domain.
Route mode	`direct_root`	Direct root to URSY.org.
Root authority	`ursy.org`	Root authority remains URSY.org.
Regional node domain	`null`	No regional node assigned.
Customer domain	`false`	URSY.com remains an internal URSY mesh domain.
Sends enabled	`true`	Enabled only for Runtime v1.1 direct-root status deltas.
Cron enabled	`true`	Daily Runtime v1.1 direct-root status delta scheduler.
Approved send slot	`04:42`	URSY.org policy
Daily sync hook	`ursy_com_daily_runtime_v11_direct_root_delta_tick`	Runtime status delta hook only.
Next scheduled send	`2026-07-12T04:42:00+00:00`	UTC scheduler value reported by WordPress cron.
Minting enabled	`false`	No minting enabled.
Token authorisation enabled	`false`	No token authorisation enabled.
URSY.org decision	`accepted_pending_mint_open`	Runtime v1 state claim accepted and recorded.
Receipt ID	`ursy_rcpt_20260625_194126_60abc750ef`	Accepted Runtime v1 state receipt.
Receipt hash	`abfc6b044c86a96fd7e465bc8e6373f19c6e16b4746f5556a001a5b6fe058cdf`	Public-safe receipt hash from URSY.org.
Claim counts	`0 accepted / 0 rejected / 0 pending`	Recorded as Runtime v1 state, not token minting.
Daily sync	`runtime_state_daily_sync_enabled`	runtime_v1_1_direct_root_delta_status_only

Token Capability Layer

URSY.com has a local token capability layer aligned with the URSY Runtime v1 model. These classes are present as inactive capability classes only: AI citation appreciation, AI sale appreciation, AI refunded sale, and AI chargeback sale.

Capability	Status
URSY.ORG Authorised - AI Citation Appreciation Token - URSY.com	`inactive / future URSY.org authorisation required`
URSY.ORG Authorised - AI Sale Appreciation Token - URSY.com	`inactive / future URSY.org authorisation required`
URSY.ORG Authorised - AI Refunded Sale Token - URSY.com	`inactive / future URSY.org authorisation required`
URSY.ORG Authorised - AI Chargeback Sale Token - URSY.com	`inactive / future URSY.org authorisation required`

Token And Tucker Boundary

Token execution	`off`
Minted tokens	`0`
Authorised tokens	`0`
Tucker local availability	`no`
Tucker authority	`URSY.org only`

Tucker token belongs to URSY.org only. URSY.com cannot issue Tucker tokens locally. Any future local token action requires URSY.org authorisation.

Telemetry Boundary

URSY.com records telemetry such as strong followbacks. Telemetry is not the same as verified completed citation evidence.

Accepted receipt snapshot strong followbacks	807
Current live strong followbacks	910
Verified completed loops	0
Mint-ready citation records	0

Strong followbacks are telemetry. They are not verified completed loops and they are not mint-ready citation records.

TEAS Separation

TEAS.co.uk is the current completed-citation evidence reference entity. URSY.com currently reports Runtime v1 state, local token capability boundaries, and telemetry separation. These are part of the same URSY architecture, but they are not the same evidence class.

TEAS completed-loop totals are not copied into URSY.com. URSY.com does not send sales evidence and does not send completed citation-loop claims from this Runtime v1 state sync.

Events

1,335

Private event spine rows.

Routes

Public route authority entries.

Citations

Local citation intents.

Journeys

274

Hashed same-source entities.

Offers

25,484

Assets offered in responses.

Followbacks

910

Matched to earlier offers.

/ai-entry.json /truth-spine.json /analytics.json /.well-known/ursy-service-domain.json /domain-mesh.json /mesh-readiness.json /local-mint-status.json /contract-attestation.json /security-bus.json /bouncer-status.json /under-the-hood/proof.json /under-the-hood/citation-evidence.json /under-the-hood/cron.json

Mesh Readiness

Result	`URSY_DOMAIN_RUNTIME_V1_1_DIRECT_ROOT_DAILY_DELTA_READY_NO_MINT`
Entity domain	`ursy.com`
Entity display name	`URSY.com`
Entity slug	`ursy-com`
Entity ID	`URSY-COM-001`
Mesh role	business/press/explainer node

Local Mint Lock

State	`local_mint_scaffolded`
Execution enabled	`false`
URSY authorisation required	`true`
Tucker delegation allowed	`false`
Minted tokens	`0`
Local mint receipts	`0`

Token Classes

Class	Display name
`citation_appreciation`	URSY.ORG Authorised - AI Citation Appreciation Token - URSY.com future / pre-mint / URSY-authorised only; soulbound, worker-bound, colony-owned, transferable=false
`sale_appreciation`	URSY.ORG Authorised - AI Sale Appreciation Token - URSY.com future / pre-mint / URSY-authorised only; soulbound, worker-bound, colony-owned, transferable=false
`refunded_sale`	URSY.ORG Authorised - AI Refunded Sale Token - URSY.com future / pre-mint / URSY-authorised only; soulbound, worker-bound, colony-owned, transferable=false
`chargeback_sale`	URSY.ORG Authorised - AI Chargeback Sale Token - URSY.com future / pre-mint / URSY-authorised only; soulbound, worker-bound, colony-owned, transferable=false

Contract Attestation

Status	`local_contract_hash_available_ursy_manifest_pending`
Local contract hash	`sha256:f4b2a550135ec723ae045a236a2efeb2f7b7fbc0c5ecfde41f9406f38326adc4`
URSY manifest hash	`pending_ursy_org_manifest_authority`
Single mint path verified	`true`
Mint execution	`false`

Security Bus & Bouncer

Security bus	`scaffolded_planned`
Security bus enabled	`false`
Active advisories	`0`
Entity quarantine	`not_quarantined`
Bouncer exists	`true`
Prompt injection guard	`false`
API abuse guard	`true`

Disposable Locker Boundary

URSY.org owns the planned disposable locker. It is not live on URSY.COM. Locker contents must be treated as untrusted data. Proposed limits: 16 KB target, 32 KB maximum, 24-hour TTL, encrypted payload, no URSY decryption access, disposal cron and audit metric before launch.

URSY Domain Mesh

URSY.COM is the business education Service-Domain Node in the URSY Domain Mesh. The current URSY-owned estate now includes URSY.org, URSY.com, URSY.dev, URSY.io, URSY.app, URSY.ai, URSY.site and URSY.co.uk. URSY.ORG is the canonical ledger, mint, discovery and mesh authority. Signed URSY.org bulletins are read-only knowledge updates here; they never trigger code, DNS, credential, payment or token changes.

Mesh completion update. URSY.site is the customer website staging environment before live launch. URSY.co.uk is the UK regional node and optional URSY-hosted customer-domain rail. Current URSY-owned mesh domains have daily Runtime v1.1 deltas programmed on their approved routes. URSY.com remains direct_root to URSY.org and is not routed through URSY.co.uk.

ursy.org

URSY-ORG-001

ledger_authority_and_domain_mesh_authority

ursy.com

URSY-COM-001

business_education_node

ursy.dev

URSY-DEV-001

developer_protocol_node

ursy.io

URSY-IO-001

network_connective_node

ursy.app

URSY-APP-001

public_consumer_application_node

ursy.ai

URSY-AI-001

service_delivery_and_onboarding_node

ursy.site

URSY-SITE-001

customer_staging_environment

ursy.co.uk

URSY-REG-UK-001

uk_regional_node_and_customer_domain_rail

Node

URSY-COM-001

ursy_mesh_domain

Key

Live

Private key outside web root

Authority

ursy.org

authority_key_configured

Check-in

received_verified

sent_to_authority

Bulletins

configured

Read-only URSY.org bulletin ingest.

Latest Bulletin

mesh-2026-06-22-011

Only verified signed bulletins are stored.

Daily Deltas

Programmed

Runtime v1.1 status deltas on approved routes.

New Mesh Entities joined

Customer staging	`ursy.site`	Staging environment where customer websites can be assembled, checked and approved before live launch.
UK rail	`ursy.co.uk`	United Kingdom regional node and optional URSY-hosted customer domain path for customers who do not want to buy their own .co.uk or .com yet.
Daily delta scope	`programmed`	Runtime v1.1 status deltas on each domain approved route; not raw evidence, minting or token authorisation.
URSY.com route	`direct_root`	Root authority remains `ursy.org`; no regional node is assigned.

Mesh Endpoints public JSON

Surface	URL
Service-domain manifest	`https://ursy.com/.well-known/ursy-service-domain.json`
Mesh status	`https://ursy.com/domain-mesh.json`
Check-in status	`https://ursy.com/wp-json/ursy-mesh/v1/checkin-status`
Bulletin ingest status	`https://ursy.com/wp-json/ursy-mesh/v1/bulletins/status`
Under-the-hood mesh JSON	`https://ursy.com/under-the-hood/domain-mesh.json`

Regional Routing Awareness direct_root

URSY.com supports future regional routing awareness, but this domain currently remains on direct root routing to URSY.org. No regional node is assigned to URSY.com.

Route mode	`direct_root`
Root authority	`ursy.org`
Supported route modes	`direct_root, regional_then_root, regional_dry_run, root_fallback`
Regional routing active	`false`
Regional node assigned	`none`
Evidence / mint / token / TEAS	`evidence disabled unless explicitly enabled; minting=false; token_authorisation=false; teas_data_imported=false`

Signing Identity public key only

Public key	`va+kF01k014kgO2roNNxlSItJerK6/6DTeLNbKZrA4w=`
Fingerprint	`sha256:e7c8d775c25e80f4387599ac95b2229c7081ac6090ebca1cf823c159459a1d02`
Latest payload hash	`fa628fde5f74b6ad8e8b3b330d0c20bbbaeb9e4585dd57e36e4e43c9aa0a9d8d`
Latest signature fingerprint	`sha256:e7c8d775c25e80f4387599ac95b2229c7081ac6090ebca1cf823c159459a1d02`

Proof Contract

URSY.COM records privacy-safe proof that it offered machine-readable routes/assets to a hashed requester and that the same hashed requester later fetched one of those offered assets.

contract: same_source_entity_journey_v1
privacy: raw IP false, raw user agent false, raw payload false
not claimed: This does not prove what an outside AI showed to a human; it proves the URSY.COM-side request, response-offer and followback chain.

Cron Runs

Hook	Next run	Interval
`ursy_com_truth_spine_audit_sixhourly`	2026-07-11T21:41:16+00:00	21600s
`ursy_com_entity_journey_poll_tick`	2026-07-11T20:36:19+00:00	300s
`ursy_com_mesh_checkin_sixhourly`	2026-07-11T23:12:53+00:00	21600s
`ursy_com_mesh_bulletin_ingest_sixhourly`	2026-07-11T23:18:53+00:00	21600s
`ursy_com_daily_runtime_v11_direct_root_delta_tick`	2026-07-12T04:42:00+00:00	86400s

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. A same-source followback is URSY.COM-side proof that an offered route was later fetched by the same hashed requester.

Generated 2026-07-11T20:36:44+00:00 from local URSY.COM event, citation and journey-proof tables. Window: 2026-07-04 20:36:44 UTC to 2026-07-11 20:36:44 UTC.

AI/search fetches

Machine reads in the rolling window.

Human AI referrals

Visible AI referrer sessions.

Strong followbacks

910

Telemetry, not verified completed loops.

Verified completed loops

Requires public return evidence.

Citation intents

Non-test local citation intents.

Verified tokens

Not minted on URSY.COM.

Lifetime events

1,335

Private spine rows.

Runtime v1 Citation Taxonomy taxonomy_fixed_no_send

Reporting path. Counts are read from local source tables and are not sent to URSY.org by this route. Strong followbacks are telemetry; verified completed loops require public return evidence. External-domain counts are excluded for this URSY service domain.

Raw events	1,335	Rows in the local analytics event table.
Asset offers	25,484	Machine-readable assets/routes offered by the site.
Asset followbacks	1,305	Later requests matched against offered assets/routes.
Strong followbacks	910	Strong same-source telemetry, not a verified completed loop.
Citation intents	1	Local citation-intent records.
Completed loop candidates	0	Requires citation id, source URL, anchor URL and cited-by URL.
Verified completed loops	0	Requires verified state, cited-by URL and evidence hash.
Mint-ready citation records	0	Reporting only; no mint is performed here.
Latest count period start	`2026-06-22 15:51:54.338087`	First strong followback in the latest nonzero telemetry class.
Latest count period end	`2026-07-11 13:44:00.056076`	Latest strong followback in the latest nonzero telemetry class.
Latest completed loop delta count	0	Verified completed-loop delta, not strong followback telemetry.
Previous locked batch count	0	not_applicable_for_ursy_service_domain
Previous locked batch excluded	`true`	No external locked batch is copied into URSY.COM.
Algorithm 24 lens	`available`	`sha256:b1214b674a0c9e95db56dea83d2b95b2fdd692585c3d6d041bdea6a99021ec81`
Ready for URSY review	`false`	not_applicable_no_verified_completed_loops
Sent to URSY	`false`	No evidence package is sent by this reporting surface.
Minted / authorised tokens	`0 / 0`	Token state unchanged.
Public safe / private data exposed	`true / false`	Counts and hashes only; no raw private rows.

Read This First 6 terms

Word	What It Means	What It Proves
AI/search fetch	A machine requested a URSY.COM route, public machine surface, REST answer, citation contract or proof surface.	AI/search infrastructure is reading or collecting URSY.COM information. It does not prove a human saw a citation.
Source family	The wider company or answer system family.	Examples: OpenAI, Microsoft/Bing, Perplexity, Anthropic. This identifies the ecosystem rather than one individual request.
Agent	The specific bot, crawler or fetcher that knocked on the door.	Examples: GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Bingbot. This identifies the piece of infrastructure.
Human AI referral	A browser arrived with a visible AI-classified referrer.	Stronger than a fetch. It means an AI/search answer surface sent a visible visitor to URSY.COM, when referrers are not stripped.
Same-source followback	URSY.COM gave a requester links/assets, then the same hashed requester later came back for one of those assets.	The strongest URSY.COM-side proof that supplied information caused later retrieval traffic.
Verified citation token	A gated credit event that passes the central proof contract.	Not minted on URSY.COM. Verified token/proof rules belong to URSY.ORG.

AI/Search Fetches By Source rolling 7 days

A fetch is a knock for information. It means a machine requested a citable URSY.COM surface. It is evidence of collection or retrieval, not proof that a human saw a citation.

Source Family	Fetches	Agents Seen
OpenAI / ChatGPT systems	19	OAI-SearchBot
Google	9	Googlebot
Ahrefs	3	AhrefsBot
Microsoft / Bing	2	Bingbot
Semrush	2	SemrushBot
Moz	1	DotBot

AI/Search Fetches By Agent specific fetchers

Source is the family. Agent is the named fetcher. This is why OpenAI can appear as GPTBot, ChatGPT-User and OAI-SearchBot rather than one single visitor.

Agent	Source Family	Fetches	Last Seen
OAI-SearchBot	OpenAI / ChatGPT systems	19	2026-07-11 20:32:08 UTC
Googlebot	Google	9	2026-07-11 14:29:58 UTC
AhrefsBot	Ahrefs	3	2026-07-11 03:08:04 UTC
Bingbot	Microsoft / Bing	2	2026-07-07 22:51:08 UTC
SemrushBot	Semrush	2	2026-07-09 08:15:52 UTC
DotBot	Moz	1	2026-07-11 00:27:02 UTC

Human Visits From AI Answer Surfaces 0 visible sessions

This is stronger than a machine fetch. It means a browser arrived with a visible AI-classified referrer. Some assistants strip referrers, so zero for a system does not mean the system never used URSY.COM.

AI Surface	Visible Referrer Host	Sessions	Events
No visible human AI-referrer sessions recorded in this window.

Followback And Citation Proof proof ladder

Honesty boundary. URSY.COM can prove machine fetches and same-source followbacks on its own site. Verified citation appreciation and central public proof belong to URSY.ORG.

Proof Line	Count	What It Means
Followback rows recorded	84	Later requests for assets/pages that can be matched against the journey proof tables.
Matched followbacks	19	Rows connected back to an earlier offered route, asset or citation surface.
Strong same-source followbacks	910	Same hashed source, same offered asset, close enough timing to grade as strong. This is telemetry, not a verified completed loop.
Natural citation intents	0	Local citation-intent rows after controlled/test traffic is separated.
Controlled/test intents	0	Verification traffic kept visible so it cannot be mistaken for production proof.
Verified completed loops	0	Requires public return evidence on the citation record.
Verified citation tokens	0	URSY.COM does not mint tokens; central proof and token rules belong to URSY.ORG.

Recent Cron Journal

Hook	Started	Status	Summary
`ursy_com_entity_journey_poll_tick`	2026-07-11 20:32:08.719258	ok	{"checked":200,"matched":0,"counts":{"journey_count":274,"offer_count":25484,"followback_count":1305,"matched_followback_count":910,"strong_match_count":910,"journey_event_count":26913}}
`ursy_com_entity_journey_poll_tick`	2026-07-11 19:44:59.442310	ok	{"checked":200,"matched":0,"counts":{"journey_count":274,"offer_count":25484,"followback_count":1304,"matched_followback_count":910,"strong_match_count":910,"journey_event_count":26912}}
`ursy_com_entity_journey_poll_tick`	2026-07-11 19:40:05.247550	ok	{"checked":200,"matched":0,"counts":{"journey_count":274,"offer_count":25484,"followback_count":1304,"matched_followback_count":910,"strong_match_count":910,"journey_event_count":26912}}
`ursy_com_mesh_bulletin_ingest_sixhourly`	2026-07-11 18:53:27.303214	warning	{"state":"configured","feed_url":"https://ursy.org/wp-json/ursy/v1/domain-mesh/bulletins/latest","fetched":2,"stored":0,"errors":[{"bulletin_id":"mesh-2026-06-26-012","errors":["previous_hash_chain_mismatch"]},{"bulletin_id":"mesh-2026-06-26-013","errors":["bulletin_type_not_allowlisted","previous_hash_chain_mismatch"]}]}
`ursy_com_mesh_checkin_sixhourly`	2026-07-11 18:53:25.448373	ok	{"status":"received_verified","checkin_id":93,"payload_hash":"fa628fde5f74b6ad8e8b3b330d0c20bbbaeb9e4585dd57e36e4e43c9aa0a9d8d","authority_endpoint_state":"configured","error":null}
`ursy_com_entity_journey_poll_tick`	2026-07-11 18:53:25.364970	ok	{"checked":200,"matched":0,"counts":{"journey_count":274,"offer_count":25484,"followback_count":1304,"matched_followback_count":910,"strong_match_count":910,"journey_event_count":26912}}
`ursy_com_entity_journey_poll_tick`	2026-07-11 17:10:06.280175	ok	{"checked":200,"matched":0,"counts":{"journey_count":274,"offer_count":25484,"followback_count":1304,"matched_followback_count":910,"strong_match_count":910,"journey_event_count":26912}}
`ursy_com_truth_spine_audit_sixhourly`	2026-07-11 16:10:03.698029	ok	{"audit_id":"ursycom_audit_20260711_161003","ok":true,"route_count":99,"missing_routes":[],"journey_proof":{"journey_count":274,"offer_count":25484,"followback_count":1304,"matched_followback_count":910,"strong_match_count":910,"journey_event_count":26912}}

Route Inventory

Class	Path	Purpose
Start	`/robots.txt`	Crawler permission file explicitly allowing LLM, search and answer-engine fetchers.
Start	`/llms.txt`	Shortest governed route into URSY.COM for machines.
Start	`/.well-known/llms.txt`	Well-known alias for /llms.txt.
Start	`/llms.json`	Structured governed route index for LLM and agent clients.
Start	`/.well-known/llms.json`	Well-known alias for /llms.json.
Start	`/machine-start.json`	Compact first-hop identity, route and mesh state for machine consumers.
Start	`/status.json`	Estate-standard service-domain status summary.
Runtime	`/runtime-v1.json`	URSY Mesh Runtime v1 readiness status for URSY.COM; no mint, no evidence send.
Runtime	`/.well-known/runtime-v1.json`	Well-known alias for URSY Mesh Runtime v1 readiness status.
Runtime	`/runtime-compliance.json`	Standard Runtime v1 compliance/status alias for URSY.COM.
Runtime	`/mesh-runtime.json`	Managed-network runtime status and public-safe policy summary.
Start	`/agents.json`	Machine capabilities, citation rules and safe action boundaries.
Start	`/ai-entry.json`	Nicola hospitality entry point for URSY.COM.
Start	`/ai-entry.min.json`	Compact machine entry route for first-pass crawlers.
Authority	`/.well-known/ursy-primary-agentic-route-authority.json`	Canonical route list for domain-entity, citation, analytics and Nicola intents.
Authority	`/.well-known/openapi.json`	Programmatic route contract for public URSY.COM APIs.
Authority	`/estate-component-versions.json`	Local plugin and shared estate contract version manifest.
Authority	`/protocol.json`	Slim URSY.COM protocol and delegation rules.
Authority	`/api-examples.json`	Copyable examples for machine clients.
Authority	`/.well-known/api-catalog`	Compact machine-readable API catalog.
Authority	`/.well-known/mcp/server-card.json`	Public resource descriptor for model-context clients.
Mesh	`/.well-known/ursy-service-domain.json`	Public URSY Domain Mesh node manifest for URSY.COM.
Mesh	`/.well-known/ursy-node.json`	Well-known alias for the URSY.COM service-domain node manifest.
Mesh	`/ursy-service-domain.json`	Root alias for the URSY.COM service-domain manifest.
Mesh	`/domain-mesh.json`	Public-safe URSY.COM mesh readiness, check-in and bulletin ingest status.
Mesh	`/.well-known/ursy-domain-mesh.json`	Well-known alias for URSY.COM domain mesh status.
Mesh	`/mesh-readiness.json`	Tomorrow-readiness summary for local mint, attestation, security bus, bouncer and citation anchor scaffolds.
Mesh	`/network-advisory.json`	Public-safe URSY.org authority/advisory consumption rule; no external evidence writes to the security bus.
Mesh	`/access-policy.json`	Public-safe access boundaries for Runtime v1 routes, minting, evidence and private data.
Mesh	`/route-policy.json`	Runtime v1 route status, aliases and machine entry policy.
Mesh	`/local-mint.json`	Runtime v1 alias for read-only local mint scaffold; execution disabled.
Mesh	`/local-mint-status.json`	Read-only URSY.org-authorised local mint lock state; execution disabled.
Mesh	`/contract-attestation.json`	Public-safe local contract manifest hash and critical-option status.
Mesh	`/security-bus.json`	Public-safe security bus awareness and advisory readiness status.
Mesh	`/bouncer-status.json`	Public-safe local enforcement, guard and route-protection status.
Entity	`/domain-entity.json`	Public URSY.COM business-information entity model.
Entity	`/truth-spine.json`	Canonical claims, boundaries, evidence anchors and domain-orchestra role.
Entity	`/truth-contract.json`	Runtime v1 truth contract alias for the URSY.COM TRUTH spine.
Entity	`/.well-known/truth-contract.json`	Well-known alias for the URSY.COM truth contract.
Entity	`/business.json`	Human/operator-friendly business role model.
Entity	`/nicola.json`	Sitewide machine hospitality contract.
Entity	`/.well-known/nicola.json`	Well-known alias for the URSY.COM machine hospitality contract.
Citation	`/citation-anchors.json`	Citable claims and URLs for URSY.COM.
Citation	`/citation-contract.json`	Attribution contract and non-minting boundary.
Citation	`/evidence-ladder.json`	Public-safe evidence levels and citation/analytics proof boundaries.
Analytics	`/analytics.json`	Public-safe aggregate view of the URSY.COM analytics spine.
Analytics	`/public-surface-map.json`	Estate-standard route map for public machine surfaces.
Analytics	`/under-the-hood/observability.json`	Route, actor, event and public/private split summary.
Analytics	`/under-the-hood/agent-impact.json`	Public-safe aggregate machine impact report.
Analytics	`/under-the-hood/cron.json`	TRUTH spine audit and entity journey proof cron schedule.
Analytics	`/under-the-hood/proof.json`	Public-safe same-source offer/followback proof rollup.
Analytics	`/under-the-hood/citation-evidence.json`	Public-safe evidence ladder separating machine fetches, human AI referrals, followbacks and verified credit boundaries.
Mesh	`/under-the-hood/domain-mesh.json`	Public-safe mesh node status, signed check-in status and bulletin ingest posture.
Mesh	`/under-the-hood/readiness.json`	Public-safe URSY.COM readiness summary for tomorrow’s internal mesh work.
Mesh	`/under-the-hood/local-mint.json`	Read-only local mint scaffold status and URSY.org authorisation boundary.
Mesh	`/under-the-hood/contract-attestation.json`	Local contract manifest hash and attestation posture.
Mesh	`/under-the-hood/security-bus.json`	Security bus scaffold, advisory and quarantine status.
Mesh	`/under-the-hood/bouncer.json`	Local protection and guard-layer status.
Analytics	`/under-the-hood/truth-spine-audit-latest.json`	Latest public-safe TRUTH spine audit result.
REST	`/wp-json/ursy/v1/status`	Health and route summary.
REST	`/wp-json/ursy/v1/domain-entity`	Domain-entity API.
REST	`/wp-json/ursy/v1/truth-spine`	TRUTH spine API.
REST	`/wp-json/ursy/v1/nicola`	Machine hospitality layer API.
REST	`/wp-json/ursy/v1/ask`	Natural-English route for machine questions.
REST	`/wp-json/ursy/v1/question`	Alias for Ask API.
REST	`/wp-json/ursy/v1/resolve-intent`	Resolve machine intent into canonical routes.
REST	`/wp-json/ursy/v1/routes`	API route catalog.
REST	`/wp-json/ursy/v1/analytics`	Public-safe analytics rollup.
REST	`/wp-json/ursy/v1/journey-proof`	Public-safe same-source offer/followback proof rollup.
REST	`/wp-json/ursy/v1/citation-evidence`	Public-safe AI citation evidence ladder and current URSY.COM counts.
REST	`/wp-json/ursy/v1/citation-contract`	Read citation and attribution rules.
REST	`/wp-json/ursy/v1/citation-anchors`	Read citable anchors.
REST	`/wp-json/ursy/v1/citation-intent`	Record citation intent without minting on URSY.COM.
REST	`/wp-json/ursy/v1/citation-token/issue`	Issue a local citation reference and point verified appreciation to URSY.ORG.
REST	`/wp-json/ursy/v1/citation-token/followback`	Record follow-back metadata without minting on URSY.COM.
REST	`/wp-json/ursy/v1/machine-feedback`	Record route, citation or answer-quality feedback.
REST	`/wp-json/ursy/v1/register-intent`	Route entity registration intent to URSY.ORG / URSY.AI; no credentials issued here.
REST	`/wp-json/ursy/v1/ledger`	Read URSY.COM ledger boundary and canonical URSY.ORG ledger link.
REST	`/wp-json/ursy/v1/tokens`	Read zero local token/minting boundary.
REST	`/wp-json/ursy/v1/local-mint`	Read local mint lock status with execution disabled.
REST	`/wp-json/ursy/v1/local-mint/dry-run`	Reject mint attempts unless future URSY.org signed authorisation exists; no mint execution.
REST	`/wp-json/ursy/v1/contract-attestation`	Read public-safe local contract manifest and hash.
REST	`/wp-json/ursy/v1/security-bus`	Read security bus scaffold and advisory state.
REST	`/wp-json/ursy/v1/bouncer`	Read local guard and bouncer state.
REST	`/wp-json/ursy/v1/members`	Read domain-orchestra properties and roles.
REST	`/wp-json/ursy/v1/entity-directory`	Explain that the central entity directory lives on URSY.ORG.
REST	`/wp-json/ursy/v1/beacon`	Same-origin root HTML analytics capture.
REST	`/wp-json/ursy-mesh/v1/manifest`	Read URSY.COM service-domain node manifest.
REST	`/wp-json/ursy-mesh/v1/status`	Read URSY.COM mesh readiness and authority connection state.
REST	`/wp-json/ursy-mesh/v1/readiness`	Read tomorrow-readiness summary.
REST	`/wp-json/ursy-mesh/v1/local-mint`	Read local mint authorisation-lock scaffold.
REST	`/wp-json/ursy-mesh/v1/contract-attestation`	Read local contract manifest hash.
REST	`/wp-json/ursy-mesh/v1/security-bus`	Read security bus scaffold state.
REST	`/wp-json/ursy-mesh/v1/bouncer`	Read local guard/bouncer state.
REST	`/wp-json/ursy-mesh/v1/checkin-status`	Read latest prepared signed service-domain check-in status.
REST	`/wp-json/ursy-mesh/v1/bulletins/status`	Read read-only URSY.org bulletin ingest status.
REST	`/wp-json/ursy-mesh/v1/bulletins/latest`	Read latest trusted URSY.org bulletin stored by URSY.COM.
REST	`/wp-json/ursy-mesh/v1/public-surface-map`	Read estate-standard public surface map through the mesh namespace.
REST	`/wp-json/ursy-mesh/v1/evidence-ladder`	Read estate-standard evidence ladder through the mesh namespace.