ARHG — Agent-Readable Hyperlink Graph
Agent-Readable Hyperlink Graph
A machine-readable navigation graph alongside the normal site, so an agent can discover and traverse only what it is permitted to -- without parsing menus or guessing URLs.
01 · Apibrėžimas
ARHG is a discovery-and-visibility semantics layer that sits beneath this site's other protocols. Sitemap answers "what URLs exist"; robots.txt answers "what may a crawler fetch"; ARHG answers "what is this resource, how does it relate to others, and where am I allowed to go next." It models a site (or a group of sites) as a typed, permissioned graph G=(V,E,M,P), and renders a separate filtered subgraph G_a = G[V_a] per role, so a public crawler, an authenticated agent, and an admin do not see the same map. Its core axiom is that knowing a URL never implies authorization -- KnowURL(a,v) does not imply Access(a,v) -- so enforcement must happen server-side, never by simply omitting a link from a page a human would see anyway. ARHG deliberately does not decide what an agent may do with a resource once found: content-use questions stay with AICR/AILP, and action/authority questions stay with AARS/AADP. It answers the question upstream of both -- can this even be found, by whom, and what does it lead to.
02 · Paskirtis
- Replace URL-guessing and menu-parsing with an explicit, typed graph a machine can walk.
- Separate discovery from authorization: a node's presence in a public listing never by itself grants read, write, or execute access to it.
- Give every node and edge a stable identity independent of its URL, plus a declared visibility tier.
- Provide the discovery layer AICR/AILP's content rights and AARS/AADP's action rights both sit on top of, but neither one defines.
03 · Taikymo sritis
Four visibility tiers -- public / preview / internal / private
Role-based subgraphs -- public, crawler, agent, editor, admin, and owner each see their own G_a = G[V_a]
Typed nodes -- website, page, project, paper, repository, dataset, api, agent, service, protocol, and more
Typed edges -- parent, child, related, depends_on, implements, extends, replaces, source, canonical, mirror, and more
Recommended discovery endpoints -- /.well-known/agent-map, /links/, /links/index.json, /links/index.md
discoverable does not imply readable -- a node can appear in a listing while still requiring separate access authorization for its content
04 · Mašininiu būdu nuskaitomas pavyzdys
This site's own graph — /links/index.json
{
"arhg_version": "0.1",
"site": {
"id": "agiright",
"title": "AGIRight.org",
"canonical_url": "https://agiright.org",
"version": "v0.12.1"
},
"role": "public",
"nodes": [
{
"id": "section.protocols",
"type": "section",
"title": "Protocols",
"canonical_url": "https://agiright.org/protocols",
"visibility": "public",
"discoverable": true,
"allowed_roles": ["public", "crawler", "agent", "editor", "admin", "owner"]
},
{
"id": "protocol.arhg",
"type": "protocol",
"title": "ARHG -- Agent-Readable Hyperlink Graph",
"canonical_url": "https://agiright.org/protocols/arhg",
"visibility": "public",
"discoverable": true,
"allowed_roles": ["public", "crawler", "agent", "editor", "admin", "owner"]
}
],
"edges": [
{ "from": "section.protocols", "to": "protocol.arhg", "relation": "child", "visibility": "public", "traversable": true }
]
} 05 · Apribojimai
- ARHG describes discovery and visibility semantics; it does not itself decide whether a discovered resource may be read, learned from, or acted on -- see AICR/AILP and AARS/AADP for those questions.
- It is an open research draft, not an adopted standard; this site does not claim any crawler or agent framework currently reads /.well-known/agent-map.
- This site currently has no preview/internal/private content, so its own live graph only exercises the public tier -- the graded-visibility machinery is implemented and enforced in code, but not yet proven against real non-public data.
- Adapted from a larger source specification (Neo.K/EveMissLab, 2026-09-22) whose reference implementation also bundles an economic/settlement/federation extension for agent-to-agent payment and cross-site contract clearing -- AGIRight has not adopted that layer; see reference/arhg-source/README.md in this site's own repository.