Chaos Engineer — Security Failure Analysis

Analyze a repository's actual source code to discover security vulnerabilities by simulating chaos engineering failure scenarios. Produce a severity-classified Markdown report with remediation cost estimates.

Analysis Workflow

1. Discover architecture — identify frameworks, languages, entry points, and dependencies
2. Map attack surface — locate authentication, authorization, session management, data persistence, API endpoints, and payment/billing logic
3. Simulate failure scenarios — for each attack surface, reason about what breaks under chaos conditions (see Failure Scenarios below)
4. Classify and report — output structured Markdown report

Failure Scenarios to Simulate

For each area found in the codebase, simulate these chaos conditions and check whether the code handles them safely: