Cloud Operations

Operate supported cloud providers through one safety contract and a provider-specific translation.

Process

1. Identify provider, account or project, principal, region/zone, environment, resource, and requested outcome.
2. Inspect active configuration without assuming defaults are correct.
3. Start with read-only identity and resource discovery.
4. State the exact command or API operation, consequences, permission needs, billing impact, rollback, and verification.
5. Execute local, disposable, or explicitly authorized remote mutations only within the confirmed target. Treat ambiguity as protected.
6. Keep credentials, tokens, profiles, key files, and kubeconfigs out of source, logs, and generated artifacts.
7. Verify the observed resource state and report withheld production actions.