Customer-facing operating guide
Migration, engineered for clarity.
A single wiki for planning, testing, executing, and accepting a Realtime Register Gateway migration—paired with production-oriented answers for the questions that surface along the way.
FRAMEWORK / 01Current
One controlled handover
Scope → decide → connect → prepare → test → authorize → execute → stabilize
- Operating model
- Parallel preparation, controlled cutover
- Hard gate
- Verified access, data, owners, and timestamps
The operating spine
Eight phases. One evidence trail.
Preparation can move in parallel across registries. Every backend still passes through the same gates before its coordinated polling cutover.
Recommended path
Use the playbook for sequence. Use the FAQ for judgment.
The playbook is the shared source of truth for owners, dates, evidence, and acceptance. The FAQ explains behavior that cannot safely be reduced to a checkbox.
- 01Confirm inputs
Inventory scope, owners, access, constraints, and source controls.
- 02Make decisions explicit
Record policy ownership before configuration and testing.
- 03Use the FAQ at exceptions
Check classifications before turning test observations into production rules.
- 04Close on evidence
Reconcile, accept, and retire legacy access only when the gates pass.
Security rule
Never place credentials or secrets in the playbook.
Registry requirements and migration scope vary. Final responsibilities, timing and recovery options are agreed during discovery. Credentials and secrets must never be entered in this workbook; use the approved secure transfer channel.