> For the complete documentation index, see [llms.txt](https://rawctx.gitbook.io/rawctx-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rawctx.gitbook.io/rawctx-docs/documentation/reference/production-readiness-checklist.md).

# Production readiness checklist

Use this checklist before an application writes answer evidence in production.

## Identity and endpoint

* Set a reviewed workspace API host in `RAWCTX_REGISTRY`; never configure the Hub browser BFF as an SDK registry.
* Create one dedicated runtime token per deployment from **Settings > Access & team > API tokens** in the workspace Hub.
* Do not run `rawctx login` in a production server or container, and do not reuse an administrator's interactive CLI token.
* Store `RAWCTX_TOKEN` in a secret manager, never in source, images, or logs.
* Set the shortest practical expiration and rehearse UI-based rotation and revocation. Current UI-issued tokens are workspace/user scoped rather than bound to one `application_key`.

## Answer evidence policy

* Confirm whether the workspace requires platform-managed keyed hashing.
* Review question-text storage, answer-text storage, and default retention separately; submission does not imply persistence.
* Define stable idempotency, external trace, conversation, and message keys.
* Define which source references and commitments the application must record.
* Decide who can append corrections, voids, redactions, and retention events.

## Evidence and privacy

* Keep original files in controlled evidence assets, not answer metadata.
* Require a purpose for retrieval and bind the returned access event when the asset informed an answer.
* Do not put raw prompts, answers, private URLs, storage keys, customer data, or access tokens in public proof material or OTel attributes.
* Test redaction and HTTP 410 behavior before relying on the deletion workflow.
* Apply a retention and encryption policy to exported JSONL or CSV files.

## Completeness and trust

* Reconcile against a genuinely separate system of record on a bounded period.
* Alert on missing, duplicate, late, unexpected, and unanchored findings.
* Verify proof bundles offline first, then use online verification when the anchor or witness policy requires it.
* Distinguish `PENDING`, local-only, and unverified-signature states from anchored verification.
* Record factual accuracy, delivery, and actual source use as separate review conclusions; rawctx proof material does not establish them.

## Failure rehearsal

* Expire or revoke a token and confirm the application fails closed.
* Reuse an idempotency key with a different payload and confirm the 409 path.
* Simulate registry timeout and verify bounded retries do not create duplicates.
* Verify an intentionally damaged proof and confirm it cannot be promoted.
* Run a reconciliation fixture with a known missing record.
* Confirm a newly created answer remains reviewable while its proof is pending checkpoint publication.


---

# 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://rawctx.gitbook.io/rawctx-docs/documentation/reference/production-readiness-checklist.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.