Provider-Neutral DevOps Operations

Priority: P1 (HIGH)

Single operations entrypoint for cloud infrastructure and services. MCP tools and discovered capabilities govern execution; organizational policy and host controls govern authorization.

Operational Lifecycle

Every operation follows seven mandatory stages:

1. Discover MCP: Verify required provider MCP is installed, connected, and advertising necessary tools. No silent CLI fallback.
2. Verify Identity & Scope: Confirm authenticated principal, organization/account, project/resource, region, and environment.
3. Identify Policy & Capabilities: Match discovered tool capabilities against target organizational security policy.
4. Propose & Authorize: Present concrete action set, target, artifact identity, risk, and expiry to authorized human.
5. Execute Bounded Operation: Perform authorized mutations with bounded deadlines and idempotency tokens.
6. Independently Verify: Inspect outward system behavior from target origin, separate from mutation operator.
7. Reconcile & Report: Emit standardized operations report; reconcile actual state; preserve feature lifecycle.

Core Operations

Default operation=deploy when omitted. Reject unknown, typo, or conflicting modes.

Effect-Based Eligibility

Classify operations by real-world effect, never by mode label alone:

• Deploy-Bearing Actions: Any traffic switch or configuration introducing a new release enters full deploy readiness gates, even under setup or recover.
• Read-Only Mode Lock: verify, monitor, and diagnose cannot execute writes. Mutation requests block and require renewed authorization.
• Recovery Boundary: recover applies fixed runbook mitigations against an identified prior artifact or state. Fresh builds require release workflows. Active harm retains incident-hotfix policy; containment retains cyber-triage.

Positive & Negative Invariants

• Positive Invariants:
  • Authorized, scoped operations proceed with least-privilege discovered tools.
  • Irrelevant or unconfigured providers do not block independent analysis of configured targets.
  • Offline review proceeds with explicit evidence limit when MCP is absent.
• Negative Invariants:
  • No implicit credentials, ambient CLI fallbacks, or automatic tool installations.
  • No agent self-approval, role expansion, or making resources public to bypass errors.
  • No secret values, credentials, or tokens in reports, receipts, or logs.
  • No timeout-as-failure retry; reconcile actual resource state before re-attempting.

Detailed References

• Authorization & Host Enforcement — Scope binding, approval invalidation, enforcement evidence checklist.
• MCP Preflight & Capabilities — Connection schema, tool discovery, structured missing-MCP outcomes.
• Operations & Effect Classification — Six operations, diagnostic side effects, uncertain-write reconciliation.
• Orchestration & Verification — Single context, specialist briefs, caller-return semantics, monitoring contract.
• Evidence & Reporting Matrix — Operations report shape, lifecycle preservation, consumer gap handling.
• Provider References — Read the matching file before any provider operation: AWS, GCP, Cloudflare, Vercel.
• Provider Extension Contract — Read before onboarding a new provider: Extension Contract.