The Idea
Writing code is only the first step of software delivery. Before a feature ever reaches a user, it must pass through a multi-stage pipeline: Code, Build, Test, Review, Deploy.
When you trigger Push Code, the automated sequence begins. In an ideal environment, every stage transitions smoothly from running to completed. However, real-world delivery pipelines are rarely deterministic. Enabling Chaos Mode introduces real-world engineering failures, causing builds to break, tests to flake, or approvals to stall.
If any single link in the chain fails, delivery stops immediately. You must resolve the failure and re-trigger the pipeline to successfully release software to the App Store.
Brilliant code creates zero value if it cannot survive the deployment system.
Behind the Experience
Developers often measure progress by completed commits, but user value only exists once code successfully reaches production. We built this experiment to make the mechanics of software delivery visible and tangible. By pairing a real-time CI/CD workflow with an unpredictable Chaos Mode, the lab demonstrates how build failures, flaky tests, and operational bottlenecks directly dictate whether code survives to production.
Keep Exploring
More experiments from the Lab
Dragging frame rates down to feel the difference between 10fps and 60fps.
play →Comparing native physics and unoptimized scrolling side by side.
play →Dragging the fidelity slider to watch small implementation errors compound.
play →