Integrations
Gwen can work through the tools the job needs.
Users should not need to manage the machinery. Gwen scopes the work, identifies needed connections, asks for approval, and uses the right integration path when the capability is available.
Integration categories
This is the public map of the kinds of systems Gwen can use. Live and pilot status will keep tightening as each path is smoke-tested.
Communication / Pilot
Email, inbox, chat, and messaging channels that let Gwen read, draft, route, and follow up with approval. Examples: Gmail, Outlook, Slack, Telegram, SMS, WhatsApp.
Documents and knowledge / Pilot
Documents, files, notes, drives, and knowledge sources that become useful context for missions and memory. Examples: Docs, Drive, spreadsheets, knowledge bases, shared files, research notes.
Research and web / Live
Research paths Gwen can use to inspect public information, summarize sources, prepare briefs, and watch for changes. Examples: web research, browsers, news, market pages, funding sources, public datasets.
Business systems / Future
CRM, finance, support, marketing, analytics, and operations systems that Gwen can coordinate as integrations mature. Examples: CRM, accounting, support desk, analytics, project management, marketing tools.
Software and runtimes / Pilot
Code repositories, runtime workspaces, command-line engines, and review loops for software missions. Examples: GitHub, cloud runtime, coding engines, test commands, pull requests, deployment checks.
Payments and approvals / Live
Billing, budget, spend control, approval queues, and audit trails for governed work. Examples: Work Budget, Stripe, approval gates, spend limits, mission ledger, audit events.
Ask for the outcome, not the engine
Gwen should choose whether a mission needs chat, memory, documents, email, a browser, a business system, a code workspace, or another execution engine. The user asks for the result; Gwen explains what access is needed before using it.