CDCDR Control RoomChaos-Driven Refactoring
GitHub

Resilience control plane

Break the system on purpose. Ship the architecture that survives it.

CDR injects load and faults into a real repository running in staging, captures the physical collapse, classifies the root cause, generates a refactor PR with full repository context and proves the fix by re-running the exact same scenario.

Analyze a repository

Runtime analysis: IBM watsonx Granite · CDR built with IBM Bob 2.0

Paste a GitHub repo. CDR queues a chaos run, classifies the collapse, proposes a refactor and verifies it. The worker executes queued runs with python -m cdr watch.

Runs tracked

8

7 completed

Collapses captured

7

under identical load profiles

Avg p95 reduction

94.0%

after verified fix

Avg AI diagnosis

3.1 min

vs 95 min manual SRE estimate

Pipeline

01

Inject chaos

k6 load + toxiproxy faults on a real target repo

02

Classify

telemetry + logs → failure category with evidence

03

Refactor

repository-aware diagnosis and generated patch

04

Verify

same chaos scenario re-run on the patched code

Experiment runs

Live updateavg 57.9s under chaos load before collapse