Advanced deployment changes

Advanced changes are handled through the facility change-control process and the version-specific deployment runbook. Public documentation does not expose internal service topology or source-level configuration.

Before changing an instrument, detector, identity provider, storage target, compute pool, workflow engine, or external integration:

1. Record the intended outcome, affected boundary, owner, and rollback condition.
2. Test the change with representative non-production data and denied-access cases.
3. Validate backup, recovery, monitoring, audit coverage, and capacity.
4. For instrument-facing changes, repeat simulation and bounded supervised operation.
5. Approve and record the resulting configuration revision.

Contact the deployment owner when a required change is not covered by the controlled runbook.