failure-taxonomy

You can categorize software failures by assigning specific categories like test_failure or api_error, and track their occurrence frequency using a local JSON file that maintains persistent failure counts and prevention status.

Preventing recurring build failures involves mapping incidents to predefined taxonomy categories and implementing preventative measures, automatically suggesting checklist additions like running tests after file edits when a category exceeds a frequency threshold.

Failure taxonomy integrates with error tracking and circuit breaker patterns by mapping detected incidents to predefined taxonomy categories, allowing systematic categorization that supports circuit breaking based on tracked failure frequency.

Yes, you need a local JSON file for persistent failure tracking, which stores the occurrence counts for each failure category and tracks the status of preventative measures across incidents.

Yes, when an API error or similar failure category occurs multiple times and exceeds a defined frequency threshold, the system automatically suggests or adds preventative measures to your team's checklist.

You should avoid using a predefined failure taxonomy when your incidents do not fit distinct categories like timeout or build_failure, or when you lack a local environment to maintain the persistent JSON tracking file.