gateway-debug

A zero score on your model qualification run indicates a critical G0-G4 gateway failure. Diagnose the exact cause by interpreting evidence JSON, stderr output, and MQS zero-scores to identify issues like loading errors, crashes, or output quality failures.

LAYOUT-002 violations during model qualification occur when output formatting does not meet structural requirements. Pinpoint these specific layout failures by analyzing the evidence JSON generated during the G4 output quality gateway checks.

Diagnose a G0-INTEGRITY failure by checking for config.json mismatches and incorrect model integrity. Analyzing stderr output and evidence JSON helps pinpoint contract invariant violations (I-1 through I-5) that block model loading.

Troubleshoot garbage output in model qualification by identifying GarbageOracle patterns in the inference results. This analysis determines if the issue stems from G2 inference problems or G4 output quality failures, guiding targeted fixes.

Interpret MQS zero-scores by mapping them to specific G0-G4 gateway failures. A decision tree helps quickly identify whether the zero-score originates from model integrity, loading issues, inference problems, stability, or output quality.

A G3 stability failure means your model qualification run crashed during execution. Perform crash analysis on the stderr output to determine if the instability is caused by memory issues, contract invariant violations, or conversion diagnostics errors.