Collection catalogs
Debugging and incidents collections
Find out what failed, keep the evidence and recover without making the problem worse.
6 collections · 80 unique ideas. Collections may share an idea.
Choose a collection
Catch weak signals before they become expensive errors
Use near misses, risky successes, repeated workarounds, leading indicators and layered safeguards to find weak points before harm repeats, while keeping reporting separate from verified improvement.
Change live systems without turning one mistake into a large one
Make software, configuration and bulk-data changes easier to test, observe, retry, stop and recover before their blast radius becomes the main problem.
Design routine work so ordinary human slips do less damage
Separate slips from mistakes, reduce avoidable dependence on memory and vigilance, and use constraints, standardization, workload checks and recovery paths when the cost of an error matters.
Find the failure without creating a second incident
Reduce a reproducible failure, locate its boundary and control the risks of retries, concurrent edits and recovery.
Find the fault without making the incident harder to understand
Turn vague technical failures into smaller tests, controlled incident work and system-level learning that another person can verify and reuse.
Operate AI agents as systems you can replay, verify and constrain
Add practical 2026 agent-engineering techniques for replay, evaluation, tool routing, computer use, scoped authorization and deterministic execution without turning conference claims into universal guarantees.