Organization scope
Members, agents, tools, workflows, credentials, and runs belong to an explicit organizational workspace.
Security and governance
Control is part of the workflow.
Taskmesh is designed around explicit permissions, review boundaries, stable releases, and inspectable execution—not trust in an opaque agent.
Governance model
Separate who can build, approve, and act.
Responsible automation starts with clear boundaries. Taskmesh keeps organizational access, workflow publication, credentials, and runtime decisions within explicit scopes.
Permission boundaries
Authoring, testing, publishing, execution, approval, and source viewing can remain separate responsibilities.
Credential isolation
Workflows use configured connections without exposing stored secrets as ordinary workflow data.
Human approval
Pause before the action that matters.
A human task can stop a workflow at a deliberate checkpoint, present relevant context to an authorized reviewer, and continue only with the selected response.
Present
Show the reviewer the decision, supporting data, and available options.
Authorize
Require the decision from a user with the appropriate organizational access.
Record
Associate the response and resulting path with the workflow run.
Auditability
Preserve how a result was produced.
Taskmesh keeps the workflow version, node path, step results, approval context, and execution status together so operators can understand the complete run.
Published version
Validated input
Node results
Human decision
Final outcome
Execution isolation
Code runs as a constrained workload.
The Python tool is designed for pure computation. Source revisions are pinned at publication and executed in an isolated gVisor sandbox.
- No outbound network access
- No workflow credential access
- No mounted organization resources
- No mutable root filesystem
- No native-runtime fallback
- Separate author, test, view, and publish permissions
Integration boundary
Connect through published APIs, not back doors.
Taskmesh integrations communicate with external business platforms through their published APIs. Workflows, scripts, and background jobs do not connect directly to an external platform’s database.
Explicit operations
Select which API actions are available instead of granting broad, undefined access.
Configured connections
Keep authentication configuration outside ordinary workflow definitions and inputs.
Invocation context
Associate tool execution with the organization, workflow version, and run that requested it.
Design the control path alongside the automation.
See how workflow composition, stable publishing, and run inspection work together.