> For the complete documentation index, see [llms.txt](https://docs.geoprismregistry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geoprismregistry.com/readme/current-1/geoprism-registry-key-components/5.2-content-related-capacities-of-geoprism-registry/5.2-content-related-capacities-of-geoprism-registry-2.md). # 5.2.3. Master vs. non-master The primary objective of a common geo-registry is to share the authoritative data coming from the governmental entity having the official curation mandate over it. This is what is being referred to as the master data and information. While this is the type of data and information that should be hosted as a priority GeoPrism Registry to serve as the source of truth, it is possible that either the master data/information is not available, not of quality (incomplete, out of date…), and/or not accessible. In these cases, and to ensure the continuity of operations, GeoPrism Registry can host, manage, and share 'non-master' data/information in parallel or complementary to the master data/information (note that both types should be clearly differentiated), as well as facilitate the convergence of the two lists once the master version is available, of quality, and/or accessible. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.geoprismregistry.com/readme/current-1/geoprism-registry-key-components/5.2-content-related-capacities-of-geoprism-registry/5.2-content-related-capacities-of-geoprism-registry-2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.