Product tour deck — Azure AKS and GCP GKE
Open the product tour deck (←/→ or on-screen buttons).
Narrative: Entra or Identity Platform → Ricardian contract → the TSP’s existing AKS or GKE cluster → provenance → deploy/predict under Open-GMASE, with CompliancePulse on the decision path. Azure still carries the Key Vault and confidential-compute target. GCP names the existing GKE cluster the same way Azure names AKS: project, location, cluster, namespace, and GCS bucket on the contract; kubeconfig path on the TSP dashboard. A missing path fails the job. Design/pilot slides are labeled as such in the deck.
| Resource | Link |
|---|---|
| Interactive deck | azure-e2e-product-tour.html |
| Speaker notes | AZURE_E2E_PRODUCT_TOUR_DECK.md |
| UI tour | Product tour (Local, Azure AKS, and GCP GKE captures) |
| Entra architecture | Azure security architecture |
| Confidential computing | Threat model · Key Vault · SKR · e2e |
| SPIFFE / WI | SPIFFE/SPIRE on Azure |
| Terraform (pilot) | deployment/azure/terraform |
| KMS / TEE | DEK·MEK · TEE attest → decrypt |
DEPA context: depa.world.