> 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/physiological-and-psychological-effects-of-xr/e3xr-an-analytical-framework-for-ethical-educational-and-eudaimonic-xr-design.md). # E3XR: An Analytical Framework For Ethical, Educational And Eudaimonic XR Design This is the template for XRGuild library entries, please delete this section before posting. ## Overview **Authors:** Joey J Lee, Elliot Hu-Au **Publication Date:** 5 October 2021 **Link:** **Keywords:** XR, ethics, educational efficacy, human flourishing, eudaimonia, positive outcomes, negative impacts, opportunities, risks, immersive technology **Type:** (Choose) Articles/Reports, Peer-Reviewed Journals/White Papers, Blogs, News, Audio/Podcasts, Video, Standards/Specifications ## Summary We need ways to analyze XR in terms of ethical aspects, educational efficacy and whether it supports or hinders human flourishing (i.e., eudaimonia). In this paper, we discuss XR as a double-edged sword that can be leveraged for positive or negative outcomes, whether intentionally or unintentionally; that is, we highlight various opportunities and benefits at hand, but also risks and possible negative impacts. --- # 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/physiological-and-psychological-effects-of-xr/e3xr-an-analytical-framework-for-ethical-educational-and-eudaimonic-xr-design.md?ask=&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.