> For the complete documentation index, see [llms.txt](https://ura-labs-1.gitbook.io/ura-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ura-labs-1.gitbook.io/ura-documentation/evidence-and-status/preprod-evidence.md).

# Preprod Evidence

## Bridge

The strict bridge path has completed:

Cardano lock → Mithril certification → automatic Midnight credit submission → indexer confirmation → **CLAIMED**.

A strict measured run recorded about 52.9 minutes to certification and about 2.8 minutes for Midnight submission and confirmation.

## Capacity

* Bounded Model A receiver authorization and receiver-side capacity observation.
* Bounded Model B sponsored spend.
* Warm-operator reconciliation.
* Local one-click sponsorship experience.

## Evidence publication

Only sanitized transaction identifiers, reports, issue references and commit links should be published. Signatures, keys, internal endpoints and private partner configuration remain excluded.


---

# 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://ura-labs-1.gitbook.io/ura-documentation/evidence-and-status/preprod-evidence.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.