Atlas

Point

Consumers must preserve provenance

Tools must retain Maps, Areas, anchor and context records, state, relations, material roles, source paths, and Check boundaries when presenting Atlas data.

Posture
asserted
Lifecycle
active

A consumer can reorganize presentation, search, filtering, or navigation, but it cannot flatten away the distinctions that give Atlas meaning. One Point remains one identity; the primary Map and each source record remain visible; local Areas stay Map-qualified; and Content, References, relations, lifecycle, and Check policy keep their roles.

A context record must not appear as another Point, and a document must not inherit one linked Point’s state. Any generated view or integration that cannot explain where a claim came from is not preserving the portable model, even if it accepts the source syntax.

PortabilityPortable exchange fails if consumers flatten away the provenance needed to reconstruct the same Point and Map model.

IntegrationIntegrations must expose source records and semantic roles so users can audit how a presented result was assembled.

Atlas conformance contractContent

A publication build must preserve selected-record provenance and derive every output surface from the profile boundary rather than the full source Atlas.

The profile selects exact Point records rather than a whole identity automatically, so generated pages and indexes need contribution-aware provenance. The output must explain which source record supports each edge and must not derive overlap, incoming relations, counts, or search terms from omitted context.

These are requirements for the hardened publication build and portal, not extra profile fields. The profile supplies the complete selected source boundary; the implementation must prove that every output channel stays within it.

Selection and closureA publisher must choose records explicitly and rebuild derived indexes from that selected provenance.

Non-disclosureRecomputing from selected records prevents omitted source-Atlas context from leaking through indexes or backlinks.

Reader experienceVisible anchor, context, Map, and source paths let readers understand where assembled claims came from.

Atlas publication profile contractContent

Relations

4 connections

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.