Official or primary
Law, authority, institution, operator or named first-hand source.
PROOF 01 · GUIDE
Verification is a practice, not a badge.
This protocol defines what GO URLA must inspect, record, date and correct before “verified” can mean more than a marketing word.
SCOPE BOUNDARY
What this version proves.
Version 1.0 proves that GO URLA has a published method and a dated register of its own twelve public entry pages. It does not certify every business, validate every third-party claim, promise availability or replace professional safety and legal checks.
EVIDENCE CLASSES
Name where every factual claim comes from.
Direct verification
A dated call, message, field observation or transaction test.
Corroborated secondary
Two credible independent sources with dates and attribution.
Editorial context
Interpretation clearly separated from factual operating claims.
MINIMUM PUBLIC RECORD
Ten fields before a verification claim.
- 01
Canonical name
- 02
Category and geographic scope
- 03
Claim being verified
- 04
Evidence class and source
- 05
Source or observation date
- 06
Checked-by role
- 07
Seasonal or access limits
- 08
Commercial relationship, if any
- 09
Last checked and next review target
- 10
Correction or retirement state
RISK-BASED REVIEW
The faster a fact changes, the sooner it expires.
These are review targets, not guarantees that a third party remains unchanged between checks.
01
Events and temporary openings
7 DAYS / RETIRE AFTER DATE02
Operating status, stays and experiences
30 DAYS03
Hours, access and booking path
30 DAYS IN SEASON04
People and operator profiles
12 MONTHS OR MATERIAL CHANGE05
Heritage and durable context
24 MONTHS OR NEW PRIMARY SOURCEEDITORIAL INDEPENDENCE
Trust cannot be a package upgrade.
No pay-to-rank
Payment cannot determine inclusion, status or editorial order.
Disclose material relationships
Hosted visits, sponsorship and ownership conflicts must be visible.
Separate sales and correction decisions
A commercial partner cannot veto a factual correction.
Retire unverifiable claims
Silence is not confirmation; stale high-risk claims leave the live guide.
CORRECTION WORKFLOW
Receive. Triage. Verify. Correct. Log.
Target: acknowledge a material report within two working days and resolve or publish its review state within ten. These targets begin only when an accountable correction inbox and owner are live.
- 01RECEIVED
- 02TRIAGED
- 03IN REVIEW
- 04CORRECTED / RETIRED
- 05PUBLIC LOG
PAGE-LEVEL REGISTER · V0
Twelve checked entry points.
This register covers GO URLA pages, not the individual venues mentioned inside them.
Open machine-readable JSON ↗NEXT GUIDE GATE
From page checks to claim records.
Apply the ten-field record to the first 25 high-value place and experience claims, then publish a visible correction log.
Return to the Guide dossier ↗