Auto-generated fixes on a misdiagnosed alert? That's what these gates prevent. Every fix must survive all six — or a human decides.
Layer 01
CONFIDENCE GATE
Every diagnosis comes with a confidence score derived from the actual logs, stack traces, and build output. Below 30%, the pipeline halts and escalates to a human. No guessing. No 'maybe this will work' deployments.
< 30%
confidence = abort
CONFIDENCE GATE
Layer 02
SELF-REVIEW
A second AI pass acts as a code reviewer. It checks for regressions, type errors, missing imports, and unnecessary changes. Score below 70? The fix is rejected before it ever touches a branch.
< 70
review score = reject
SELF-REVIEW
Layer 03
FILE BLOCKLIST
.env, .lock files, CI configs, migration files, credentials — hardcoded blocklist. No override, no flag to bypass. The AI physically cannot generate changes to these paths.
0
exceptions
FILE BLOCKLIST
Layer 04
CI MUST PASS
The fix runs through your full CI pipeline. If it fails, the AI analyzes the CI error and tries a completely different approach — up to 3 times. Three failures? Escalates to your on-call. No PR is created.
3×
retry with different approach
CI MUST PASS
Layer 05
TRUST LEVELS
Every project starts at Rookie — draft PRs only, human must approve every merge. The system earns trust through successful fixes with passing CI and no regressions. Each level unlocks tighter auto-merge gates.
ROOKIE
Draft PR only
Human approves every merge
APPRENTICE
Auto-merge enabled
Confidence ≥ 90% · Review ≥ 70 · ≤ 50 lines
TRUSTED
Expanded autonomy
Confidence ≥ 80% · Review ≥ 70 · ≤ 100 lines
EXPERT
Full auto-merge
Confidence ≥ 70% · Review ≥ 60 · ≤ 200 lines
Layer 06
POST-MERGE MONITOR
After merge, InariWatch monitors for 10 minutes. New errors detected? Automatic revert. The branch is rolled back, the incident is re-opened, and your on-call is notified. No human intervention needed.
10 min
active monitoring
POST-MERGE MONITOR
THE ANSWER
By default: 100%.
Every project starts at Trust Level 0 (Rookie). The AI creates draft PRs only. A human reviews and merges every single fix.
Autonomy is earned, not configured.
The system builds a track record. Fixes that pass CI, survive post-merge monitoring, and cause zero regressions count toward the next trust level. Bad fixes reset progress.
Even at maximum trust, 5 gates must pass.
If a single gate fails — low confidence, failed self-review, CI error, or too many lines changed — it falls back to a draft PR. Human decides.
Worst case: auto-revert in 10 minutes.
If a fix somehow passes all gates and causes a new error in production, the post-merge monitor auto-reverts the change. No human intervention needed.
PERSPECTIVE
Dev hotfix at 3 AM
InariWatch auto-fix