workspace-environment

To ensure files are saved to the correct output directory, you need workspace file-writing rules that automatically enforce all deliverables go to the `output/` subdirectory. This guarantees correct file collection and retrieval in a containerized agent environment.

Preventing an agent from writing to forbidden absolute paths requires enforcing mandatory workspace file-writing rules that block restricted system directories like `/home/user/` or `/tmp/`. This actively promotes the use of relative paths for reliable file operations.

Generated reports fail to appear in the output directory because they were likely written to forbidden paths instead of the `output/` subdirectory. Enforcing relative path writing rules redirects all generated artifacts to the correct location for retrieval.

No, you cannot use absolute paths for file creation within this containerized agent workspace. Forbidden path prevention actively blocks attempts to write files to restricted system directories, instead guaranteeing all deliverables are directed to the `output/` subdirectory.

You need workspace environment rules for file writing whenever an agent creates, saves, or generates files in a containerized environment. This ensures that any report, data file, or generated artifact is correctly placed in the `output/` subdirectory.