asset-validation-debug

Asset validation failures are diagnosed by mapping warnings or errors from asset_validate() to concrete repair primitives, selecting the cheapest effective strategy within a defined retry budget, and re-validating to confirm resolution.

The retry budget limits automated repair attempts during asset validation by enforcing a defined threshold, minimizing looping by applying cost-effective repair primitives and escalating if failures persist beyond that budget.

An automated diagnosis tree classifies asset pipeline failures as local, global, or compositional to determine the appropriate remedy, selecting cost-effective repair strategies based on the specific failure type identified.

When repair primitives exhaust the retry budget, you escalate the failure by generating a diagnostic payload for further analysis, particularly if the failure recurs or requires routing policy changes.

Asset validation repair supports escalation for persistent failures by providing a diagnostic payload when repairs exhaust the budget, indicating when routing policy changes are required to resolve the issue.

Available repair primitives for fixing asset validation warnings include matte, inpaint, route-change, and seed-sweep, each mapped to specific validation codes to apply the most cost-effective remedy.