How We Verify

Evidence first. Confidence second.

The system is designed to downgrade uncertain information instead of leaving an old green tick on a changing travel rule.

1. Register the authority

Record the official source, the claims that depend on it and the relevant part of the page.

2. Monitor meaningful content

Remove menus, scripts and irrelevant page noise before comparing versions.

3. Detect material changes

Cosmetic changes are ignored; regulatory, deadline, fee and process changes trigger re-verification.

4. Reverify or degrade

If evidence is clear, update. If evidence is ambiguous, suppress the definitive claim and point to the authority.

5. Keep history

Claim versions, source checks and verification events form an auditable trail.

Supersession

Newer official rules can override older official pages

Government sites sometimes leave an old PDF or announcement online after a rule changes. The engine does not treat every official page as equally current forever.

Target-scoped

A source can be superseded for one specific claim without being discarded for unrelated information it may still contain.

Effective-dated

The replacement only takes effect from the authority’s stated change date. Historical versions remain available for audit instead of being silently deleted.

Fail-safe

Once evidence is superseded, it cannot keep a current claim VERIFIED. If the newer evidence cannot be confirmed, the claim degrades rather than falling back to the old rule.

Active-source conflicts

Two current official sources can genuinely disagree

Supersession handles an old rule that has been replaced. A different problem occurs when two current authoritative sources both remain active but express incompatible values.

Canonical positions

The engine can record the specific value each authoritative source currently expresses for a claim field, such as a submission window, validity period or fee.

Current evidence only

Only verified, unexpired PRIMARY or SUPPORTING sources count. Historical, stale, reporting/community and explicitly superseded evidence cannot create a regulatory conflict.

REVIEW REQUIRED

If current authoritative sources disagree, the public claim is not allowed to remain VERIFIED. The engine shows uncertainty and directs travellers to the authorities until the conflict is resolved.

Traveller intelligence

Experience is useful, but it is not law

Practical travel reality can come from official operators, reputable reporting or traveller/community datasets. The engine keeps those signals separate from legal eligibility and shows their provenance publicly.

Authority tier stays visible

PRIMARY and SUPPORTING sources can establish official facts. PRACTICAL sources describe operations. REPORTING and COMMUNITY sources remain context or sentiment rather than government rules.

No fake percentages

A recommendation percentage or strong sentiment label requires a transparent methodology, including the dataset, sample size and time range. Otherwise the engine falls back to Limited evidence.

Nationality-specific friction

Documented friction can be scoped to a passport or traveller group without turning it into a false claim that the destination legally refuses that nationality.

Data provenance

Free/open data where it is safe to use

Operational datasets are kept separate from regulatory claims so one provider can be replaced without rewriting the product.

Worldwide airports

OurAirports data is imported into our own database and refreshed on a schedule. Search continues from local data even when the upstream site is temporarily unavailable.

Aircraft positions

Open ADS-B data can power recent aircraft position where coverage exists. Position age is always visible and anything older than 10 minutes is treated only as a last-known position.

Conflict & disaster layers

Official aviation advisories and disaster feeds are cached locally. Nearby hazards are context only; the site never invents the reason an aircraft changed route.