Point
Atlas maps connected project context
Atlas makes the context connecting project documents, decisions, questions, evidence, and perspectives explicit, portable, and navigable.
- Posture
- asserted
- Lifecycle
- active
Atlas makes the context between project documents explicit, portable, and navigable. It maps how strategy, product, design, architecture, implementation, operations, publication, security, and governance affect one another through durable decisions, constraints, evidence, tradeoffs, questions, and direction.
Atlas helps people and software agents connect project documents to the decisions, questions, and perspectives they inform, making that context navigable without moving or duplicating the documents. It gives those connections stable identity, explained context, explicit state and relations, and deterministic validation. Atlas Portal renders the model without each project building a context UI; every additional semantic primitive and application claim remains subject to evidence.
Project contextConnected project perspectives are the subject Atlas is meant to represent, so this claim defines the project-context scope.
Shared navigationShared identities and links make those perspectives navigable as one context rather than isolated documents.
Authoring turns connected perspectives into an explicit deposit decision rather than leaving their relationships implicit in documents.
The product thesis becomes operational when a writer can identify which durable perspective the new information affects, find the shared Point identity, and state that perspective’s consequence. The write path must make those decisions inspectable for both people and software agents.
RoutingTurning implicit document relationships into Atlas context begins with choosing the Map question those relationships affect.
Contribution boundariesAfter routing, the author must decide whether the material changes a canonical anchor or adds Map-local context.
Adoption outside the repository requires the project-context thesis to remain useful across different organizational and technical perspectives.
Another project should be able to derive Maps from its own durable questions rather than copying this Meta-Atlas taxonomy. Portability succeeds when the shared semantic contract supports different strategy, product, technical, operational, and governance contexts without hidden repository assumptions.
PortabilityThe project-context model must survive different organizations and toolchains instead of depending on this repository's categories.
Adoption costTeams must translate their own perspectives into Maps, so context-model fit is part of adoption cost.