CAST AI Offline-First Development Loop

Overview

Make configuration feedback fast without treating a live cluster as a test fixture. Render, validate, diff, and policy-check locally; use a sandbox only for the behavior that cannot be proven offline.

Prerequisites

• Repository-owned Terraform, Helm values, policy, or workload manifests
• Pinned tool and provider versions
• Sanitized fixtures for cluster identity, policies, and API failures
• Optional sandbox with a distinct kube context and budget owner

Instructions

Step 1: Map inputs and ownership

Use Read and Grep to locate provider constraints, chart versions, values, annotations, policy definitions, generated files, and secret references. Identify which files are authoritative and which are derived.