Current capability boundary

Working with Atlas

Atlas 0.8.0 supplies a portable model and operating guide for people and software agents. Point identity separates independently standing claims from supporting prose. Maps and Areas organize context through explained connections. Records use JSON front matter and Markdown bodies.

The fictional starter demonstrates two Point identities, a local context record, and scoped implementation evidence. It provides an entrypoint for authoring and reading a small Atlas.

Available tools

The reference validator checks structure and resolved relationships. Invalid or incomplete validation withholds normalized output. Exact Point inspection assembles one local identity with its records, provenance, and directly used Resource metadata.

Atlas Portal validates a complete Atlas, applies one explicit publication profile, and generates a static website. The reader provides Map and Area navigation, assembled Points, document reading, relations, and search. Authored summaries introduce each destination. Help explains the terms and navigation. Copyright and license notices come from the site's configuration.

The portal reads selected local documents within allowed roots and preserves external documents as links. Local Checks remain authoring policy and do not become reader pages. Search indexes Resource metadata and a bounded excerpt of each inline document; a missing search match does not establish that the full document lacks the term.

The released repository includes the specification, validator, portal, and copyable examples. Cloudflare Workers Static Assets is an optional deployment path. The source model and operating guide also work without a hosted portal.

Atlas’s own project portal is available at atlas.neutral.dev. Its first deployment was verified on 2026-09-05 through live HTTP checks and browser review.

Current limits

Authoring applications, dedicated agent integrations, migration tools, hosted validator APIs, and package-registry distribution remain outside the current release.

Structural validation, independent-reader agreement, and recorded browser checks establish specific technical behavior. They do not establish universal accessibility, comparative reader benefit, reliable handoffs, or lower maintenance cost. Bounded development exercises inform the design; the effect on ordinary project work still requires evidence.

The publication profile selects whole source units. It does not grant access, authenticate readers, or authorize redistribution. The current portal implements a selected static reader; it does not claim a separate publication-build conformance class, automatic production promotion, or a general attachment pipeline.