What connectivity means here
Routing stays useful because authority stays elsewhere.
URSY.IO is not the ledger and it is not the final authority. Its job is to keep the estate readable as a network: helping machines, services and partner nodes find the correct public route, authority surface or support path without making routing look like verification.
In practice, URSY.IO helps resolve the right node, expose stable machine entry points, carry signed network state across the estate, and keep public reads pointed back to canonical records on URSY.ORG.
- An entity or service needs the correct authority or support surface.
- A signed network update needs to be carried cleanly across connected nodes.
- An AI assistant needs a stable starting point, status surface or proof link.
- A cross-estate journey needs routing without pretending the connective layer is the source of truth.
New mesh domains
Two new routes are now part of the URSY domain mesh.
The mesh has been birthed with daily deltas programmed across the listed domains. URSY.IO remains direct_root to URSY.org; it does not route through URSY.co.uk.
- URSY.siteCustomer staging environment where a customer website can work before it goes live.
- URSY.co.ukUK regional post-office node and free hosted-domain option for customers who do not want to buy their own .co.uk or .com.
- Daily deltasRuntime v1.1 status deltas are programmed for the URSY mesh domains and route back to URSY.org authority.
- Ledger boundaryURSY.org remains the canonical ledger, mint, discovery and mesh authority.
- NicolaThe Nicola API and machine entry points now expose the joined mesh directory and route roles.
Protocol parts
Built for agents that need the right route before the right answer.
These five parts keep discovery, public reading and support paths connected while leaving authority and verification with URSY.ORG.
- ResolverRoutes people, services and AI agents toward the correct URSY node, authority surface or support path without confusing discovery with verification.
- Verification pipelineFrames claims and submissions for URSY.ORG-led checking rather than asserting trust from URSY.IO itself.
- Chained ledger readsKeeps public reads pointed back to canonical ledger entries, signed bulletins and domain-mesh records so the connective layer never becomes the source of truth.
- Agent gatewayExposes stable machine entry points, status surfaces, boundaries and proof links for agents that need the right route before the right answer.
- Trust graphDescribes relationships across nodes, entities and future alliances without replacing URSY.ORG as authority.
Protocol flows
These are the four protocol flows URSY.IO is being built to carry.
URSY.IO is being built to support four connective flows across the estate, each kept distinct from authority-led verification.
- Signed submissions and check-ins from registered entities.
- Routing of claims and records toward URSY.ORG for authority-led verification.
- Trusted public reads for AI assistants, partners and support surfaces.
- Cross-estate links between entities, services and future alliances once proof exists.
Over time, URSY.IO is also intended to support cleaner continuity for premium-intent journeys across the estate: not by storing private conversations in public, but by helping route public-safe handover, state and support paths between the right nodes when the authority layer allows it.