> For the complete documentation index, see [llms.txt](https://nytshift.gitbook.io/nytshift-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nytshift.gitbook.io/nytshift-docs/policy-control-and-incident-response/rehearsal-record-template.md).

# Recovery rehearsal record template

Copy this template into the controlled operational evidence system. Do not commit completed production records containing personal contacts, provider endpoints or sensitive infrastructure detail.

## Record identity

* Rehearsal ID:
* Scenario: provider drift / signer compromise / credential rotation / unknown outcome / reconciliation outage / alert outage / backup-restore / exact release rollback
* UTC start and finish:
* Environment: isolated / testnet / production-safe read-only
* Exact release commit and artifact digest:
* Incident Commander:
* Risk Owner:
* Security Owner:
* Execution Owner:
* Release Owner:

## Preconditions and authority

* Capital-moving actions authorized: **none** unless a separate signed authorization is attached
* Venue and network:
* Entry kill-switch evidence:
* Mainnet flags disabled evidence:
* Backup/artifact verification digest:

## Timeline and observations

Record only UTC time, role, fixed reason code, command category, bounded outcome and evidence digest. Do not include secrets, wallets, account/order IDs, URLs, raw bodies or provider text.

## Acceptance

* Exact containment gate passed:
* Store schema/integrity/WAL passed:
* Alert delivery/deduplication passed:
* Unknown-outcome non-retry rule demonstrated:
* Reconciliation/finality boundary demonstrated:
* Exact rollback or restore passed:
* Browser/health gates passed:
* Open exceptions and expiry:

## Sign-off

* Incident Commander / UTC:
* Risk Owner / UTC:
* Security Owner / UTC:
* Execution Owner / UTC:
* Release Owner / UTC:

An unsigned or partially signed record is evidence-incomplete and cannot restore mainnet authority.


---

# 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://nytshift.gitbook.io/nytshift-docs/policy-control-and-incident-response/rehearsal-record-template.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.