Point
An Atlas is one portable context boundary
One root establishes the namespace in which Maps, Point identities, Resources, and Checks resolve.
- Posture
- asserted
- Lifecycle
- active
An Atlas begins at one atlas.md root and defines the namespace in which Map identifiers, Resource identifiers, Point identities, and root Checks are interpreted. A descendant atlas.md begins another Atlas, so parent discovery stops before entering that nested boundary.
This scope is semantic as well as physical. A Reference can identify material outside the boundary, but that target does not become structural Atlas content and the standard validator does not read it. Portability depends on being able to move the bounded document set without inheriting hidden repository state or ambient authority.
Boundary and namespaceThe root sets the discovery stop and namespace for every identifier resolved as part of one Atlas.