Editor Iteration Guard runs one controlled base-versus-change Unity fixture, then reports comparable compilation, assembly reload, asset import, and enter-play-mode deltas against agreed budgets.
Same fixture, runner, Unity version, target, and cache state.
A fail-closed iteration report that shows repeatable medians, run spread, budget status, and the exact comparability reason whenever a result must remain unknown.
The first pilot uses the subset that matches your workflow. The rest stay out of the way until they earn their place.
Check runner, Unity version, target, cache state, fixture version, warm-up, and repetition count before evaluating a delta.
Compare scripted compile duration across repeated base and candidate runs instead of treating one editor session as a benchmark.
Separate reload cost from compilation so the owner can see which part of the edit loop moved.
Report attributable import timing and touched-asset evidence only where the Unity output supports it.
Measure one agreed transition fixture with the same configuration; unrelated runtime performance remains out of scope.
Apply absolute or relative budgets to comparable medians and retain the evidence needed to review the trend.
The first pilot is an evaluation contract, not an open-ended integration. The evaluator decides whether one real workflow became clearer or faster.
Tools engineer, technical director, engineering lead, or developer-productivity owner.
One scripted interaction fixture run repeatedly on the same runner, Unity version, target, cache state, and project revision metadata for an accepted base and candidate change.
Comparable compile, reload, import, and enter-play medians with spread, budget status, evidence references, and an explicit unknown result when the fixture is not comparable.
The evaluator can reproduce one material regression or clear one suspected regression without relying on a single noisy timing sample.
Once the contract above is confirmed, the first report is prepared within one week. No platform migration and no quarter-long rollout.
Name the evaluator, review point, safe input, exact output, transfer method, and success criterion.
Run a read-only analysis step in the current workflow or against the agreed sanitized sample, then produce the first report.
Run it against representative changes, tune noise, and decide whether the next scope is justified.
No. Unity's profiling and import tools diagnose individual activity. The pilot adds a controlled revision comparison, comparability gate, repeatable budgets, and a reviewable history around one editor-loop fixture.
No. It reports observed timing deltas and traceable evidence, not blame or automatic root-cause certainty. A changed-path correlation stays informational unless the evidence is sufficient.
A first CI-local or controlled-runner report for one agreed fixture after the evaluator confirms the runner, cache, Unity configuration, repetitions, budgets, and success criterion.
A controlled checklist for comparing compile, assembly-reload, asset-import, and enter-play timings without turning environment noise into a regression verdict.
Read the workflow checklist ↗Describe the recurring production problem and the smallest representative input you could evaluate. XeSoft will first confirm whether this narrow pilot is a fit—and say so plainly if it is not.
Prefer email? outreach@xesoft.dev
We will tell you what a useful one-week pilot can cover—and what it cannot.
Request a private pilot ↑