Point
Integrations remain caller-authorized
A consuming or authoring integration preserves Atlas semantics but receives every operational capability from its caller, not from mapped relevance or policy.
- Posture
- asserted
- Lifecycle
- active
An authoring tool, agent, search indexer, publisher, or other consumer may use Atlas to select relevant context and applicable policy. It must still receive filesystem scope, network access, credentials, publication permission, deployment rights, and execution capability from an independent caller or platform boundary.
The integration must expose provenance and refuse ambiguous operations. It cannot interpret a Reference as retrieval consent, a Point direction as an instruction to execute, or a passing Check as permission to publish. This constraint applies even when the same software both reads and writes the Atlas.
IntegrationCaller-supplied capabilities are the integration boundary that keeps semantic consumption separate from operations.