Operations and Change Management

Software that works on your laptop isn’t finished. It’s not even close. Software becomes real when it runs in a place where other people depend on it, and stays real only as long as you can change it without breaking that trust. This section is about the operational patterns that govern how software moves from development into the world, and how it evolves once it gets there.

These patterns form a progression. An Environment is the context where software runs. Configuration lets the same code behave differently across environments. Version Control is the system of record for every change. A Git Checkpoint is a deliberate boundary that makes risky work reversible. Migration handles the delicate business of changing data and schemas without losing what came before. Ship is the root verb: putting a real, working outcome into users’ hands and giving up the ability to silently change what they see. Deployment is the mechanical act of making a new version available. Continuous Integration, Continuous Delivery, and Continuous Deployment progressively automate the path from commit to production. When things go wrong, Rollback gets you back to safety. Feature Flags decouple what you deploy from what users see. And Runbooks capture hard-won operational knowledge so it doesn’t live only in someone’s head.

In agentic coding, these patterns aren’t optional luxuries. An AI agent can generate code fast, which means it can also introduce change fast. Without version control, checkpoints, and the ability to roll back, that speed becomes a liability. The operational patterns in this section are the guardrails that make agentic velocity safe.

This section contains the following patterns:

• Environment — A particular runtime context (dev, test, staging, production).
• Configuration — Data that changes system behavior without changing source code.
• Version Control — The system of record for changes to source.
• Git Checkpoint — A deliberate commit or reversible boundary before/after risky work.
• Migration — A controlled change from one version of data/schema/behavior to another.
• Ship — Putting a real, working outcome into users’ hands, in a version you can no longer silently change.
• Deployment — Making a new version available in an environment.
• Continuous Integration — Merging changes frequently and validating automatically.
• Merge Queue — Serializing approved changes through an ordered queue that tests each one against the changes ahead of it, so concurrent merges that pass alone but break together never reach the mainline.
• Continuous Delivery — Keeping software releasable on demand.
• Continuous Deployment — Automatically releasing validated changes to production.
• Progressive Delivery — Releasing a change to users incrementally, reversibly, and on evidence rather than all at once.
• Pipeline as Code — Defining the delivery pipeline in version-controlled files rather than clicking it together in a UI.
• Pipeline Synthesis — Having an agent generate and maintain the delivery pipeline from the repository it already understands.
• Build Provenance — A verifiable record of how an artifact was built, from which source, by which process.
• Autonomous Remediation — A detect-fix-verify loop that lets an agent repair bounded failures under retry limits, review gates, and governance.
• Retry Budget — A bound on how many times a failed operation may be retried, under what backoff, for which failures, and what happens when the attempts run out.
• GitOps — Driving the state of running systems from a Git repository that is the single source of truth.
• Rollback — Returning to a previous known-good state.
• Feature Flag — A switch that decouples deployment from exposure.
• Runbook — A documented operational procedure for recurring situations.
• Cascade Failure — When one component’s failure triggers failures in others, creating a chain reaction that can bring down an entire system.
• AI First Responder — An agent on the front of the incident lifecycle that triages the alert, gathers read-only context, and posts hypotheses before a human joins, with every fix gated behind approval.