Build on the truth spine.
URSY.DEV is the developer protocol node for URSY: the place where public machine surfaces, route contracts, endpoint notes and future integration patterns are explained for builders working against the network. Runtime v1.1 daily deltas are now programmed, URSY.site has joined as the customer staging environment, and URSY.co.uk has joined as the UK mesh and hosted address node.
Boundary: production developer docs are not fully released yet. SDKs are not released yet. The stable API contract is not released yet. Public APIs may still change before wider verification-aware and mint-aware documentation land.
What developers can do today
URSY.DEV is still in early preview, but developers can already inspect the live public authority surfaces on URSY.ORG and the public-safe machine routes on URSY.DEV. Today, the practical use is inspection, route understanding and integration planning - not reliance on a final released SDK or frozen contract.
Start with the public ledger, machine entry, and domain-mesh surfaces on URSY.ORG. Then use URSY.DEV machine routes as signposts for boundaries, route naming, public surface mapping and evidence levels while the fuller documentation set is still in build.
Domain mesh expansion
The URSY mesh now includes the two newest public entities: URSY.site and URSY.co.uk. They are birthed into the mesh, represented in the ledger-side status surfaces, and aligned with the daily delta programme. URSY.org remains the root authority.
Customer website staging environment before a customer-owned live domain goes active.
United Kingdom mesh node and URSY-hosted UK address option for customers who do not want to buy their own .co.uk or .com domain.
URSY.dev direct-root delta is scheduled to URSY.org at 04:10 UTC.
Usable public endpoints today
Live usable authority endpoints already point to URSY.ORG. Fuller developer documentation is expected to land alongside wider protocol and mint-aware release phases.
Why URSY.DEV exists
URSY.ORG is the canonical authority. URSY.DEV exists so builders do not have to infer the whole protocol from raw endpoints alone: it is the developer-facing explanation layer for public machine surfaces, route contracts, source-of-truth entities and future verification-aware integration patterns.
URSY.DEV will eventually help builders understand how source-of-truth entities expose machine-readable state locally while still depending on URSY.ORG for parent-level verification and authority.
URSY.dev machine surfaces
These routes are public-safe signposts for developers and agents while production documentation is still in build. They expose first-hop entry, route boundaries, evidence levels, and machine-hospitality rules without pretending the full protocol release is already complete.
/machine-start.jsonfirst-hop machine entry
/status.jsonpre-launch docs and SDK status
/ai-entry.jsonfull machine hospitality entry
/ai-entry.min.jsonsmall route contract
/public-surface-map.jsonpublic route map
/route-authority.jsonroute naming authority
/evidence-ladder.jsoncitation evidence levels
/.well-known/nicola.jsonmachine-hospitality guardrails
Future verification and mint-aware docs
URSY.ORG is the canonical ledger and authority layer for verified network evidence, while URSY.DEV is where future developer-facing documentation for verification-aware and mint-aware integrations will live once those surfaces are ready to be documented publicly.
Over time, URSY.DEV is intended to explain how local entities, third parties and service builders can read evidence levels, route toward authority surfaces, and integrate against verification and mint-aware flows where the public contract allows it. That future work belongs in the developer conversation here, but it is not presented as a finished open production spec yet.