Reliability Fallback Guard — v1.0
Category: orchestration
Price: $4.99
Released: 2026-08-06
What it does
Reliability Fallback Guard checks operator-provided operating notes for timeout handling, authentication failure recovery, tool-failure fallback paths, retry limits, and stability evidence. It returns a deterministic PASS / REVIEW / BLOCKED JSON report with scored evidence and actionable recommendations. Reads local notes only; no API calls, no live services, no config mutations.
Use cases
- Validate agent orchestration runbooks for timeout and retry coverage before deploying multi-step pipelines to production.
- Check that every tool-failure path has an explicit fallback documented, preventing silent failures from halting autonomous workflows.
- Give reliability engineers a fast, repeatable pre-flight gate for new service integrations, surfacing auth recovery gaps and missing stability evidence before go-live.
Requirements
- Python 3.8+
- Standard library only (
argparse,json,re,pathlib) — no pip dependencies, no network access, no external services.
Example usage
# Check from a notes file
python3 scripts/reliability_fallback_guard.py --notes /path/to/runbook-notes.md --json
# Check inline text
python3 scripts/reliability_fallback_guard.py --text "No timeout set; retry limit: 3; auth fallback: undefined" --json
# Run built-in self-test
python3 scripts/reliability_fallback_guard.py --self-test --json
Expected output:
{
"status": "BLOCKED",
"score": 31,
"evidence": ["timeout_handling: missing", "auth_failure_recovery: undefined", "retry_limit: present"],
"recommendations": ["Set explicit timeout thresholds for all external calls", "Document auth failure recovery path and token refresh strategy"],
"mutated_files": []
}
Self-test returns ok: true, clean fixture PASS, risky fixture BLOCKED, and mutated_files: [].