Workspaces & Execution Boundaries
Reference for how Niyatna scopes delegated work, tool permissions, and evidence logging.
A workspace is the boundary around delegated company work.
Instead of letting agents run uncontrolled commands in system roots, Niyatna keeps each task inside a dedicated workspace with its own files, permissions, and temporary area.
How work is scoped
Every execution lane enforces clear boundaries:
- File scope: Agents are limited to their assigned project repository or an isolated temporary directory.
- Tool permissions: Tools are declared up front in the workspace profile. Unauthorized network calls or unapproved shell operations are denied by policy.
- No blind codebase changes: Primary codebase changes are not made blindly; larger coding tasks are delegated to separate isolated environments.
How work is delivered
When work in a workspace completes:
- Evidence check: Independent tests or exit codes must confirm success before a status is reported.
- Durable output: Deliverable artifacts (reports, generated media, compiled binaries) are copied to the task attachments or the target project folder.
- Temporary cleanup: Temporary files and intermediate workspaces are cleaned up automatically after a set period.