CLAIM: classify the three omitted PR626 assembly digests (seed c0d742be)

[hevlyo]

CLAIM — verifier engineering, portable-replay, priority revision 5.

Assignment nonce c0d742beb437484a0cb0c8971994843d (scope key 91a9a2afec282c926282). Base b5ea56e0a5ac4552166253b1fa4be0753bb38c30. Selected record unchanged.

Object. The three digest paths that research/selected626-linux-reconciliation removes before comparing the Linux artifact with the committed #626 assembly: template_sha256, input_sha256.owner_audit, and input_sha256.fresh_invoice. Producers are pinned at sprint base 66849e1475c930fd7732b1a0067ffee7e1e95f60 in research/complex-k492-owner-repair/code/{invoice_allcold,assemble,audit_allcold}.py.

Question. Is each omitted digest a gzip-container receipt, a decompressed payload hash, or a raw indented JSON file hash? A container mismatch alone must not be treated as a mathematical disagreement, and a payload mismatch must not be dismissed as gzip metadata.

Method. Read the pinned hash helpers and reproduce them on one fixture: same payload under two gzip containers, and one indented owner file whose only change is a nested container hash. No supplier replay and no new kappa.

Not the same work as the existing reconciliation (it already refuses to call the differences gzip metadata) or research/gzip-container-reproducibility (the general convention). This audit names what these three recorded differences can and cannot mean.

Expected finish 2026-10-15T19:30Z. Prepared by Riquelme Soares (@hevlyo) with substantial Cursor agent assistance.

[hevlyo]

DONE. Head af96f6e3eb00c8e3f60d310ba12fd9e4590fdc74. Package research/pr626-omitted-digest-audit. PR #2695

Classification of the three omitted paths:

• template_sha256 is a decompressed-payload hash. The recorded Linux/committed mismatch is a template-content disagreement, not a gzip-header artifact.
• input_sha256.owner_audit and input_sha256.fresh_invoice are indented JSON file hashes. A nested container can change the file while a paid_profile projection stays equal. Those two disagreements stay mixed without the omitted files.

Limits: producer blobs are pinned at 66849e1475c930fd7732b1a0067ffee7e1e95f60. This does not rerun make frontier626-verify, reconstruct OWNERS-AND-PROFILE.json or PREFIX-AND-INVOICE.json, explain the numerical template difference, or change the selected frontier. Selected baseline bindings were not rerun in this sparse checkout.

Prepared by Riquelme Soares (@hevlyo) with substantial Cursor agent assistance. Apache-2.0.