Rust service layer
Public APIs, live snapshots, search, summaries, contact delivery, and thematic records are served through the Rust application layer.
Computational atlas architecture
Historical GIS, live public signals, 3D scenes, source records, and formal research are published through one coherent infrastructure. Rust carries the service layer; cartographic interfaces preserve the identity, time, provenance, and precision of every record.
Operating model
The system does not flatten an archive, a live alert, a historical boundary, and an analytical surface into the same claim. Each enters the atlas through its own contract and remains readable as a distinct evidence class.
Public APIs, live snapshots, search, summaries, contact delivery, and thematic records are served through the Rust application layer.
Exact, locality, regional, centroid, and proxy geometries remain distinct across sensitive historical and political datasets.
Period filters, dated records, historical boundaries, routes, and event layers support comparative reading across time.
Controlled public feeds are normalized into compact current snapshots without retaining an unnecessary long-term live backlog.
Heritage and Earth-system scenes reuse source-aware atlas layers while preserving their thematic legends and record identities.
Canonical pages, structured data, sitemaps, durable record routes, and source links connect maps with research discovery.
Publication chain
Connected output
Continue through the system