Atlas

Point

The current format is the only contract

HEAD defines one format-1 behavior without compatibility code, parallel schemas, or fallback processing.

Posture
asserted
Lifecycle
active

The root declares "format": 1. The released specification, schemas, validator, fixtures, normalized output, Meta-Atlas, and release gates implement that contract only. Immutable specification and processor revisions identify the exact pre-1.0 contract. Earlier experiments remain in the separate dated archive and do not create aliases, migration behavior, parallel schemas, or fallback processing in the active repository.

One contract reduces ambiguity for authors and independent implementers. A future compatibility surface would become a current maintenance promise and therefore requires present evidence, explicit scope, and synchronized tests rather than an assumption that historical behavior must remain executable.

Syntax and discoveryRejecting old paths and aliases keeps discovery and parsing on a single current grammar.

Conformance evidenceOne HEAD contract gives implementations one observable behavior to reproduce rather than a compatibility matrix.

Atlas release recordContentAtlas format contractsupporting

Relations

2 connections

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.