Temporal state
Dates, intervals, approximate periods, and undated context use separate states.
Source-aware atlas methodology
Temporal and Interface Architecture
A timeline is not decoration. It changes which claims are visible and therefore must distinguish newly appearing records, active-period records, accumulated trails, and context without a defensible event date.
Core distinctions
The operational standard
Layer state
The active layer, theater, evidence class, and filter remain visible to the reader.
Selected record
Interaction resolves into a stable panel with source, time, place, confidence, and geometry status.
Progressive disclosure
Overview first, evidence on demand, and no explanatory clutter covering the map.
01
Current versus accumulated views
The atlas must state whether it shows only the selected period or preserves records accumulated from earlier periods.
02
Operational view versus evidence view
Fronts, arrows, zones, and density layers can support reading, but they cannot replace clickable event and source records.
03
Responsive research interfaces
Desktop, mobile, and PWA layouts preserve filters, legends, timelines, and selected records instead of hiding the methodological core on smaller screens.
Continue reading