Use the result to choose the next action.

Start with the named check and its reason. Keep the original file, change one relevant input, then rerun; the checker does not repair or upload your document.

Binding FAIL: the declared context conflicts

Check event, year and session against the selected profile. In the inherited example, declaring CVPR workshop while selecting the main/Findings profile fails binding. Correct the declaration or choose the matching profile. A binding failure rejects applying that rule; it does not prove the conference rejects the PDF.

Geometry FAIL: an applicable size condition differs

The synthetic UAB A1 input is 594 × 841 mm, while its archived intended final-size rule is A0. Verify the intended print size and scale. If the source document is wrong, correct it and export again. If a printer will transform the file, establish that path instead of silently treating the input as final output.

For the archived CVPR scaling exception, a nominal mismatch can remain UNKNOWN. Do not turn that uncertainty into either unconditional acceptance or rejection.

UNKNOWN: inspection or evidence is insufficient

Resolve an uncertain result

Reason	Next action
Missing or future profile	Obtain a verified official rule for the actual context; do not substitute a different year.
Conflicting page boxes	Inspect intended artwork bounds and export settings using your tool’s documentation; clarify the print box.
Malformed, encrypted or unsupported PDF	Open the source in an appropriate local application and produce a supported single-page PDF if possible. No cloud fallback is provided.
Multiple pages, input cap or inspection timeout	Choose the intended single-page export; the local cap is 10 MiB and watchdog is 15 seconds. These limits are not print-quality rules.
Parser disagreement	Seek a qualified manual geometry check; do not average conflicting measurements.

Fonts, images, bleed and color remain separate

The generic font-program inventory can identify a missing program in a supported resource. It cannot establish correct font rendering, effective image resolution, bleed artwork or color proof. Changing a filename, reducing a file’s byte size or receiving a dimension PASS cannot clear those checks. Ask for an appropriate local/manual review and a print proof.

Practice with safe files

Use the clearly labelled synthetic example PDF for the A0 path. The accompanying project also contains six inherited synthetic inputs, including a deliberately invalid file and an ambiguous-box file. They demonstrate limited states, not a comprehensive PDF test suite or real-user error reduction.

Reset clears file and result. Changing context or file invalidates the result, and cancellation terminates the active analysis. A new export needs a new check.