Historical snapshot

Verifier-run digest comparisons are frozen.

These comparisons concern records created under the superseded activated checker status. They are retained for auditability and cannot establish the current target theorem.

Current theorem boundarynot established
mathematicalTheoremEstablished = false
publicTheoremEmissionAllowed = false
publicTheoremStatement = null
finalTheoremReady = false
projectSpecificAxiomsRemaining = true

What the digest comparison did

The old utility normalised record fields and compared SHA-256 digests for historical verdict data, activated-status coordinates, checker-script outputs, logs, and complete records. A digest match means the normalised historical bytes agree. It does not verify the truth of an assertion carried by those bytes.

Identity only

Hashes and comparison cells identify matching historical record content. They do not prove theorem correctness.

Superseded boundary

The records contain old activated fields. The authoritative current status has theorem establishment and emission set to false.

The old green badge has been removed

status = "historical-verifier-run-matrix-summary-frozen"
currentStatusBadge = false
badge.state = "historical"
badge.tone = "neutral"
badge.shortText = "historical snapshot"

Historical pair metrics remain in the payload so the snapshot can be audited, but they are not rendered as a current pass signal.

Frozen machine-readable records