Map
Publication and Access
Explicit publication selection, publication-build responsibility, and the intended reader experience for selected Atlas context.
Areas
5 Areas · 10 PointsCurrent publication boundary
The current profile, Portal compiler, static deployment, and absent conformance boundaries.
Selection and closure
Exact source-record and registered-document selection without implicit expansion.
Non-disclosure
Build and serving guarantees that keep unselected material out of every generated channel.
Reader experience
Direct-document access, stable navigation, provenance, and continuation through mapped context.
Publication evidence
Fixtures, accessibility, performance, and human outcomes required before maturity claims.
About this Map
This Map separates the current source-selection contract from the publication systems that consume it. Profiles consolidate exact eligible records and Resources; they do not contain compiler, rendering, indexing, serving, or deployment policy.
Atlas Portal projects selected records and Resources into a static reader. The concrete Meta-Atlas application runs that output locally through Wrangler and serves the public project portal through Workers Static Assets. Its first deployment has separate live HTTP and browser evidence. That observation does not establish release-grade non-disclosure auditing, artifact promotion, or portal conformance guarantees. Core context never implies publication eligibility, and a valid profile never proves that a downstream system enforced its boundary.