GuideIncident response
What did the postmortem fix prove?
Separate a completed task from evidence that the underlying risk was reduced.
Articles
Guides, news and explanations about AI and reliable systems.
ExplainerAI in production
The operational cost of AI tokens
Account for context limits, retries, latency, and the work behind a useful result.
GuideIncident response
Why a 5 Whys investigation can branch
Evidence can split a 5 Whys investigation into several contributing causes. A concurrency example shows how to turn those explanations into useful tests.
GuideAI in production
Comparing incident sources with NotebookLM
Conflicting restart instructions show where a source-backed notebook helps: finding the relevant passages, dates and exceptions for the runbook owner.
ExplainerPlatform engineering
GPU capacity depends on power and cooling
Power and cooling affect the work a GPU pool can sustain. Device signals, request completions and queue growth help distinguish a physical limit from a workload change.
GuideAI in production
Evaluating Claude Opus 4.6 for incident work
A rollback exception tests whether Opus 4.6 preserves decisive evidence across a long session, and whether the resulting answer arrives in time to help.
GuideAI in production
Recovering an interrupted agent skill
A timed-out scaling request needs a durable record and destination-state checks. Reusable operational skills need to recover unfinished work as well as start it.
ExplainerAI in production
How an AIOps finding becomes an agent action
A rollback proposal crosses from recorded evidence into a changing system. The handoff carries source references, current preconditions and unfinished actions.
The on-call work that page counts leave out
Disturbed nights, specialist help and cleanup consume capacity beyond the primary shift. A workload worksheet connects that demand to staffing and delivery plans.
CommentaryObservability
What AIOps alert correlation can hide
Grouping can shorten the incident queue while hiding a second failure. Following a replay past the first mitigation reveals whether that failure stays visible.
GuideSLOs & reliability
Release gates that hold up under incident pressure
An error-budget hold needs a route for an urgent repair. Fresh measurements, artifact-specific exceptions and recovery criteria determine how that route works.
GuideIncident response
Keeping incident state consistent across PagerDuty, Jira and Slack
A reference design for duplicate deliveries and partial API success, with durable incident identifiers and summaries drawn from the resulting record.