GCP Costs and Risk Controls¶

Executive Summary¶

This document defines the financial, operational, and governance controls managing WorkWingman’s Google Cloud Platform (GCP) footprint.

Cloud Run Cost Structure: Serverless architecture scales compute according to inbound request volume, preventing idle capacity costs. Traffic-split capabilities isolate test revisions from production billable traffic.
Artifact & Content Storage: Storage utilization in Artifact Registry and GCS is governed by lifecycle policies.
Budgeting & Limits: TODO(verify) exact monthly budget caps, alerting thresholds, GCP project IDs, and region specifications.

Immutable Deployment Safeguard: Mandating immutable sha-<commit> tags and digest deployment prevents stale-byte code execution and costly deployment rollback incidents.
Secret Version Continuity: Enforcing the requirement to publish replacement secrets prior to disabling older versions prevents self-induced application downtime.
Configuration Drift Governance: Mandatory tracking of service variables in env-ladder mitigates the risk of stripping active production settings during routine releases.

CMS Integrity Verification: SHA-256 ETag guards on the GCS content bucket protect against silent data corruption and invalid state writes.
Identity & Access Management: TODO(verify) exact service account roles, billing administrative access, and principle-of-least-privilege boundaries.

Attribution: Comprehensive tracking via GCP Cloud Logging ensures full visibility into principal actions and deployed revisions for post-incident audits and financial governance.