Tutorial Custom Validation Policy

← Home

Tutorial: Build a custom validation policy

Take a default solarxy.toml from zero to a tuned policy that matches your studio's asset categories, tolerances, and which checks make sense for your pipeline. Aimed at technical directors taking ownership of validation gates.

Phase 1 scaffold. The full tutorial lands in Phase 2. See Configuration for the schema reference and Validation Reference for what each check does.

• Goal
• Setup
• Steps
• Verify
• What you learned
• Where to go next

---

Goal

Phase 2: a solarxy.toml that classifies your studio's assets correctly and gates CI without false positives.

---

Setup

Phase 2: a representative folder of assets across every category you care about.

---

Steps

Phase 2:

1. Start from a default solarxy.toml.
2. Define [budgets] for hero / mid / prop / background (or your own labels).
3. Define [[filenames.rules]] regex patterns mapping filenames to budgets.
4. Tune [validation] toggles - flip off checks that don't apply (e.g. set allow_open_mesh = true for deliberately unsealed assets).
5. Tune [thresholds] - triangle_budget_tolerance_percent for the warning band, flipped_normal_dot for normal sensitivity.
6. Re-run on the asset folder and iterate.

Screenshots to capture:

• img/tutorial-policy-toml.png - the annotated solarxy.toml open in an editor with schema completions hovering.

---

Verify

Phase 2: zero false positives on known-good assets; expected findings on known-bad assets.

---

What you learned

Phase 2: how the per-category budget mechanic composes with the tolerance band, when allow_open_mesh is the right call, and why thresholds.flipped_normal_dot = -0.5 is the default.

---

Where to go next

Phase 2: pointers to Validation Reference and the CI tutorial.

---

See also: Configuration · Validation Reference · CI/CD Integration · Tutorial: Validate in CI