Point
Safe parsing rejects ambiguous input
Strict text, JSON, structural discovery, symlink, path, and nested-boundary rules make processor behavior explicit and fail closed.
- Posture
- asserted
- Lifecycle
- active
Structural files use strict UTF-8, one JSON object between front-matter delimiters, and CommonMark bodies. Processors reject byte-order marks, NUL, invalid UTF-8, duplicate decoded member names, unsupported JSON syntax, non-finite numbers, unsafe integers, unpaired Unicode surrogates, and malformed structural locations. These checks keep metadata interpretation consistent across implementations.
Discovery does not follow symbolic links, ignores defined build and package outputs, and stops at nested Atlas roots. Local target checks require exact regular paths and reject structural or reserved targets. If required filesystem inspection cannot complete, the result is incomplete instead of pretending the input is conforming.
Syntax and discoveryStrict UTF-8, one JSON object, and bounded discovery make the accepted input language unambiguous.
ResolutionPath, symlink, nested-boundary, and target rules prevent unsafe or ambiguous files from entering resolution.