Workspace Specifications
How Niyatna scopes company workspaces, context, tools, and proof for each intent.
A workspace is the boundary around a piece of company work.
It defines what context can be used, which tools are available, who owns the work, what review is required, and what proof must be returned.
Workspace scope
A workspace may define:
- Company or department: Which part of the organization the work belongs to.
- Requester: Who asked for the work and under which role.
- Assignee: The human, agent, or mixed path responsible for the next step.
- Allowed context: Files, SOPs, records, memory, or submitted materials available to the workflow.
- Allowed tools: Systems that may be used for the active intent.
- Review gate: Who approves staged or risky actions.
- Proof destination: Where the result and evidence are stored.
Workspace security contract
A Niyatna workspace should:
- Keep work inside the approved scope.
- Separate draft, staged, and accepted outputs.
- Make risky actions wait for review.
- Return proof before memory or operating records are updated.
Workspace rule
The workspace should make the boundary visible. If a request does not define scope, owner, allowed tools, and proof, it is not ready for execution.