Permissioned access
Every tool connection is scoped by role. The employee can only access what you explicitly allow.
Security & governance
Built for real-world accountability.
Autonomous actions should be predictable, auditable, and easy to override. Turin keeps operators firmly in control at every layer.
Full audit log
Every action is logged: what happened, when, why, by which policy. Drill into any step.
Memory editor
Review, edit, and approve long-term memory updates before they take effect. No silent drift.
Escalation paths
When confidence is low or an action is outside policy, the employee pauses and routes to a human.
Spend controls
Credits are prepaid. Set a monthly budget; autopilot pauses at $0 unless you pre-approve a top-up.
Employment contract
Explicit working terms: autonomy level, escalation triggers, SLA, review cadence. All in writing.
Operating model
Safe delegation, explicit control.
Before action
Define role scope, approve tools, set autonomy level, and establish escalation triggers.
During action
Turin records intent, action, output, and policy path so teams can review exactly what happened in context.
After action
Review outcomes, correct memory, tune policies, and tighten boundaries without re-platforming workflows.
At scale
Keep consistency across teams using role packs, shared policy templates, and repeatable governance controls.
FAQ
Security questions
What makes it 'governed'?
Every action is logged, memory updates require approval, tool access is least-privilege, escalation paths are explicit, and spend is capped by prepaid credits. You stay in control at every layer.
How does memory work?
Memory updates are explicit — the employee proposes, you review and approve. You can inspect and edit memory at any time. No silent drift.
What if the employee does something wrong?
The audit log shows exactly what happened and why. You can revert actions where possible, correct memory, tighten the policy, and restart — often without any downstream impact.
Which Google Workspace scopes are needed?
You grant the minimum scopes for the role — typically read+send for Gmail, read+write for Calendar. Turin uses least-privilege access and never stores credentials.