> For the complete documentation index, see [llms.txt](https://devs.truebit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devs.truebit.io/overview/what-is-a-transcript.md).

# What Is a Transcript?

**Transcripts are certificates of compute**. Each transcript serves as an unchanging record of every step taken, attesting details of every task execution​.

It acts as the ultimate **source of truth**, ensuring that anyone who reviews it can accurately determine the status of a task and verify the correctness of its output. This means **you can rely on the transcript** to provide an accurate account of what happened during such execution.

## Transcript Pillars

<div data-with-frame="true"><figure><img src="https://1506829519-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAfNTfJ48HTdTVB8EdvCs%2Fuploads%2F7I4aNSub4k8PGZROveQj%2Fimage.png?alt=media&amp;token=f677abc7-7540-42e2-888a-13d638ce2fe4" alt=""><figcaption></figcaption></figure></div>

Transcripts ensure full transparency, driven by the following key pillars:

* **Immutability**: The transcript provides an **unchangeable record** of everything that occurred during task execution. It's a reliable source of truth for the entire process.
* **Protocol**: *Clear Roles & Responsibilities -* The transcript clearly outlines **who is responsible for what and when.** This means anyone reviewing the transcript can easily determine the progress of the task and verify the accuracy of the results.
* **Incentives & Slashes**: *Rewarding Good Behavior, Correcting Mistakes -* The transcript includes **information about rewards and penalties** for following or deviating from the protocol. This ensures that everyone involved has extra motivation to act in accordance with the established guidelines.

{% hint style="info" %}
Click [here](/architecture/execution-transcripts.md) to view an example transcript.
{% endhint %}