Registry stack documentation: machine-readable Markdown.
Index of all pages: https://docs.registrystack.org/preview/llms.txt
Full corpus: https://docs.registrystack.org/preview/llms-full.txt

# Prepare the operator handoff

> Move a validated Registry Stack project from local evaluation to an operator-owned deployment.

The beginner tutorials stop at a loopback-only local runtime. Use this
checklist to decide whether an operator can take ownership. Registry Stack
provides bounded runbooks for product operations, but it does not provide a
verified production deployment for your institution.

## Handoff checklist

Before activation, the implementer and operator must record:

- The reviewed authored project, intended environment, generated artifact
  manifest, and validation results
- Named owners for source data, configuration, secret distribution, signing
  keys, runtime state, audit output, and monitoring
- The exact fields, filters, purposes, scopes, and callers exposed by each
  service
- Production identity, Transport Layer Security (TLS), network, and outbound
  connection boundaries
- Institution-owned procedures for backup, retention, recovery, credential
  rotation, upgrades, rollback, and incident response
- The approval evidence and named authority required before activation

Files under `.registry-stack/runtime/local/` contain local
credentials, Compose input, and runtime results. Keep them private and do not
treat them as a production deployment package.

## Use the operations guidance

The available guidance defines product procedures and the evidence to retain.
You still need to adapt, review, and exercise each procedure in the target
environment:

- [Compare, rotate, recover, and diagnose generated product inputs](advanced/)
- [Registry Notary deployment hardening](../products/registry-notary/deployment-hardening-runbook/)
- [Registry Notary PostgreSQL operations](../products/registry-notary/postgresql-state-operations/)

Draft procedures for reverse proxies, backup and restore, retention, upgrades,
and rollback are not released as supported runbooks yet. Institution-owned
procedures remain required before production exposure.

This checklist and the linked runbooks do not establish production readiness,
legal approval, data fitness, or country acceptance.

## Next

- [Validate the project](../verify/)
- [Understand generated files](../generated-artifacts/)
- [Review the security guidance](../security/)
- [Review the security support window](../security/support-window/)
- [Report a vulnerability](../security/report-a-vulnerability/)