Approvals and control

Gwen can usually read available context, scope work, draft text, summarize information, and prepare artifacts without taking external action.

External sends, publishing, purchases, payments, record changes, code pushes, deployments, deletions, and sensitive actions should ask for approval or follow a configured policy.

The mission ledger shows what Gwen is doing, what context was used, what tools were attempted, which approvals are waiting, and what was delivered.

Higher tiers can support more configurable approval policies, role separation, and governance for teams using Gwen across many workstreams.