failure-forensicslisted

# Failure Forensics **Problem shape:** something failed (or will fail) and the evidence is being averaged away, cleaned up, or explained by its most convenient story. The move: treat anomalies as data, reconstruct the timeline at the right timescale, and design the degraded state as a first-class behavior. ## Relevant geniuses | Agent | Use when | |---|---| | [hamilton](../../agents/genius/hamilton.md) | overload and simultaneous failure scenarios; priority shedding by criticality; the degraded mode is undesigned; "users will never do that" | | [mcclintock](../../agents/genius/mcclintock.md) | aggregate metrics look smooth but one specific case is weird; a class of observations is being trimmed as noise | | [fleming](../../agents/genius/fleming.md) | anomalies keep appearing during routine work and being cleaned up; "that's weird" said and never investigated | | [ginzburg](../../agents/genius/ginzburg.md) | reconstruct what happened from marginal traces and involuntary evidence (logs, timestamps, artifacts nobody meant to leave) | | [braudel](../../agents/genius/braudel.md) | the incident needs three-timescale decomposition — event, cycle, structure — before a root cause is named | | [wu](../../agents/genius/wu.md) | the failure hides under an assumption everyone considered too obvious to test | | [maxwell](../../agents/genius/maxwell.md) | the system oscillates, overshoots, or hunts — feedback stability and gain-margin diagnosis | ## Invocation 1. Pick the best-fit agen