A community link should be treated as an entry to verify, not as the whole task. The reader needs to identify the page source, compare it with the device screen, and decide what information belongs in the local record before moving on.
Identify the page source first
Start with the page title, route, and task shown after the link opens. If the page claims to guide a Ledger setup or account view, compare the expected path with the similar entry and download page review.
Compare the page task with the device screen
The device screen should explain what the page is asking the reader to confirm. If the task involves account viewing or a device prompt, the daily Ledger use flow helps place the prompt in a normal sequence.
Set a narrow information boundary
The local note can include the link source, page title, time, and device state. It should not include recovery phrase words, PINs, or private setup material. For support-style contact records, see the computer and phone entry boundary guide.
Return to a known entry if the route is unclear
If the page task and device screen cannot be matched, stop using that entry and reopen the expected path from a known page. The next note should identify the checked route and the page task, not the sensitive record.
