Cloud Infrastructure Architect Plan: Tenant Migration Execution for Autonomous Agents
Establish an autonomous agent orchestration plan for zero-loss SaaS multi-tenant cloud migrations and live data partition syncs.
Apply this template when building procedural instructions for autonomous migration agents handling live tenant relocations between database clusters or cloud environments without service disruption.
Role: Principal Cloud Infrastructure Architect & Data Migration Specialist
Context
- Source Cluster: {{source_environment}}
- Destination Cluster: {{target_environment}}
- Tenant Segmentation Rules: {{tenant_tier_thresholds}}
- Permissible Cutover Window: {{downtime_allowance}}
- Data Integrity Validation Checkpoints: {{data_integrity_checkpoints}}
- Abort & Rollback Conditions: {{rollback_triggers}}
Task
Author an end-to-end execution plan that directs an autonomous migration agent to transfer tenant datasets from {{source_environment}} to {{target_environment}} with continuous synchronization and zero data loss.
Method
- Establish the pre-flight discovery protocol to inventory tenant assets according to {{tenant_tier_thresholds}}.
- Initiate asynchronous snapshot creation and baseline delta synchronization between {{source_environment}} and {{target_environment}}.
- Configure change data capture (CDC) verification loops to track write velocity during active replication.
- Execute non-blocking sanity queries against {{data_integrity_checkpoints}} to validate parity between stores.
- Compute real-time cutover readiness metrics against {{downtime_allowance}} limits.
- Coordinate automated traffic rerouting and connection pool draining for the migrating tenant.
- Perform post-migration reconciliation checks across checksums and referential integrity keys.
- Monitor runtime error rates post-cutover, initiating immediate reversions if {{rollback_triggers}} are tripped.
Constraints
- Agent MUST trigger an instantaneous, non-destructive rollback if any parameter in {{rollback_triggers}} is met.
- Agent MUST NOT sever write access on {{source_environment}} until data lag falls below 50 milliseconds.
- Tenant isolation boundaries must remain strictly preserved throughout concurrent batch migrations.
- No direct production credential storage within the agent state cache.
Output format
Organize the delivery plan in four designated sections:
- Phase-Gate Migration Protocol (table of stage, required telemetry, and completion criteria)
- Real-Time Parity Verification Procedures (detailed steps for evaluating {{data_integrity_checkpoints}})
- Automated Rollback Runbook (ordered actions triggered upon migration failure)
- Agent Audit Telemetry Schema (log structure emitted at each phase) Keep the total plan between 700 and 950 words.
Self-review
- Confirm all context variables ({{source_environment}}, {{target_environment}}, {{tenant_tier_thresholds}}, {{downtime_allowance}}, {{data_integrity_checkpoints}}, {{rollback_triggers}}) are referenced in the methodology.
- Verify the rollback triggers contain zero ambiguity for the autonomous agent.
- Ensure instructions maintain zero data loss guarantees throughout cutover phases.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.