How the checkup and guides are made

The checkup rules

Jolly Ledger Ready is deterministic: the same answers always produce the same findings. There is no AI model and no score, and this application processes your checkup answers in your browser and does not submit them anywhere. The hosting platform separately receives normal page requests and may run its own measurement; see Privacy. The current rule version is 2026.10-3, printed on every pack.

• No backup → preparation is incomplete; follow official guidance for your model. Never generic reset or migration advice.
• Not sure → a confirmation task, never treated as yes or no.
• Unchecked backup, or setup changed since checking → use the official backup-check process.
• Several devices on the same backup → flagged as a shared recovery dependency.
• One event could affect device and all backups → review independent recovery routes.
• Access depends on one phone or computer → plan an alternative.
• Passphrase with no plan beyond memory → an extra dependency to resolve first.
• Trusted person cannot find instructions → complete the family briefing offline.
• Multisig or smart-contract wallets → a bounded general report; single-signature guidance is suppressed and the limit is stated in every export.

Answers to follow-up questions are cleared automatically when an earlier answer makes them irrelevant, so the pack never reflects stale choices.

Limitations

The checkup only knows what you tell it. It cannot inspect devices, verify backups, detect compromise or guarantee recovery. Observing a risk is different from establishing that something went wrong.

How articles are sourced and dated

We prefer primary sources: vendor notices, official documentation and published standards. Reported facts are attributed; where an official statement could not be retrieved we say so and omit figures we could not confirm. Each article shows a publication date and a review date set by hand — pages are never automatically marked as “reviewed today”. Incident pages also show the date of the event itself.

Corrections

When we find an error or a vendor publishes a material update, we correct the page, update the review date and, where the change is substantive, describe it in the text. We do not promise automatic updates. See the incident hub for dated explainers.