How we work
Useful, sourced and honest about limits
Every page begins with a reader need, not a word-count target or an opportunity to manufacture another URL.
Qualification
A proposed page must answer a distinct question, support a real decision or provide a useful orientation that cannot be handled adequately inside an existing page. Trivial facts belong inside entity hubs, not on thin standalone pages.
Evidence
Primary official and technical sources lead the evidence hierarchy. Secondary sources are used for context or independent interpretation. Consequential rules, fares, legal guidance and safety information require an identifiable authority and a current verification date.
Short answers and depth
Where a direct answer helps, it appears near the page title and names the subject explicitly. The rest of the page explains the mechanism, evidence, exceptions and limitations. Length follows the complexity of the question.
Visual integrity
Illustrative diagrams are labelled as illustrative and not to scale. Simplified maps are not presented as navigation maps. Charts identify their dataset, period, unit and method.
Human publication gate
Automation may collect sources, structure research and run quality checks. It does not replace human approval. A page cannot be released as approved or published until its sources, claims, schema, links and presentation pass the recorded publication workflow.
Corrections and change
Material errors are corrected visibly. High-freshness pages carry scheduled review dates, and stale consequential guidance is withdrawn or clearly marked rather than left to decay.
