Filesystem functions
File reads resolve relative to the directory of the source declaring the expression, including a child module. They never use the controller working directory or home. path.module identifies that root.
Read paths may be relative or absolute inside the declaring root. Parent traversal, URI paths, outside absolute paths, escaping or dangling symlinks, and nonregular reads fail. In-memory sources must supply an explicit root, and all source names in a compilation must be unique so declaring roots cannot be confused. fileset requires an existing base directory, refuses directory symlinks and symlink entries, and inspects at most 100,000 entries.
Local reads may precede global catalog validation because they supply desired values. Cloud resource acquisition waits for global validation. Rendered/read bytes used as file content are bundled; applying needs no source files. Lexical basename/dirname do not grant read access. File hashes are listed under hash and crypto. templatefile and templatestring are detailed under templates.
Example
All calls obey the function limits and annotation rules.