# Map-as-Database Architecture

Map-as-database is the architectural pattern underneath the Pacific Muse Atlas. It treats geographic places — routes, waypoints, purveyors, Artifacts — as primary records in a structured database, and the map as a visualization of that database rather than the database itself.

## The Premise

Most travel content treats the map as the source of truth. A pin on a map is the unit; the data behind it is whatever can be displayed in a popup. This works for casual discovery but fails for editorial work: the data is unstructured, the relationships between pins are implicit, and the records are not independently queryable.

Map-as-database inverts the relationship. The database is the canonical record; the map is one of several views over it.

## How It Operates

**Records, not pins.** A purveyor in the Atlas is a structured record with an inspection history, a partnership status, a versioning trail, and explicit relationships to routes and Artifacts. A pin on a member-facing map is a rendered view of that record at a point in time, not the record itself.

**Schema-versioned.** The database schema for nodes, routes, and Artifacts is itself versioned. When a new field is added — an accessibility flag, a seasonal-window range, a vehicle-suitability marker — the change is recorded against the schema version, and prior records are migrated explicitly rather than retrofitted silently.

**Multi-view.** The same database supports the public map, the inspector's working tools, member exports (GPX files, PDF folios), and the agent-facing surface that allows AI agents to query the Atlas as a structured source. Each view is generated; none is canonical.

**Audit-friendly.** Because records are structured and versioned, the Atlas can answer questions humans care about. When was this node last inspected? Has its partnership status changed since the last inspection? What was the schema when it was first canonized? These questions are answerable in seconds, not days.

## Why It Exists

The Atlas is meant to outlast the founder, the original schema, and the current technical stack. Map-as-database is the architecture that makes that possible. It treats geography as data — typed, versioned, queryable — and treats the map as one of several ways to look at that data, none of which is privileged over the underlying record.

It is the structural commitment that the Atlas is a verification record first, and a beautiful map second.

## Related

- [Pacific Muse Inspection Doctrine](https://justinhammack.com/methodology/inspection-doctrine.md) — the standard the Atlas records.
- [Pacific Muse](https://pacificmuse.com) — the operating property where the Atlas lives.