> For the complete documentation index, see [llms.txt](https://docs.tracr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tracr.com/release-notes/tracr-1.30.0.md).

# tracr 1.30.0

##

### Tracr API

* Implemented restrictions on diamonds registered by Sarine
  * The following attributes cannot be modified:
    * Rough carat weight
    * Rough scan
* Implemented restrictions on diamonds polished by Sarine
  * The following attributes cannot be modified:
    * Polished carat weight
    * Polished shape
    * Polished scan
    * Polished scan report
    * Grading certificates can only be uploaded through GIS

### Portal

* Implemented new archive flow
* Implemented new unarchive flow
* Added support for Polished Check

### Diamond Experience

* Added support for Polished Check

### Grading Integration Service

* Fixed and issue preventing GIS from working for diamonds that only have a carat weight and shape

### Integrations

* Support split rough diamonds being registered by Sarine
* Support polished diamonds being registered by Sarine


---

# 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.tracr.com/release-notes/tracr-1.30.0.md?ask=<question>&goal=<endgoal>
```

`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.