I'm Chris, an SRE in Rexburg.

I keep software up for the people who depend on it.
I ship small changes to a few users first.

ResumeEmail meAGENTS.mdRead my posts

Chris Roos with his two kids

For you

Chris Roos with his two kids

Chris Roos

Site Reliability Engineer

SRE in Rexburg, Idaho, and dad of two. I use AI agents for the first hour of an incident and the routine work around it.

For your agent

> Point your agent at https://christwentyfour.com/llms.txt

Your agent can have my rules: paste AGENTS.md into its instructions. To load every page at once, fetch llms-full.txt.

Start here

  1. StrategyDocuments for incidents, deploys, access, and cost.
  2. The mathError budgets, small releases, canaries, and test suites, worked out with numbers.
  3. AutomationThe blueprint, then herdr, Jira, Claude Code, and the human approval step.
  4. PostsAlerts that earn the page, restores you've never run, staging that lies.
  5. RunbooksHow I use Terraform, containers, pipelines, observability, and Python, with example config.

My engineering strategy

A strategy is built on models and values. It tells you what to do to optimize for them.

4 min read

On this page

A strategy is built on models and values, and it tells you what to do to optimize for those models and values. It isn't a roadmap or a list of projects. A good one lets any engineer make the right call without escalating.

It differs from a runbook. A runbook is a checklist you run. A strategy is a value statement. Less of a checklist, more of a way to choose. With the right models and values, you can work out the next move yourself, in any position.

A strategy is a set of values

In chess, a bad strategy values pawns more than queens. A good one values queens more than pawns. Neither tells you which move to make. With the right values, you can work out the move yourself, in any position.

Engineering works the same way. Say "a deploy is worth more than a dollar of cost, as long as you stay above the SLO" and the next decision follows from it.

max Changes, min Cost s.t. Reliability ≥ ReliabilitySLA\htmlClass{sym}{\text{max}}\ \text{Changes},\ \htmlClass{sym}{\text{min}}\ \text{Cost s.t. Reliability} \text{ ≥ } \text{Reliability}_{\mathrm{SLA}}

Ship as many changes as you can, as cheaply as you can, as long as reliability stays at or above the SLA.

Good strategy vs bad strategy

GoodBad
Names the real problem in one sentenceRestates the goal ("be more reliable")
Picks a trade-off and says no to thingsTries to do everything
A few actions that fit togetherA pile of unrelated projects and OKRs
Plain wordsJargon
Gets revisited when the situation changesGets written once and filed

Strategy vs a runbook

StrategyRunbook
QuestionWhere do we spend effort?How do we do this step?
HorizonQuartersMinutes to days
Aided byModels and values: equations, charts, what each thing is worthDiscipline, training and docs: checklists, practice
Fails whenThe model is wrongA step gets skipped
ExampleShip as many changes as the SLO allowsRoll back a bad deploy in under 5 minutes

Rule:if you're deciding, reach for models and values. If you're doing, reach for discipline and a runbook.

Diagnosis, in this framing, is the runbook: the checklist you run once you know where you are. The takeaways of a strategy are its guiding principles. What you can produce are the coherent actions: what you, or your agent, can make once you understand the models and values and follow the strategy.

The operational documents, the checklists themselves, start at Start here. Tool runbooks are under Runbooks.

Takeaways

These are the guiding principles of the engineering strategy, as it stands. They come out of the models below, not the other way around.

  1. Reliability is a constraint, not a number to maximize. Meet the SLO, then spend the rest of the budget on change.
  2. Impact is the downtime people feel: how many people, for how long, how much of the system they need. Cut who sees a bad change, and how long they see it.
  3. Deploy is not release. Put code on a server without making it visible, and you can ship often and still control exposure.
  4. Make changes cheap to get wrong. Halve the fix time and you double what you can ship.
  5. If you can't write the check, you don't know what done means yet.
  6. Work that ships more changes, or cuts toil, goes first. Priority is changes divided by cost.

What you can produce

Follow the strategy, and understand the models and values under it, and you or your agent should be able to produce these without waiting for a new page from me:

  1. A runbook for a system you have diagnosed: the checklist you actually run. Start from Start here and the runbooks.
  2. The desired-state checks for a change: what must be true when the work is done.
  3. A change policy for a service: what can go out unattended, what needs a human, and what "reversible in 5 minutes" means here.
  4. An agent brief that uses the same models and values, so the agent can propose a change you would actually accept. AGENTS.md is the starter.

The documents

The engineering strategy will be several documents. Reliability and change management is first. DevOps and agentic tool use are coming.

  1. Reliability and change management. The models for shipping change under an SLO: error budgets, impact, smaller releases, tests, desired state, and deploy vs release.
  2. DevOps. Coming. Until it is written, use the runbooks and the notes on toil and elite delivery in the reliability document.
  3. Agentic tool use. Coming. Until it is written, use Working with Claude, the automation blueprint, and AGENTS.md.

The runbooks have example config for each tool and the Claude workflow I use with it.