Exact build-contract gate
Ten environment and build labels must match. A candidate built under a different target, format, runner, compression, or entry point cannot receive a budget verdict.
This working preview compares an accepted Unity build summary with one candidate. It requires the Unity version, target, artifact format, backend, configuration, architecture, stripping, compression, entry point, and runner profile to match before applying visible size, payload, shader, Addressables, duplication, duration, and dependency rules.
Two ceilings per signal. Crossing both is a failure; crossing one requires review. Missing optional evidence also requires review. A malformed core value or any build-contract mismatch makes the complete verdict unknown.
Ten environment and build labels must match. A candidate built under a different target, format, runner, compression, or entry point cannot receive a budget verdict.
Core totals map to BuildSummary. Optional payload, Addressables, duplication, and shader counts remain visibly tied to the declared exporter source rather than inferred from a source diff.
Each numeric signal has absolute and relative ceilings. Missing optional evidence keeps the result in review; it never becomes a silent pass.
The result can prioritize one evidence source and show dependency movement. It cannot establish runtime memory, frame time, root cause, blame, or release approval.
Unity's BuildSummary exposes platform, output size, duration, result, warnings, and errors. Addressables build-layout data exposes bundle and asset sizes, dependencies, and duplicated assets. The preview accepts a narrow summary of those surfaces; it does not request a repository or raw artifact.
The free evidence kit exports the two core BuildSummary signals and registered package versions without project content. A private pilot adds approved optional evidence, baseline lookup, studio-owned policies, PR output, and an evaluator-owned success test inside the studio's CI boundary.