← BUILD DELTA GUARD / LOCAL LAB
LOCAL TECHNICAL PREVIEW
No upload. No model. No runtime-performance theatre.

Match the build contract.
Then review the movement.

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.

EXECUTION
Entirely in your browser
CORE EVIDENCE
Build size + duration
POLICY
Absolute + relative ceilings
FAIL-CLOSED
Contract mismatch becomes unknown
LOCAL WORKBENCH / BUILD-DELTA-V0.1

Compare one accepted build with one candidate.

VISIBLE POLICY / BUILD-BUDGET-V0.1

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.

Total build output+25 MiBAND +2%
Texture payload+16 MiBAND +5%
Audio payload+8 MiBAND +5%
Shader variants+5,000AND +10%
Addressables bundles+20 MiBAND +5%
Scene payload+10 MiBAND +5%
Duplicated bundle payload+5 MiBAND +10%
Build duration+60 sAND +10%

Nothing in either summary leaves this browser. Use only numeric build evidence, package versions, and non-sensitive contract labels. Do not paste logs, source, project paths, credentials, personal data, or confidential names.

WHAT THIS PREVIEW PROVES
01

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.

02

Traceable signals

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.

03

Visible budgets and coverage

Each numeric signal has absolute and relative ceilings. Missing optional evidence keeps the result in review; it never becomes a silent pass.

04

Bounded inference

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.

Unity BuildSummary reference ↗Addressables build-layout reference ↗
PRIVATE PILOT

Need the summaries produced inside the real build job?

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.