Larkspur Systems · Engineering · Fictional example
Q3 review · Through September 6

Delivery recovered.
The release gate hasn’t.

We are deploying again. One unfinished safeguard still lets a data-dependent regression reach production.

Ines Fontaine · September 7, 2026

1
01 / Delivery

Back to 26 deploys a week.

26

Week 36
11 the week before

3.8%

Change failure rate
18.2% the week before

The freeze ended after the index and timeout fixes landed.

Illustrative deploy log · August 31–September 6, 2026

2
02 / The gap

The canary passed.
The busiest region failed.

CanarySmall datasetQuery passes
EU production9× the dataPool exhausted

Small test data hid an unindexed query. An absolute latency limit did not catch the regression.

Illustrative incident review · August 27, 2026

3
03 / The response

Fix the query.
Then fix what let it through.

ChangeState
Partial index and 2-second pool timeoutShipped
Hold on a 25% relative latency increaseIn review
Explain queries against realistic data volumeProposed
4
04 / The tradeoff

One week on the gate.
One week later on webhooks.

Borrow a release engineer to finish and validate the gate. Webhook rollout moves from September 22 to September 29.

We can keep the original date by accepting the same release risk for another week.

5
Decision / September 9

Give the release gate
the next week.

Approve the engineer’s time and the revised webhook date.

Ines owns the gate review on September 12. Reopen the schedule if it does not pass.

Fictional scenario · Published with Shareout

6
1 / 6