The Copy That Didn't Know It Was Old

Description and use

Integrity checks on template copies prevent stale copies from publishing by byte‑by‑byte comparison of guard functions.

Copies of a publishing template drift over time, causing stale copies to publish with outdated rules without triggering existing guards.

The integrity check prevented stale copies from publishing, ensuring that only copies matching the current template’s guards are allowed to run.

1. Extract guard functions (verification and receipt writer) from the copy using definition anchors.
2. Retrieve the same functions from the live template via anchors.
3. Compare the byte streams of each guard pair; if any differ, abort with exit code 2 and log "COPIA_DIVERGENTE".
4. If all guards match, proceed with network calls and publishing.
5. Include an identity line in the publish receipt for auditability.

Any divergence, including a missing function, aborts with exit 2 and a COPIA_DIVERGENTE line, before a single byte leaves the machine.

A faithful, byte‑identical copy: passes.