env
Meaning and placement
→ permits
Engine env names passed through to child processes · exact POSIX names, no globs · composed with the runner env floor, never inherited (spec/01-envelope.md §permits · NEP-0005). An interpolated entry passes the shape gate and is refused as a non-literal bound (NIKA-AUTH-007).
In the same object: exec · fs · net · tools
Schema source (use the pointer above)
exec
OS environment variables for THIS subprocess · a key→value map applied over the composed environment. Nothing is inherited — the ambient environment reaches a task only throughpermits.env (spec/01-envelope.md §permits).
In the same object: capture · command · cwd · decode · shell · stdin
Schema source (use the pointer above)
Examples
No matching source-template occurrence is recorded in this projection. Write a workflow or consult the schema declaration above.Contract and implementation
This page projects the named specification revision. Check released engine status and the validation workflow before running a file. An optional field is not evidence that every engine supports every value. Canonical identity:language:word:env. Spec revision: c5ebbb7b862b.
How documentation stays connected.