Point
Documents remain primary reading surfaces
Atlas adds explicit context around source material without forcing documents to become Point bodies or generated views.
- Posture
- asserted
- Lifecycle
- active
Long-form explanations, specifications, designs, policies, evidence, and code-adjacent guidance remain direct Resources. Atlas records why that material matters and how it participates in project context; it does not require every document to become a Point or every paragraph to be reconstructed as metadata.
This boundary protects the useful test. If the semantic layer merely reproduces document hierarchy, titles, or related-page links, it adds maintenance without adding meaning. Consumers must preserve direct reading and show each context edge separately instead of assigning one Point’s state or Map membership to an entire document.
Project contextDirect Resources keep project documents in the connected context without converting them into Point prose.
Useful differenceAtlas must add useful semantics around readable documents instead of charging readers a translation cost.
A reader must preserve direct document routes and show Atlas context as visible edges rather than replacing source material with generated semantic pages.
Publication must keep a Resource readable in its own right and explain every reason it entered the selected corpus. A document can be relevant through several Points and records, but it must not inherit one canonical posture, lifecycle, Map, or Area from those connections.
Reader experienceDirect document routes keep source material readable while Atlas edges provide optional surrounding context.