Corrections

Correction policy

Locked outputs are never silently edited. Every published score is locked at publication and carries a SHA-256 integrity hash recorded in a public log. A corrected score is issued as a new, separately dated version. The original file remains unaltered, and its original hash continues to verify against its original content — including its error. Corrections are additive records, not retroactive edits.

A correction and a rescore are different things. A rescore reflects new evidence about the subject: the product changed, a vulnerability was disclosed, a manufacturer shipped something new. A correction reflects an error in Linkmerica's own work: a research gap, a factual mistake, a misstatement. Both are dated and published. They are not the same event and are not described as though they were.

A correction is issued when a factual error is identified in a published output, or when the evidence base underlying a score is found to have been incomplete or inaccurate at the time of scoring.

Every correction states plainly whether any score was affected. Where the answer is no, that is stated directly rather than implied.

Synthesis brief withdrawn and rebuilt before announcement

Affected output: Research brief, "Five Ways an Agentic Protocol Fails Custody."

What was wrong: The first published version contained factual errors introduced during drafting. All three rated protocols were given incorrect formal names. Both Linkmerica framework acronyms were expanded incorrectly. A statement describing a rated party's response to published research was included without any source. A specification publication date was stated without a source. Two of Linkmerica's own prior rescore dates were stated incorrectly, contradicting the locked score files. One transaction-volume figure was overstated, and two cumulative figures were described as monthly rates.

What changed: The brief was withdrawn and rebuilt the same day from the locked score files, with every factual claim constrained to verified sources. It was republished before any announcement was posted. An editorial verification gate was built the same day and now runs against every brief before publication, checking score claims and dates against locked files and flagging any statement attributed to a named third party.

Was any score affected? No. All five agentic protocol scores referenced in the brief were correct, locked, and hashed throughout. The error was confined to the brief's prose.

Trezor Quantum Resistance Readiness — research gap in original score

Affected output: Trezor Quantum Resistance Readiness score, published 2026-06-28.

What was wrong: The score's rationale stated that no public quantum-readiness statement from the manufacturer had been identified. This was incorrect at the time of scoring. Trezor had published quantum-readiness technical content in March 2026, over three months before the scoring date, and it was publicly accessible throughout.

What changed: A dated correction note was published, and a new score version was issued on 2026-07-24 incorporating the manufacturer's disclosures. That version also documents a device-generation change in what the Trezor entry assesses. The original 2026-06-28 file remains locked and unaltered with its original integrity hash.

Was any score affected? Yes. The Quantum Resistance Readiness score moved from 7.8 (HIGH) to 4.4 (MODERATE). Both versions remain in the public record. View the current score.