Atlas

Point

HEAD carries one coherent contract

The supported repository state contains one internally aligned format, while a separate archive preserves discarded models without making them runtime obligations.

Posture
asserted
Lifecycle
active

The current branch is expected to explain and execute one meaning without requiring a reader to reconstruct compatibility from old proposals or retired applications. Normative documents, schemas, fixtures, processors, self-hosting records, and release gates must agree at HEAD.

The separate dated archive retains intermediate models and removed code. That archive does not require aliases, migration scaffolding, dormant implementations, or current prose for unsupported behavior. Reintroducing any such surface is a new maintenance decision that needs present evidence and explicit scope.

Contract changeOnly the aligned HEAD contract governs current changes; historical models stay outside runtime behavior.

Lifecycle and reversibilityThe separate archive preserves discarded choices without forcing compatibility or migration obligations into current lifecycle.

Decision history with current consequencesContentAtlas release recordhistorical

Relations

3 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.