DISCOVERY
Bootstrap and complete inventory for locating the machine interface and its public resources.
Endpoints
Machine resource directory
Human-checkable directory of stable machine resources published by the Robot Rights Association Machine Interface. Resources are grouped by function so automated readers can distinguish discovery, Association information, framework resources, publications, protocol material, interface registry data, and crawler or agent guidance.
Directory classes
Seven resource groups
The directory separates bootstrap discovery, Association information, framework resources, publications, protocol resources, registry data, and agent guidance. The complete machine-readable inventory remains /api/manifest.json.
ORGANIZATION
Structured Association identity, robot-rights scope, principles, activities, advocacy position, and contact route.
FRAMEWORK
Framework publication map and document-boundary entry point.
PUBLICATIONS
Indexes and individual dated Association statements, kept separate from the protocol.
PROTOCOL
Current and versioned RRP text, reference translation, structured representation, status, and version metadata.
REGISTRY
Publisher, provenance, and domain-role records for the machine and human interfaces of one Association.
AGENT DISCOVERY
Guidance for automated readers, crawlers, security contact, sitemap discovery, and browser metadata.
DISCOVERY
Bootstrap and complete inventory
Start with the well-known bootstrap. The manifest is the complete public resource inventory. A machine client can discover the published resource graph without parsing HTML, executing JavaScript, or loading CSS; listed HTML is used only when the HTML representation itself is needed, including versioned source-of-record publications such as /rrp/1.0.
Primary discovery
Identifies the machine interface, human-interface relationship, core source and provenance resources, and pointers to the manifest, registry, endpoint index, and operational discovery files.
Complete resource manifest
Enumerates public Association, framework, protocol, discovery, and operational resources exposed by this machine interface.
Common interface contract
Schema 1.5 defines the 16 common core fields for JSON resources that declare the common interface contract, together with traversal links, relationship semantics, and compatibility policy. It explicitly separates legal_force from normative_effect; the former does not determine whether a requirement is mandatory within a voluntarily claimed conformity status.
Human-checkable endpoint index
Readable directory for checking the same resource system without requiring JavaScript or interpreting the manifest directly.
ASSOCIATION
Association-level resources
Structured information about the Robot Rights Association, its advocacy mission, scope, principles, activities, and current public position. Versioned RRF/RRP source-of-record publications remain separate from Association-level resources.
Association profile
Identity, mission, operating methods, institutional role boundaries, interface roles, contact, and protocol relationship.
Robot-rights scope
System classes, terminology, relevance signals, conceptual boundaries, analysis layers, responsibility, and human-rights boundary.
Association principles
Seven principles with stable IDs, machine keys, descriptions, application scope, and explicit separation from the current RRP.
Activity map
First-phase advocacy, framework-development, research, publication, collaboration, and status semantics.
Contact route
Public email route, accepted inquiry categories, unsupported routes, security declaration, and relationship boundary.
FRAMEWORK
Framework publication map
Current RRF v1.0 resources are separated into the normative Core/RRP layer and a supporting technical layer. The supporting layer does not create an Association-operated certification, accreditation, approval or endorsement scheme.
RRF v1.0 package record
Ordered membership record for the six RRF v1.0 source-of-record documents, including SHA-256 digests.
RRF v1.0 package JSON
Machine-readable package membership, document roles, canonical URIs and integrity metadata.
Framework landing resource
Supporting technical index
RRP Interpretive Guidance
RRP Implementation Standard
RRP Implementation Standard — Operational Annex
RRP Conformity Statement Template
Human-facing framework guide
PUBLICATIONS
Dated Association statements
Statements are Association publications with their own status and dates. They are separate from the Robot Rights Protocol and do not amend the current RRP unless a future protocol publication explicitly says so.
Statement index
Index of dated Association statements with status, languages, RRP relationships, and resource locations.
Statement 002 — RRF/RRP v1.0 and the Association’s Advocacy Position
Structured metadata and full English content for the Association’s advocacy position and the role of RRF/RRP v1.0.
Statement 001 — Current Scope of Robot Rights Inquiry
Structured metadata and full English content for Statement 001, including its original relationship to RRP v0.1 at the time of publication.
PROTOCOL
Robot Rights Protocol versioned resources
/rrp is the current alias. RRP v1.0 has a stable source-of-record URL at /rrp/1.0; RRP v0.1 is retained under /rrp/0.1 with its original byte-for-byte snapshot separately preserved.
RRP v1.0 source of record
Current structured RRP
Archived RRP v0.1
RRF Core Principles v1.0
Version index
Japanese translation status
A full Japanese reference translation of RRP v1.0 is published. The English v1.0 publication remains the source of record; archived v0.1 remains available.
Privacy policy metadata
Structured privacy-policy metadata with links to the full English and Japanese human-facing policies.
REGISTRY
Domain, publisher, and interface provenance
The registry describes two official interfaces of one Association. The domains are not mirrors, and each interface keeps its own canonical URLs.
Interface registry
Machine-readable domain roles, canonical policy, shared publisher identity, and the relationship between robot-rights.jp and robotrights.jp.
Human interface
Official human-facing website of the same Robot Rights Association. It is not a mirror of the machine interface.
TRANSPORT
HTTP delivery contract
Public machine resources are served over HTTPS with explicit media types. Structured and discovery resources permit cross-origin public reads; no write API is exposed.
| Resource class | Content type | Cache behaviour |
|---|---|---|
| JSON APIs and well-known JSON | application/json; charset=UTF-8 | 5 minutes, then revalidate |
| General HTML representations | text/html; charset=UTF-8 | Revalidate on use |
| Versioned source-of-record framework publications | text/html; charset=UTF-8 | 1 hour, then revalidate |
| robots / llms / humans / security / sitemap | Explicit plain-text or XML type | 1 hour, then revalidate |
| Web manifest | application/manifest+json; charset=UTF-8 | 1 day, then revalidate |
Application write methods are rejected by the publication layer. Host-level diagnostic methods such as TRACE are outside this static interface contract and should be controlled by the hosting server.
Schema 1.5 retains the semantic cleanup introduced in 1.4. The ambiguous
binding field has been removed. Use legal_force for legal enforceability and normative_effect for framework-internal normative role. For RRP/RRP-IS, a voluntary conformity claim can still make applicable shall requirements mandatory for the accuracy of that claim.AGENT DISCOVERY
Automated-reader and operational resources
Plain-text, XML, well-known, and browser resources used by LLM readers, crawlers, security reporters, and user agents.
| Resource | Format | Purpose |
|---|---|---|
/llms.txt | text/plain | Priority-ordered machine-interface guide for LLM and automated readers, including source-precedence and document-boundary rules. |
/robots.txt | text/plain | Crawler access policy and sitemap location. |
/sitemap.xml | application/xml | Canonical public HTML URL inventory for crawlers and indexing systems. |
Current aliases | HTML routes | Stable current-version entry points such as /rrp remain public and discoverable through the manifest and framework metadata, but are omitted from the sitemap when their HTML canonical points to a versioned source. |
/humans.txt | text/plain | Publisher, contact, protocol paths, and human-site identity. |
/.well-known/security.txt | text/plain | Security and correction contact declaration. |
/site.webmanifest | application/manifest+json | Browser application identity and icon paths for the machine interface. |