Review contracts for
Unity production
workflows.
Practical, primary-source-backed checklists for deciding what a CI review can observe, how to make the evidence comparable, and where the claim must stop.
Unity build-delta review
A repeatable way to compare a candidate Unity build with an accepted baseline and turn package growth into traceable review evidence.
Read the field guide ↗Unity project integrity in PRs
A conservative checklist for catching meta/GUID, serialized-reference, LFS, and package-state damage before a Unity branch lands.
Read the field guide ↗Mobile release-artifact diff
A package-first checklist for reviewing store-facing contract and payload changes between accepted and candidate mobile releases.
Read the field guide ↗Unity CI failure triage
A deterministic workflow for separating shared log noise from the first materially divergent failure chain and choosing one bounded next check.
Read the field guide ↗Unity editor iteration regression review
A controlled checklist for comparing compile, assembly-reload, asset-import, and enter-play timings without turning environment noise into a regression verdict.
Read the field guide ↗Comparable input.
Traceable evidence.
Explicit unknown.
These guides define evaluation surfaces for XeSoft's private-pilot proposals. They are published to make the reasoning inspectable—not to imply a deployed product, customer result, or automatic diagnosis.