Deliberate handoff
For the button-to-handoff sequence and the behaviour expected from a current-link page.
Open the access guide →Torzon Link Guide
Follow the current-link journey from discovery and publication context through route changes and a deliberate market handoff.
Read the hostname, title and page purpose. A Torzon link guide should explain the handoff and should not imitate a market login.
Read the publication date and whether the route is described as current or superseded. A copied page without change context is weak discovery evidence.
The market transition begins only after a POST button is submitted. Search referrals, timers and crawler identity do not trigger it.
| Public Torzon link guide | Destination interface |
|---|---|
| Route purpose and navigation controls | Current account and market interface |
| Discovery source, freshness and change context | Login, recovery and authenticated account actions |
| Independent editorial limits | Current listings, vendors and transaction functions |
| No passwords, payments or private keys | Sensitive actions only after the user verifies the destination |
For the button-to-handoff sequence and the behaviour expected from a current-link page.
Open the access guide →For source comparison, full-address checks and common phishing warning signs.
Open the verification guide →For concise answers about buttons, automatic movement and editorial scope.
Open the link FAQ →For an explanation of normal requests, logs, client-side code and the transition boundary.
Open the privacy page →A clear route is not a promise about everything beyond it.
This guide can describe discovery, publication context, route changes and button behaviour. It cannot authenticate a user, confirm a vendor, inspect an account, guarantee availability or establish the outcome of a market action.
Re-check the visible destination before entering private information. If a public directory asks for credentials, recovery material or payment, leave it.