Point
Documents enter Atlas through explained context
Documents remain Resources; useful claims receive Point identity and explained connections without requiring one Point per document or sentence.
- Posture
- asserted
- Lifecycle
- active
Keep incoming material directly readable. Register or link a useful Resource without manufacturing a Point when no independently referable item is established. A document can support several claims, one existing claim, or no Point at all.
For retained context, inspect candidate identities and preserve the source's distinctions and uncertainty. Add a material edge, improve an existing record, or create a scoped Point only where independent reference is useful. A second pass over unchanged meaning can require no edit; a new source can still add evidence.
Explained Area memberships and material roles make the added context inspectable. They do not require a copy in every relevant Map or an exhaustive source-unit inventory. A project can deliberately adopt stronger integration policy through Checks. Validation establishes record structure, not successful absorption or agent usefulness.
RoutingMaterial can remain directly readable while its useful implications answer one or several Map questions.
Identity searchA shared source can support independently standing claims, so document identity cannot decide Point identity.
Contribution boundariesContent and Reference roles add traceable meaning without replacing the source or copying it into every perspective.
Resource identity, Point identity, and contextual navigation remain separate so one document can support several claims or no Point at all.
The Resource identifies addressable material; a Point identifies a useful independently standing item. Several claims can cite the same document without sharing posture, lifecycle, or identity. A useful source can remain registered without any Point.
Local records and material edges explain particular connections rather than attaching every related tag to a document. Preserve their provenance and roles. Supporting rationale can stay with its claim, and unrelated implementation state should not be copied into every contextual explanation.
Maps and AreasQuestions explain useful relevance without assigning every source to an exclusive semantic location.
Point identity and recordsClaims sharing a source can have independent standing, so document or subject identity cannot replace the Point test.
Material and overlapMaterial roles preserve each source connection while optional context records add local significance.
Explained connections should make existing material easier to use without imposing a duplicate document or compulsory curation step.
The useful difference is contextual explanation around existing material, not the act of producing more records. A direct source answer, a source-only contribution, or a no-op can be a better result than another mapped item.
The portable model can support a shared portal and ordinary agents reading files. Neither representation establishes benefit by itself. Evaluate whether people and agents recover consequential distinctions across tasks without spending more effort maintaining them than the context saves.
Project contextUseful claims and source links expose project reasoning while leaving unmapped material available for direct reading.
Useful differenceThe semantic layer must justify its upkeep through better work rather than a larger inventory of Points.
Shared navigationPeople and agents can reuse explicit identities and source references without requiring the same reader application.
A reader should preserve direct document access and useful surrounding context without treating relevance as publication eligibility.
A document-first reader should show useful connections without requiring every document to acquire a Point. Exact source access and contextual exploration serve different requests; neither should force edits or unnecessary navigation.
A relevant but unselected source remains outside a publication build. Profile selection must not expand through document links, related Points, or Map overlap. Reader studies and publication evidence test different claims; neither a valid profile nor the proposed experience establishes either outcome.
Reader experienceKnown material should remain directly reachable instead of requiring a Map-first journey.
Publication evidenceReader benefit and boundary enforcement require evidence separate from a useful source-to-context explanation.