Atlas

Point

Tools are source-distributed without a service promise

The public repository receives runnable Portal and validator source, while registry packages, hosted validator APIs, update channels, and support promises remain absent.

Posture
asserted
Lifecycle
active

The public repository receives Atlas Portal and the reference validator as private source packages in one isolated tools/ workspace. The projection includes exact dependencies, a lockfile, public commands, tests, static generation, and optional Workers Static Assets deployment commands. The independent reader and concrete deployment application remain development-repository packages.

The project’s own hosted Meta-Atlas is a separate deployment of this software. Source distribution does not create an npm package, hosted validator, network API, automatic update channel, compatibility commitment, or support surface. Any broader distribution decision still needs installation and upgrade contracts, security response, support duration, provenance, licensing, and evidence that the chosen channel helps adopters rather than centralizing the portable format around one implementation.

DistributionThe source projection supplies installable files without registry delivery, automatic updates, or a service support commitment.

release-policyContent · Resource unavailable in this portal · link unavailable
Current capability boundaryevidence
public-tools-syncimplementation · Resource unavailable in this portal · link unavailable
workspace-manifestimplementation · Resource unavailable in this portal · link unavailable

Relations

1 connections
  • supports
    Evidence bounds maturity claims

    Source availability establishes a distribution route without establishing registry packages or maintained service commitments.

Original Atlas material: CC0 1.0 Universal or 0BSD. Referenced material retains its own terms.

Reading this Atlas

Atlas connects project documents to the claims, decisions, and perspectives they inform. It helps readers find relevant material and understand why it matters.

Explore the portal

  1. Start with a Map, then narrow the view through its Areas.
  2. Search for a phrase, title, or Point identity. Filter results by type.
  3. Open a Point for its explanations, related Points, and sources. Follow source links for the underlying material.

Quick reference

Map
A durable project perspective organized around one central question.
Area
A concern within a Map. Areas can overlap; memberships explain why a Point belongs.
Point
One claim, decision, constraint, question, or other coherent item with its own identity.
Context
An explanation of how the same Point matters in another Map.
Relation
A directed link between Points with an explanation, such as support, dependency, or replacement.
Resource
An addressable document or other material.
Content
The primary material for an Atlas item.
Reference
Material linked as evidence, background, implementation, history, or an example.

Missing links do not mean that no relationship exists.

Read the state

Posture describes the author's stance: asserted means presented as applicable or believed; open, unresolved; proposed, a candidate; intended, a desired or selected future state.

Lifecycle describes standing: active means current context; historical, retained prior context; superseded, replaced by another Point; withdrawn, retracted.

Asserted does not mean verified. Intended does not mean implemented. Source links provide material to assess these claims.