uberrca

What problem does it solve?

UberRCA prevents repeated failures by forcing evidence-backed, class-level root cause analysis before proposing durable patches.

Core Features & Use Cases

• RCA ladder to class-level cause: Moves from symptom and immediate failure to enabling conditions, failed invariants, upstream admission failures, recovery/detection gaps, and class-level design causes.
• Proximate-cause rejection: Treats “prompt told the agent,” “the model erred,” and “it timed out” as incomplete until deeper missing policies, state constraints, or monitors are identified.
• Self-challenge and convergence tests: Requires the analyst to prove the cause names an enforceable invariant whose enforcement would make the failure class impossible.
• Repeated-failure workflow: If the same failure family repeats (notably at five consecutive clear test failures), it preserves evidence, halts blind patching, and routes revised hypotheses to planning/routing skills.

Quick Start

Use uberrca to investigate why a recurring bug or agentic-system incident keeps happening and to identify the upstream invariant whose enforcement would have prevented the failure class.