Build Delta Guard
A candidate Unity build moved and the reviewer cannot explain the material delta.
Build evidence can explain composition; it cannot establish runtime frame time or memory residency.Read the evidence contract ↗Start with the failure event.
Leave with one testable check.
Choose what happened, the comparable evidence you can produce, the decision that pays the cost, and how the workflow is covered today. The diagnostic routes those facts to one of five distinct technical previews and tells you what would make that route the wrong fit.
- INPUT
- Four workflow choices
- PROCESSING
- Only in this browser tab
- OUTPUT
- One first check + one route to rule out
- STORAGE
- None
Nothing is transmitted. Answers and the recommendation exist only in this browser tab. No analytics event, account, cookie, local storage, or server record is created.
The diagnostic does not collapse everything into “Unity CI.”
Each route starts from a different event, evidence surface, owner, and falsifier. Open the source-backed field guide before treating any result as a gate.
Project Integrity Bot
A Unity branch may contain structural repository damage before anyone opens or merges it.
Static evidence can expose contradictions; it cannot prove merge safety or replace opening the project when evidence is incomplete.Read the evidence contract ↗Mobile Release Auditor
An Android or iOS release candidate changed at the package layer before submission.
Package evidence supports release review; it does not sign, submit, or guarantee store acceptance.Read the evidence contract ↗Build Failure Fingerprinter
Unity CI is red and the failed log does not expose one bounded next diagnostic check.
The comparison narrows triage; it does not guarantee complete redaction or claim automatic root cause.Read the evidence contract ↗Editor Iteration Guard
Compilation, assembly reload, import, or enter-play time moved in the daily editor loop.
A controlled fixture measures one editor loop; it does not attribute blame or generalize across mismatched machines.Read the evidence contract ↗EVIDENCE BOUNDARYA route is not a diagnosis.
A route is not a diagnosis.
A preview is not adoption.
The recommendation only selects the narrowest existing test. Every evaluator still applies its own comparability gate and explicit unknown outcome. No answer, recommendation, page visit, or local result is counted as studio interest.
Product evidence begins only when a verified studio owner explicitly submits workflow context and evaluation intent through the separate consented form after trying a preview.
Review the response-data boundary ↗