Atlas Portal implements profile-driven generation

Atlas Portal validates a complete Atlas with the resolved validator profile, requires one publication-profile id and an explicit Portal configuration, projects selected Maps, Point records, and Resources, and emits static Atlas, Map, Area, Point, Resource, and search routes. Check definitions remain outside the reader. Full Atlas validation still covers their structure and references. The explorer combines a compact navigation rail with a white reading pane. Selected Point contributions, explained Area memberships, sources, and relations remain with the reading destination. Narrow screens open navigation in one drawer.

The Portal configuration owns the reader name and optional copyright and license footer lines. These builder-supplied strings have no defaults. Footer text does not alter Resource licenses or infer terms from source metadata.

The reusable package contains no Meta-Atlas paths or notes. The public-tools workflow projects it with the reference validator into an isolated tools/ workspace, rewrites development-only paths, and supplies public tests against the published specification fixtures. The separate neutral-dev-meta-atlas application supplies concrete local inputs, builds the selected view, runs it locally through Wrangler, and deploys it through Workers Static Assets. Its dry-run command validates the package without uploading it. Compiler tests also exercise the complete publication-profile fixture and static Astro generation.

The explorer verification records specific responsive, keyboard, search-continuation, and context-jump observations. Its source hashes and named scenarios limit those claims. The maintenance course separately follows source changes through their Atlas assertions and a fresh reader handoff.

This establishes reusable source distribution, static generation, and a native deployment path, not a complete publication guarantee or product result. The implementation still lacks a public stable corpus contract, capability manifest, complete publication audit, deterministic artifact promotion, attachment handling, automated browser and accessibility coverage, package-registry distribution, and reader-outcome evidence. The hosted Meta-Atlas has its own deployment observation.

Strict TypeScript checking covers the compiler, process runners, Astro components, and browser controls. The private corpus cache is validated at its read boundary. Each command uses its own temporary cache and removes it after the Astro process exits. These controls and regression tests support bounded implementation claims; they do not establish complete publication hardening.