CASTLE ATLAS

Offline guide

Offline Castle Research Workflow

Prepare source ledgers, selected media attribution, and bounded map context before connectivity drops.

Castle Atlas’s local release build demonstrates offline discovery and per-castle packages, but it does not promise a complete offline roads-and-terrain basemap.

Save the evidence, not just the pin

An offline research packet should retain identity, selected historical claims, source links, and complete media attribution.

  • Canonical URLs stored.
  • License details stored.
  • Retrieval date visible.

Understand the map boundary

The verified per-castle overlay is a bounded discovery layer. Full terrain, roads, water, and live routing are separate systems.

  • Do not call an overlay a basemap.
  • Keep attribution available offline.
  • State what was omitted.

Plan for expiry and corruption

Offline packages should expose verification, replacement, low-storage, and stale-data states instead of silently presenting old content as current.

  • Check package integrity.
  • Reverify visitor facts online.
  • Remove corrupted packages safely.

Sources and review scope

Reviewed September 1, 2026. The examples below support identity and dataset method. They do not by themselves support current visitor information or a complete historical profile.