Point
Publication selection is fail-closed
Only units named by an explicitly selected publication profile are eligible, and no semantic or containment edge expands that source allowlist.
- Posture
- asserted
- Lifecycle
- active
The publication profile is an explicit source allowlist. It names the root Atlas record, exact Maps, exact Point records by Point-and-Map pair, registered Resources, and Checks. An absent profile selects nothing, and selecting one unit does not pull in containers, other contributions, relation targets, or referenced material.
Processing resolves this source-selection decision. Publication tooling must separately enforce the selected boundary across generated surfaces. A valid profile does not establish a publication audit or serving guarantee. Implementation evidence belongs in the current capability boundary rather than in a volatile description of this normative edge.
Current publication boundaryThe profile defines source eligibility; build and serving guarantees require separate contracts and evidence.
Selection and closureAn absent profile or omitted selector leaves a source unit outside the publication allowlist.
Stewardship keeps source eligibility explicit in reviewed profiles and treats publication-build guarantees as a separate release boundary.
Publication eligibility enters only through a validated profile whose selectors resolve against the exact Atlas revision. Compiler options, portal routes, or deployment configuration cannot silently widen that authored decision.
The current release proves profile syntax, resolution, normalization, and independent processor agreement. A later publication-build release must supply its own tests for leak prevention across documents, navigation, indexes, search, machine outputs, diagnostics, and caches.
Security and authorityOnly a named profile can establish source eligibility; build and serving systems must separately prove non-disclosure.
Contract changeChanging profile meaning is a semantic contract change, while implementing a compiler is separate product work.
Release stewardshipThe release can include profile validation without claiming a publication build, deployment, or portal class.
Included processors validate explicit publication profiles, and Atlas Portal projects one selection before deriving static reader data.
Structural discovery accepts direct profile files at the root policy location. Resolved validation verifies every selected Map, Point record, Resource, and Check, then emits a deterministic normalized selection. Invalid input withholds the entire normalized model.
Atlas Portal continues from that result. It reads selected local Resources only within caller-supplied roots, filters navigation and indexes to selected units, and builds static pages. It does not yet implement a capability manifest, complete publication audit, atomic output promotion, serving policy, or deployment guarantees.
Repository gatesRepository, schema, fixture, validator, and interoperability gates keep profile behavior synchronized.
Portal implementationAtlas Portal derives routes, counts, search data, and readable Resources from one explicit selected source set.