> For the complete documentation index, see [llms.txt](https://library.xrguild.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.xrguild.org/xr-guild-library-2.0/criteria-for-submissions.md).

# Criteria For Submissions

We are currently refining the submission process. Please look forward to an update in 2026!

### Summary

The Library makes no guarantee that content submitted will be accepted for display. This is not intended to call into question either submitter or content; rather, items must meet a few basic guidelines. Even otherwise excellent items may be rejected if they do not meet the criteria outlined below. The Library will make a reasonable effort to preserve all submissions but only accepted submissions will be displayed to the public.

### Criteria

1. Content must be primarily relevant to XR (VR, AR, Metaverse, etc.)
   1. Example: A single passing mention of “augmented reality” in an article focusing on the health and safety of teens online is not relevant enough to qualify for the XR Guild’s Library
2. Content's focus must be at least partially ethical in nature
   1. Many excellent technical XR-related articles exist, but the XR Guild is established primarily for ethical considerations as technology progresses rather than purely favoring technological progress
3. Content must be publicly available
   1. Very limited exceptions to this rule have been made for early Library submissions, but in general the Library wishes to avoid linking to content which is hidden, behind a paywall, private, etc. to respect the wishes of authors and/or institutions
4. Content must reasonably fall into one or more of the established Library Categories
   1. The Library is open to suggestions for new Categories, but submission of an Item requiring a new Category without prior discussion is likely to result in rejection rather than in creation of a new Category


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://library.xrguild.org/xr-guild-library-2.0/criteria-for-submissions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
