Map
Governance and Stewardship
The change discipline, evidence boundaries, security posture, and reversibility needed to keep Atlas coherent.
Areas
5 Areas · 11 PointsContract change
Synchronized updates across prose, schemas, diagnostics, fixtures, implementations, and evidence.
Claim discipline
Maturity and product claims constrained to the evidence that actually exists.
Lifecycle and reversibility
Explicit replacement, withdrawal, archival history, and the cost of preserving weak choices.
Security and authority
Untrusted-input processing and denial of inferred file, network, publication, or execution permission.
Release stewardship
Clean-checkout evidence, included scope, licensing, merge discipline, and current support.
About this Map
This Map receives choices that affect how Atlas can change without splitting into incompatible meanings or overstating maturity. It connects contract synchronization, release evidence, lifecycle, security, licensing, and the deliberate removal of unsupported surfaces.
Governance is not a reason to preserve complexity. The active repository keeps one supported contract at HEAD, while a separate dated archive retains discarded work. New compatibility behavior, services, or conformance classes require current evidence and an explicit maintenance commitment.