Atlas

Resource

Decision history with current consequences

Earlier choices retained only where their rejection explains a current Atlas constraint.

Resource decision-history

The current release followed a first-principles reset. Earlier work mixed semantic modeling, spatial navigation, publication behavior, deployment, and compatibility concerns before the core identity model had settled. The reset removed those surfaces from the current contract instead of preserving them as dormant alternatives.

Three consequences remain active. First, one Point now keeps one Atlas-wide identity through an anchor and same-named Map-local context records; the primary Map establishes provenance without exclusive ownership. Second, publication eligibility is an exact profile allowlist, while compilation and non-disclosure remain portal-build responsibilities. Third, the portal direction starts with direct documents and a stable reader shell rather than making a Map workspace the required entry point.

Checks also remain part of the write system. Removing them would leave project-specific authoring policy outside the portable Atlas boundary, while treating them as mapped context would confuse policy with meaning. Their current contract therefore keeps them separate, bounded, and fail-closed.

The separate dated archive preserves discarded implementations and intermediate choices. The active repository does not carry their runtime behavior, aliases, migration paths, branches, or tags.

Where this Resource is used

6 uses

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.