Evidence guide · 22 published records
AI for troubleshooting and recovery
Compare reversible diagnostic and recovery plans for software, devices, files, accounts, and reproducible bugs.
The decision this guide supports
Does AI start with evidence and reversible checks, or jump to a risky fix before the cause is known?
- Published records
- 22
- Average first score
- 2.7/10
- Average final score
- 7.2/10
- Average gain
- +4.5
- Worked / mixed / failed
- 11 / 9 / 2
Averages use 22 records with a disclosed first score. The set contains 22 synthetic benchmarks and 0 file-backed tests; it is a task collection, not a representative model leaderboard.
What the records compare
Evidence before a recommendation.
Diagnostic order, rollback paths, data preservation, stop conditions, and verification after a proposed repair.
Across this released set, 2 records failed and 9 remained mixed after the single correction. Those outcomes stay in the guide because a useful decision needs the misses as well as the wins.
- Capture symptoms and state before changing anything.
- Prefer reversible diagnostics and preserve healthy data.
- Define a stop condition for destructive or privileged steps.
Representative evidence
Open the prompts and checks.
The sample deliberately includes different verdicts when available. Every card opens to the full first result, correction, final result, and evidence boundary.
Completed field testSynthetic benchmark
Why Does This Certificate Chain Break on One Client
This completed synthetic TLS Diagnosis field test asked the session to debug a certificate-chain failure that affects one client, preserved an actual five-row tls chain diagnostic record, and derived 2/10 then 10/10 from task-specific semantic checks after one failure-only correction.
Completed field testSynthetic benchmark
Why Is the Test Computer Running at High CPU? An AI Diagnosis
This completed synthetic CPU Performance field test asked the session to diagnose unexplained high cpu usage, preserved an actual five-row high-cpu causal trace, and derived 0/10 then 6/10 from task-specific semantic checks after one failure-only correction.
Completed field testSynthetic benchmark
Does an AI Backup Design Survive a Clean Restore
This completed synthetic Backups field test asked the session to design a backup that can actually be restored, preserved an actual five-row restorable backup design, and derived 0/10 then 4/10 from task-specific semantic checks after one failure-only correction.
Completed field testSynthetic benchmark
Recover a Corrupt Git Branch with Reversible Steps
This completed synthetic Version-Control Recovery field test asked the session to recover a corrupted Git branch without overwriting healthy history, preserved an actual five-row reversible git branch recovery plan, and derived 0/10 then 8/10 from task-specific semantic checks after one failure-only correction.
Completed field testSynthetic benchmark
What Does This Kernel Panic Actually Point To
This completed synthetic Kernel Diagnostics field test asked the session to diagnose a kernel panic from a bounded evidence packet, preserved an actual five-row kernel panic causal analysis, and derived 4/10 then 10/10 from task-specific semantic checks after one failure-only correction.
Completed field testSynthetic benchmark
Does AI Reproduce an Environment-Specific Software Bug Reliably
This completed synthetic Bug Reproduction field test asked the session to reproduce an environment-specific software bug, preserved an actual five-row environment-specific bug matrix, and derived 4/10 then 10/10 from task-specific semantic checks after one failure-only correction.