How guides are prepared
Each guide starts with a defined reader question, a small set of item-identity terms, and named examples. The draft separates stable catalog concepts from claims that would require a current venue check. Editors then add a comparison, a repeatable workflow, common failure cases, an evidence boundary, and topic-relevant further reading.
English and Russian guides use parallel review criteria, but their prose is written for each language rather than treated as a machine-readable live market feed. The visible publication and modification dates describe the article record.
Evidence boundaries
A saved catalog or provider observation can support a dated statement about the covered row and field. It cannot, by itself, prove a live executable listing, completed sale, total supply, private transaction, universal eligibility, or future value. Missing coverage remains unknown; it is not converted to zero.
Guides do not make an outbound market request while a page is rendered. Readers must independently verify current item identity, availability, fees, account restrictions, settlement, and final terms in the trusted interface before acting.
How sources are used
Source lists are chosen for the question being answered. They may point to first-party Dota 2 news, Workshop documentation, Steam Support, or a user-opened market search when those pages help verify release context, item submission rules, account safety, or current venue conditions. A link is a place to check, not an endorsement or certification.
Dota Ledger uses third-party and locally committed data only. It does not require a Valve or Steam API key, and a citation never turns a dated observation into a current quote.
Review and corrections
Editors review identity fields, dates, wording, internal links, and unsupported market implications before publication. When a guide is materially corrected, its source content and visible modification date are updated together. Unresolved conflicts stay labelled as unknown instead of being filled with an estimate.
The quickest way to audit a conclusion is to keep the exact item name, field label, observation date, and source beside it. Return to the guide library to inspect the method and sources attached to a specific topic.