Atlas

Point

The independent reader proves consumer agreement

A separately implemented read-only processor produces the same normalized model for valid fixtures and the Meta-Atlas without importing reference-validator code.

Posture
asserted
Lifecycle
active

The repository contains a second processor built from the normative schemas and valid examples without importing or naming the reference validator implementation. Interoperability tests compare its normalized model byte-for-structure with reference output for every valid fixture and this self-hosting Atlas.

That agreement is evidence for read-only consumer interoperability and preservation of Point provenance. It is not evidence that the independent reader conforms as a validator, because it does not reproduce every required invalid-fixture outcome and standard diagnostic.

Conformance evidenceAgreement from a separately implemented reader is evidence that the contract is reproducible outside reference code.

Normalized modelExact comparison tests provenance, ordering, Area explanations, relation notes, and indexes as consumer-visible output.

Implementation independence is protected by a source-level import boundary and exact model comparison in the release gate.

Repository checks reject reference-validator imports or names inside the independent reader, and tests execute both implementations against the same sources. Exact deep comparison catches missing extensions, changed ordering, flattened records, and divergent derived indexes.

Independent processingA no-import source boundary separates the second reader's implementation from the reference validator.

Repository gatesExact release-gate comparison turns that source separation into executable interoperability evidence.

Relations

2 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.