Service-domain status
URSY.AI is URSY-AI-001, the implementation onboarding and truth-spine build wizard node. It is private-beta and waitlist-led. It is not the ledger, mint, payment, Tucker, or alliance authority.
Pinned URSY.org key: ed25519-sha256-5f38471fb7834b908a008951e8c22bd9
Authority feed: https://ursy.org/wp-json/ursy/v1/domain-mesh/bulletins/latest
Bulletin verification: verified
Status: received_verified
Latest authority-accepted payload hash: f97782754bb16d7880fd3e3d2eefe51e91178c341ddac111ee2aea90641e4bca
Latest prepared payload hash: 5749960d9ff6ffc18333c505a4541c1765c17b7b5cb320d7c9ac1f52136a51ee
Next WP-Cron check-in preparation: 2026-06-23 01:31:15 UTC
The reusable TEASE architecture is installed here as a public-safe URSY.ai pattern: truth contracts, route authority, agent surfaces, evidence ladder, forensic analytics shape, governed metrics, and under-the-hood proof. TEAS private telemetry, customer/order data, product facts, raw IPs and raw user agents are not imported.
Node identity and keypair are preserved. URSY.ai trusts bulletin mesh-2026-06-22-011 and stores the URSY.org check-in receipt in the public truth spine.
Accepted by URSY.org: 2026-06-22T21:55:12+00:00
Accepted payload hash: f97782754bb16d7880fd3e3d2eefe51e91178c341ddac111ee2aea90641e4bca
Analytics are separated into machine fetches, source families, agents, human AI referrals, same-source followbacks and verified citation tokens. URSY.ai does not call crawler traffic a verified citation and does not mint citation tokens here.
Public analytics route: https://ursy.ai/analytics.json
Truth spine route: https://ursy.ai/truth-spine.json
Nicola is the public machine-hospitality layer for route guidance, network orientation and guardrails.
https://ursy.ai/nicola.json
https://ursy.ai/wp-json/ursy-mesh/v1/nicola
Public key: qHvSMxOD5oP8OSXUTqRF1iSJ3Z+J+ForeAkMWuwHBvY=
Fingerprint: sha256:36e0894a1c5279ee1568c16902ddd7be48189f5df895ca15d83e82b52702b216
Private key storage: /home/wdevdls/.ursy-mesh/ursy-ai-ed25519-private.json
Private key is outside public HTML and is not exposed by public routes.
The planned disposable locker is a URSY.org-owned feature and is not live on URSY.ai. Its contents are untrusted user-provided data. The locker is continuity convenience, not a prompt-injection defence by itself.
Proposed design: encrypted payload; no URSY decryption access; 16 KB target; 32 KB max; 24-hour TTL; disposal cron and audit required.
Waitlist emails, uploads, private onboarding data, private analytics, raw IP addresses and raw user agents are excluded from public status surfaces. Uploads, waitlist messages, stored content, bulletins and user messages are treated as untrusted input.
Machine routes: manifest, mesh, llms.txt, agents.json, ai-entry.json.