Weld Log Auditor

The failure mode in a weld dossier is a MISSED ROW, not a wrong number: a 93%-complete exception list is strictly worse than none, because the shop ships it believing it is clean. Point Weld Log Auditor at the five files a fab shop already keeps — weld log, welder continuity list, WPS register, PQR register, NDT index — in CSV, TSV or XLSX, and it builds the cross-reference in the tab. Nothing leaves the page: no fetch, no upload, and the weld data is never stored; you re-drag the files each run, so a client-NDA or defense job has no residency question at all. The rule set is the product surface. Each rule prints the clause it enforces, its tier, and the rows it examined, so a CWI can audit the rule rather than trust it: HARD rules (ASME IX QW-322.2 six-month continuity per welder × per process with the renewal-coupon semantics, WPS on the approved register, NDT disposition where the job ITP demands it, orphan NDT rows, duplicate weld numbers, welds after a stencil was retired, repairs without their own WPS or re-examination) and ADVISORY rules that ship off until confirmed for the job (PQR thickness/P-number/F-number ranges with carve-outs, NDT report wording, RT interpretation authority as a contract-spec check). Acceptance-criteria numbers are never bundled: they are entered once per job, because a stale table for the wrong code edition is exactly the error this tool exists to prevent. Join coverage is a first-class output printed before any verdict — welds, matched, unmatched stencil strings, unparsed dates — and the completeness statement is refused when coverage is not provable, with the unmatched rows listed. Entity normalization is an explicit reviewed diff (stencil aliases approved by hand), never a silent regex. The deliverable is a signed completeness statement with each source file's SHA-256 plus a CSV exception list, and a forward-looking list of who goes out of continuity next and which welds that puts at risk. The heat-number/MTR and scanned-