> For the complete documentation index, see [llms.txt](https://vci-gci-docs.clinicalgenome.org/vci-gci-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vci-gci-docs.clinicalgenome.org/vci-gci-docs/getting-started-in-the-vci-and-gci/about-the-curation-interfaces.md).
# About the Curation Interfaces
**ClinGen** has two distinct curation interfaces, the **Test Site** and the **Production Site**.
The two sites have the same functionality, but there are important differences.
Test
Production
Training and practice curation
Real curation
Data erased annually
Data saved permanently
Data is not publishable
Approved curations can be published
{% hint style="info" %}
Please note that registration for the two sites is separate, so users wishing to use both sites must register for both sites.
{% endhint %}
### The Test Interface
####
The test site (also called the demo site) is intended as a resource for new curators and others wishing to familiarize themselves with the interfaces. All data is periodically deleted, and as such, this site should NOT be used for "real" curation.
{% hint style="info" %}
A pink banner with next deletion date is always displayed at the top of the test interface.
{% endhint %}
### The Production Interface
####
Data entered into the production interface is permanently saved, so this interface should only be used for “real” curation.
We recommend curators become familiar with the curation interfaces by exploring the test versions before curating “real” evidence in the production interfaces. Data entered into the test interfaces is erased annually, so do NOT enter any data you wish to be permanently saved.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://vci-gci-docs.clinicalgenome.org/vci-gci-docs/getting-started-in-the-vci-and-gci/about-the-curation-interfaces.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 `build a script that syncs our docs to a CMS` 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.