> For the complete documentation index, see [llms.txt](https://plimsoll-protocol.gitbook.io/plimsoll-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://plimsoll-protocol.gitbook.io/plimsoll-protocol-docs/guides/auditors-and-transcribers.md).

# For auditors and transcribers

## Getting registered

Both roles are granted by the registry admin. Open an issue in [plimsoll-contracts](https://github.com/plimsoll-protocol/plimsoll-contracts/issues) with:

* the Stellar account you will sign with,
* the display name to show (max 64 characters),
* for auditors: your firm and a public page that confirms the engagement.

The admin calls `set_reporter`. You can confirm with:

```bash
stellar contract invoke --network testnet --send=no \
  --id CCZCBR7MGSW5LGIEUQR5TU5Z7JQWBDEESB3RGPTRPMCBUMOISRPY7GOB -- \
  get_reporter --reporter <YOUR_G_ADDRESS>
```

## Auditors

Your reports carry the strongest tier. Integrators that require `min_tier = AuditorSigned` see only your figures.

Post the figure from your attestation, with **As of** set to the attestation date, and the URL and hash of the signed document. Use the app's [Post a report](https://plimsoll-app-gths-amber.vercel.app/report/) page; it shows **Will post as Auditor-signed** once you connect.

## Transcribers

You copy figures from reports that issuers or auditors have already published, for assets whose issuers are not posting themselves. Your reports are the lowest tier and are labelled *Transcribed* everywhere.

Rules:

1. Copy the figure exactly as published. Do not adjust or convert it.
2. **As of** is the date in the document, not today.
3. Link the issuer's own URL for the document, and hash the exact file.
4. One report per published document. The contract rejects a report that is not newer than your last one for the same asset.

## Mistakes

A report cannot be edited or deleted. If you post a wrong figure, post a corrected one with a later `as_of` and explain it in an issue. If you think another reporter's figure is wrong, open an issue with the evidence.


---

# 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://plimsoll-protocol.gitbook.io/plimsoll-protocol-docs/guides/auditors-and-transcribers.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.