Acting on the results
Verification checks
The comparison includes added, changed and deleted source files, even when the caller omits a new helper. Each helper uses its own resolved analysis configuration. Existing finding identity and severity are compared; merely keeping the same total finding count does not hide a different finding.
Packing detection
If code lines fall from 100 to 50 but tokens fall from 1,000 to 950, the ratio is0.05 / 0.50 = 0.10. The default threshold is 0.6, so that reduction is attributed mainly to packing. The verdict reports the attributable lines and the ratio used. Verification counts code without comments; ordinary file-length findings keep their existing total-line metric.
An exact certified mechanical result is exempt from the packing penalty. Iris Code recomputes the fixes from its owned baseline and requires the entire current source to match one certified fix or the complete certified batch. Extra packing or other source edits do not qualify. Imports, exports, parse failures and new findings are still checked; the result discloses the exemption and configured ratio.
Baselines
A standalone CLI process cannot carry its in-memory baseline into a later process. An unknown baseline ID is refused rather than substituted with HEAD. Every verdict reports
disabledChecks and packingRatioUsed; disabled checks reduce the evidence available.
Verification is advisory and cannot prove behaviour equivalence. A regression or failed check does not change CLI verification’s exit status; argument and baseline errors still fail normally. The correction gives a concrete next move and names failed checks or omitted evidence.