Control
Gwen should be powerful, but governed.
Intelligence That Works needs memory and tools. It also needs clear boundaries, approval gates, scoped credentials, and a mission ledger.
Control model
User-controlled memory
Users can review, approve, edit, and forget remembered context.
Approval before external action
Sending, purchasing, scheduling, deleting, and other side effects can require explicit approval.
Scoped tools
Tool access is workspace-scoped and can be separated by read, write, spend, and destructive capability.
Mission ledger
The ledger shows what Gwen is doing, what needs approval, and what was delivered.
Mission-backed audit
Gwen records action checks, approvals, audit events, context, memory updates, feedback, and usage telemetry. The product experience stays focused on work and approvals instead of exposing infrastructure plumbing.