Atlas

Point

The repository contract chain changes atomically

A semantic change must keep prose, schemas, diagnostics, fixtures, processors, tests, assurance, self-hosting context, and release gates at one meaning.

Posture
asserted
Lifecycle
active

Atlas behavior is represented in several forms that can drift: normative prose, authored and output schemas, diagnostic registration, exact fixtures, validator code, independent-reader expectations, Check evaluation, assurance links, Meta-Atlas explanation, portal handoff language, and repository guardrails.

A semantic change is incomplete until every affected representation agrees at one reviewed revision. The canonical release command installs locked dependencies in a clean checkout and runs repository, validator, fixture, Meta-Atlas, Check, interoperability, and pilot gates. Any nonzero result blocks the release claim.

Repository gatesThe release gate checks synchronized prose, schemas, fixtures, processors, assurance, and self-hosting policy together.

contribution-policyContent · Resource unavailable in this portal · link unavailable
assurance-indexevidence · Resource unavailable in this portal · link unavailable
repository-checkerimplementation · Resource unavailable in this portal · link unavailable
release-runnerimplementation · Resource unavailable in this portal · link unavailable
release-policysupporting · Resource unavailable in this portal · link unavailable

Release governance binds every evidence surface to the exact reviewed revision and rejects stale gates or partial semantic updates.

A passing run no longer supports merge when the branch changes afterward. Review must cover the intended commit set, the clean-checkout release gate, and the same head used by continuous integration. A nonzero gate or unresolved assurance link blocks the release claim.

Contract changeEvery semantic representation must match the exact revision evaluated by the release gates.

Release stewardshipRejecting stale or partial evidence prevents a release from claiming a contract no single commit actually contains.

release-policyContent · Resource unavailable in this portal · link unavailable

Relations

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