Atlas

Map

Format and Interoperability

The portable file contract and deterministic behavior on which independent Atlas processors must agree.

Areas

5 Areas · 9 Points
About this Map

This Map contains behavior that must survive movement between repositories and implementations. It covers physical discovery, safe parsing, resolved identity, deterministic normalization, validation states, and the evidence required before an implementation can claim conformance.

Repository-specific policy does not become part of this Map merely because code enforces it. A claim belongs here only when independent processors need the same observable interpretation or when an extension boundary protects that agreement.

Shared selected Points

Original Atlas material: CC0 1.0 Universal or 0BSD. Referenced material retains its own terms.

Reading this Atlas

Atlas connects project documents to the claims, decisions, and perspectives they inform. It helps readers find relevant material and understand why it matters.

Explore the portal

  1. Start with a Map, then narrow the view through its Areas.
  2. Search for a phrase, title, or Point identity. Filter results by type.
  3. Open a Point for its explanations, related Points, and sources. Follow source links for the underlying material.

Quick reference

Map
A durable project perspective organized around one central question.
Area
A concern within a Map. Areas can overlap; memberships explain why a Point belongs.
Point
One claim, decision, constraint, question, or other coherent item with its own identity.
Context
An explanation of how the same Point matters in another Map.
Relation
A directed link between Points with an explanation, such as support, dependency, or replacement.
Resource
An addressable document or other material.
Content
The primary material for an Atlas item.
Reference
Material linked as evidence, background, implementation, history, or an example.

Missing links do not mean that no relationship exists.

Read the state

Posture describes the author's stance: asserted means presented as applicable or believed; open, unresolved; proposed, a candidate; intended, a desired or selected future state.

Lifecycle describes standing: active means current context; historical, retained prior context; superseded, replaced by another Point; withdrawn, retracted.

Asserted does not mean verified. Intended does not mean implemented. Source links provide material to assess these claims.