Point
Atlases are untrusted input
Processors bound local inspection, reject unsafe structures and paths, avoid retrieval and execution, and report incomplete work instead of assuming safety.
- Posture
- asserted
- Lifecycle
- active
Processors must not execute Markdown or JSON content, follow structural symbolic links, traverse unsafe local paths, fetch external URIs, or treat referenced operations as instructions. Local targets are checked only within the Atlas, and relative targets that leave the boundary are reported without being read by the standard validator.
If required inspection encounters an I/O failure, unsupported profile, ambiguous structure, or unsafe target, processing becomes invalid or incomplete. Embedding applications must also set appropriate file-size, memory, CPU, and time limits for their environment instead of assuming the portable format supplies runtime resource controls.
Security and authorityTreating all Atlas files as untrusted bounds what processors inspect and prevents semantic content from bypassing safety checks.