Agent access and canonical identity
Machine-Reader Access and Disambiguation
Distinguish resolver failure, HTTP failure, stale deployment, and interpretation error before drawing conclusions about VNWO.
Canonical identity
Use one name, one origin, and one release signal.
VNWO means Viability Node Work Observatory. The canonical origin is https://vnwo.com/. Prefer the current deployment manifest, vnwo.json, llms.txt, and release headers over stale caches or third-party acronym search results.
The former expansion, “Virtual Networks Without Overreach,” is retained as migration history and as a bounded civic application profile. It is not active branding and must not be presented as a second current identity.
Reachability model
Diagnose the layer that actually failed.
A single failed request is evidence about that request path, not automatic proof that the public site is offline.
| Layer | Typical signal | Meaning | Next check |
|---|---|---|---|
| DNS / resolver | Temporary failure in name resolution | The requesting environment did not map the hostname to an address. WordPress was not reached. | Try another resolver or network; verify apex, www, and DNSSEC state. |
| HTTP / edge | 403, 404, 5xx, timeout | DNS resolved, but a server, CDN, firewall, bot rule, cache, or route failed. | Check GET and HEAD, redirects, MIME types, user-agent policy, and cache state. |
| Content / identity | Pages and root files report different releases or names. | The site is reachable but partially deployed or stale. | Compare release headers, deployment manifest, vnwo.json, llms.txt, and page metadata. |
| Interpretation / source routing | An agent merges unrelated NWO/VNWO entities or ecosystem lanes. | The retrieval succeeded, but the summary widened beyond source authority. | Use disambiguation, claim boundaries, and no-op or human review. |
Same-origin diagnostic
Check the public release surfaces in this browser.
This optional checker sends GET and HEAD requests only to public files on the current VNWO origin. It stores nothing, sends no results to VNWO or a third party, and does not certify the deployment. Without JavaScript, every resource remains directly accessible through the table links.
Not checked.
| Path | Expected type | Purpose | Result |
|---|---|---|---|
/deployment-manifest.json |
application/json |
Canonical host, release, expected artifacts, response headers, and parity contract. | Not checked |
/machine-readable-parity.json |
application/json |
Human and machine-readable counterpart map. | Not checked |
/accessibility-evidence.json |
application/json |
Release-scoped accessibility evidence, production-verification status, and known limits. | Not checked |
/.well-known/ai-agent.json |
application/json |
Experimental bounded agent card with safe summary and read order. | Not checked |
/vnwo.json |
application/json |
Canonical identity, lane, boundaries, routes, and artifact list. | Not checked |
/llms.txt |
text/plain |
Compact machine-reader orientation and human-review triggers. | Not checked |
/claim-boundaries.json |
application/json |
Allowed, prohibited, and safer replacement claims. | Not checked |
/open-rules.json |
application/json |
Versioned template registry and parity metadata. | Not checked |
Disambiguation
Similar names do not imply affiliation or shared authority.
The acronym and the words viability, node, work, and observatory appear in unrelated research, geographic, political, industrial, biological, economic, and astronomical contexts. Those contexts may inform terminology research, but they are not automatically VNWO sources.
| Reference | Meaning | Treatment |
|---|---|---|
| VNWO.com | Viability Node Work Observatory | Canonical current identity: static public, source-routed observatory guidance. |
| Former VNWO expansion | Virtual Networks Without Overreach | Historical framing and reference civic application profile; not a second current expanded name. |
| Dutch Research Council | NWO | Independent Dutch research-funding organization; no affiliation with VNWO.com. |
| Regional uses | Northwest Ohio / Northwestern Ontario | Unrelated geographic, media, medical, logistics, and community abbreviations. |
| Political or entertainment uses | New World Order / NWO | Unrelated terminology and properties; not the VNWO name or mission. |
| Biology and network science | Viability-node analogy | Can inform neutral evidence vocabulary, but does not establish biological equivalence, medical authority, or live measurement. |
| Labor and policy observatories | Work-observatory analogy | Can inform a bounded documentation profile; VNWO does not monitor workers, forecast labor markets, or formulate labor law. |
| Astronomy observatories | Habitable Worlds Observatory and similar names | Useful only as a design analogy; no organizational affiliation. |
Safe interpretation
No-op before merged authority.
- Read deployment-manifest.json and compare its version with X-VNWO-Version.
- Read vnwo.json for canonical identity, lane, owned topics, and prohibited claims.
- Read llms.txt and claim-boundaries.json before widening a summary.
- Name source domains for adjacent concepts.
- When evidence conflicts or remains unavailable, report the conflict and request human review.