Cloud Computing Platform Maps

These cloud computing platform maps were presented at Commit Your Code 2026, exploring devOps and SRE sociotechnical practices across cloud platform value streams.

Social practice sources: minimumcd.org, dora.dev, sre.google/books.

Cloud Platform Value Stream Map

The cloud delivery value stream: code moves from DEV to UAT to PROD. SLIs can be identified as "what to measure" in dev. SLOs are ranges for SLI metrics aligned with SLAs and error budgets to ensure production stability.

Cloud Platform: DevOps Practices

DevOps practices across the cloud platform value stream: from pull request through continuous integration, continuous delivery, and deployment. Teams should initially establish devOps practices illustrated with the blue anchors before pursuing the purple anchors, which are shared practices between devOps and SRE.

Cloud Platform: Reliability Practices

Site reliability practices: observability, error budgets, incident management, and toil reduction. Maps the practices that support service reliability from the SRE / on-call perspective, showing dependencies between observability backends, telemetry collection, and incident tooling. Here teams should be trying to move from the shared purple practices to the SRE practices illustrated by the red anchors.

GreenTest - Bootstrapping & Verifying a Linux Environment

A dependency map for a local DEV stage of the value stream above: what it takes to get a verified local dev environment. bash and linux sit as commodity, not worth building, just depended on. The interesting work is the custom-built-to-product band above them: greenTest's bootstrap scripts and notebook, verified against vanilla compost or whichever repo you're working on. The greenTest notebooks are used to smokeTest repositories locally before customizing them for any specific use.

Vanilla Compost - Base Wardley Map

A minimal blog platform dependency map: what it takes to build and deploy a static site. Shows the relationship between content creation, site generation, hosting platforms, and the underlying infrastructure components across their evolutionary stages. The content creation is embedded in the markdown file, which is effectively the only artifact that needs to be shipped to publish a post.