Proof Suite — Twelve Checks, One Verdict On The Whole Delivery

Twelve tools that already work on their own. What the suite adds is theanswer none of them gives alone: can this delivery go out?

One run over the whole folder

Point it at what you are about to send. Every file inside is checked by everytool you own, and you get a single report and a single verdict for the lot.

Each file is opened in its own background Blender. The scene you have open isnever touched — not opened over, not saved, not modified in any way. That isalso why a file that will not open costs you only that file: the rest of thedelivery is still checked, and the report says which one failed and why.

Each file is opened once for all twelve checks, not once percheck. Measured on three checks over two files: the combined run took 21 to 26per cent less time than running them separately, and the saving grows with everytool you add.

A report that leaves with the files

One self-contained page. The verdict first, then one sentence a lead can readwithout scrolling, then the numbers, then every finding with its address andwhat to do about it.

Nothing in it is loaded from the internet — no fonts, no styles, no scripts.It opens in six months on a machine with no network, which is exactly whensomeone asks what you delivered. Attach it to the email, drop it in the deliveryfolder, or keep it as your own record.

A gate, not a button

The same run works with no interface and no person, and finishes with a codeyour build system can read: clean, something blocking, or could not be checked.

Those last two are deliberately different. A check that did not runhas not passed. A gate that treats silence as success will one day wavethrough the very delivery it was built to stop. For the same reason, a tool youdo not own is named in the report rather than quietly absent.

It remembers last time

Save a run as a baseline and a later run tells you what moved, in which direction, and which findings are new. Direction is never guessed: eachmeasurement carries its own sense of which way is worse, so rising coveragereads as better and rising drift reads as worse.

Sign-off that lives in the file

One button records what was checked, when, with which tools and versions, andwhat came out — inside the .blend itself. Open that file next month and thepanel says so before you press anything. Save the file afterwards and the recordsays it is out of date, because a record that stays quiet about later edits isworse than none: people believe it.

Seven of the twelve also repair

Where a repair can be made without deciding something that is yours todecide, it is made — and proved by measurement, not by the warning going quiet.

• BindProof predicted a vertex would sit 893.917 mm out of place in the game engine, repaired the weights, and the skin moved by 893.917 mm. The prediction and the result agree to a ten-thousandth of a millimetre.
• DeformProof put weights back from its snapshot and took the drift from 615.134 mm to 0.000. Undo does not survive closing a file; the snapshot does.
• RetopoProof pulled drifted vertices onto the original surface: worst deviation 50.000 mm before, 0.000 after, with the topology untouched.

Where a repair would mean guessing, it is not made. An unbound vertex isnever assigned to "the nearest bone", because that is how an ear ends up sewn toa shoulder. Rig Inspector changes nothing at all, on purpose — its whole promiseis that it reads a rig without touching it.

One sidebar tab

Own twelve tools and you would have twelve tabs. One click puts them all in asingle tab, collapsed, with one delivery panel instead of twelve. One click putsthem back.

What is inside

• Rig Inspector — what is broken in a rig, without changing anything in it
• Modifier Profiler — which modifier is eating your viewport
• Cache Commander — what your simulation caches weigh, what is stale and what belongs to nothing
• ShadeProof — why the shading looks wrong, and it repairs it
• PathProof — pink textures found, relinked and proved
• HandoffProof — how your file opens for the person you send it to
• AnimProof — whether a bake moved the pose
• DeformProof — whether a weight edit broke the deformation, and it puts the weights back
• RetopoProof — how far the retopology sits off the sculpt, and it pulls it back
• SampleProof — how many samples this shot actually needs
• BindProof — whether the skin is really bound, and it fixes what the engine would drop
• OverrideProof — whether override edits survive reopening the file

Compatibility

• Blender: 4.2 LTS through 5.2
• OS: Windows, macOS, Linux
• No dependencies to install. Nothing is downloaded at any point, and nothing leaves your machine.

Tested

8769 automated checks across Blender 4.2.9 LTS, 5.1 and 5.2 — zero problems.That includes installing all twelve into one Blender at once and confirmingthat among 432 operators, 193 panels and 96 scene properties nothing collides,that switching them all off leaves nothing behind, and that switching them allback on works.

Every number in this description is a measurement taken on a real scene, not an estimate.