QC step 2 — QC_FIX correction layer

kerfmaster pin list · Agreed & queued (build after fidelity)

intentmixedWhat we want to build. Never claimed the present, so it cannot be stale — and must never be read as a description of the code.

Content last changed 2026-08-02 — computed from the item itself, not typed.

Contract — QC stage

This contract describes a stage we intend to build — it is NOT a description of the code.

takes topology

makes healed-geometry

fails if A correction applied silently rather than as a separate, labelled, deletable layer.

Contract last changed 2026-08-06 — computed, not typed. Dated separately from the text above, so neither date can speak for the other.

1 open question blocks this pin

Q16 Snap gaps at or under 0.5 thou, flag from there to 60 thou -- are those the right numbers, and should the snap stay silent?
Aristide, Jordan — Reporting what was stitched or closed is QC step 2's job, and it is not built.

Attempt an auto-fix of each flagged anomaly as a separate, per-flag, labeled, deletable layer. The operator accepts (push to production) or deletes and fixes by hand.

Status: not built — and note the order things happened in. The first QC auto-fix already ships without any of this machinery: heal.close_micro_gaps() closes sub-0.5-thou gaps on every heal (item 9), unlabelled, on no separate layer, with no accept step and no way to delete that one fix. Grepping the code finds no QC_FIX layer and no accept/reject path anywhere.