# TESS-MIG-001 — Cutover Procedure

This procedure is evidence-bound. It does not authorize a production cutover until the M5 qualification gate records the required validation.

1. Confirm the gateway has the explicitly registered `runtime.hermes` adapter (`apps/gateway/src/agent/agent.module.ts`) and provider reachability evidence (`apps/gateway/src/agent/hermes-runtime-reachability.e2e.test.ts`).
2. Query the normalized runtime capability surface, not a Hermes API directly. Confirm the session capabilities required for the operation are advertised.
3. Query the transitional matrix through `RuntimeProviderService.transitionalCapabilityMatrix` (`apps/gateway/src/agent/runtime-provider-registry.service.ts`). Kanban, skills, memory, tools, and cron must remain `unsupported`; stop rather than route those operations through Hermes.
4. Route new memory activity through the Mosaic operator-memory plugin path; there is no landed Hermes memory import.
5. Use `MosCoordinationService` for orchestration handoff. Tess does not take Mos authority.
6. Record the qualification evidence and only then update an external deployment/channel binding through its separately authorized operational process.

No claim here authorizes bulk transcript copying, data-schema migration, or enabling an unsupported transitional capability.