By-origin battery

Defect

Two QBI booleans — business_is_sstb and SSTB-qualification — are deterministically failing by-origin battery comparisons: QBI reconciliation intentionally clears these flags on clone 0 because base ASEC lacks frozen PUF QBI observations (qbi_inputs.py:1228), while the battery registry hardcodes clone-0 comparisons (stacked_spine.py:3015) and the comparator deliberately fails zero/zero booleans (stacked_spine.py:13660).

Evidence this is clone-role incompatibility, not absence: processed PUF source positives are ~31.6k/30.7k for the two flags, final clone-1 positives ~37.9k/37.6k — clone 0 alone is intentionally zero.

These two comparisons cannot pass under the current contract on any build, at any scale. They appear as 2 of the 78 failure reasons in the 25% candidate gates receipt and in every 1% diagnostic.

Fix direction (owner adjudication)

Either register these targets against the clone that owns them, or give zero/zero-with-populated-sibling-clone comparisons an explicit non-fatal status. Adjudicated spec change, not a tolerance tweak.

Start by reading qbi_inputs.py:1228 and the clone-0 battery registration in stacked_spine.py:3015, then inspect the zero/zero comparator at stacked_spine.py:13660 and reproduce the two failures in the candidate-gates receipt. Done means the clone-role contract is adjudicated and these comparisons no longer appear as deterministic failure reasons, with the relevant battery diagnostics confirming the result.