Stable local identity
Spot UUIDs do not automatically change when a vendor renames, moves, merges or deletes a source record.
Places evolve. Evidence should too.
See where each landmark claim came from, when its source was checked and when it should be reviewed again. Explore how a future source change would be handled without silently changing an Orbit, Spot or visitor's saved memory.
Explore quality checks →i
Maintenance dates are not verification.
They are illustrative review intervals, not evidence that a business is closed, unsafe or incorrectly mapped. Provider update timestamps are not ground visits. No actual user correction has been accepted or approved.
CURATED SPOTS–Reviewed name references
REFRESH REMINDERS–Attribute reviews due
MISSING EVIDENCE–Places with unverified claims
FIELD VERIFIED–Independent checks
SOURCE CLAIMS · NOT OVERALL TRUST SCORES
Every attribute has its own clock
Pick a landmark to inspect where the data came from and what still needs attention.
Loading source ledger...
PROVIDER CHANGE SANDBOX
What if the source changes tomorrow?
This simulator uses documented Overture changelog event types. Every scenario is hypothetical. It does not fetch an actual changelog, verify any venue or change the current data.
Choose an event to see how an independent local Spot identity should be protected.
Keep history. Question changes. Never guess.
Per-claim freshness
Different evidence needs different check intervals. A name reference is not opening-hours evidence.
Review before publication
Conflicts, missing sources and changing geometry require independent evaluation before alerts, directions or public corrections.