Integrations and tools
Boundary firstExpose context carefully. Admit execution separately.
An integration can read, propose, subscribe, or execute. Those are different powers. SkyTwin documents them separately and does not treat connector code or a model response as authorization.
Current status
| Surface | What a source evaluator can inspect | Supported-preview status |
|---|---|---|
| Fictional sample | Briefings, decisions, approvals, controls, and explanations using made-up data. | Available and account-free. |
| Gmail and Google Calendar | Live connectors in the historical desktop alpha and exact experimental source mode; the alpha wizard is available in its window and to an already authenticated local-browser session; connector architecture and tests. | Available as advanced Google setup. The alpha contains a historical SkyTwin-team client ID for initial identity/Calendar authorization and requires a user-created client for Gmail; current source uses an operator-created client. No supported managed SkyTwin client; credential and unsigned-alpha limitations apply. Setup guide. |
| Microsoft accounts | Retained Outlook/Graph implementation and source tests. | Experimental source implementation only; no equivalent supported setup path or managed OAuth client. |
| Local MCP server | Scoped context, proposals, and subscriptions for a local agent. | Documented for source builders; policy and approval remain mandatory. |
| Execution adapters | Admission, fallback, provenance, risk, and policy structure. | Only admitted work may enter an adapter. A proposal is not execution authority. |
| DXT transfer | Source artifact format and intended configuration-transfer design. | Forward-looking. Do not treat it as a current public workflow. |
Local MCP is scoped, not delegated autonomy
The Twin MCP server is a local, token-scoped surface for agents. A safe agent reads context and may record an action proposal with source and reasoning. The current proposal path is inspection-only: it neither runs policy evaluation nor creates an actionable approval request. An agent must not bypass policy, fabricate provenance, or reinterpret that record as permission.
The agent guide covers setup, scopes, tool classes, failure handling, and a recommended safe loop. For the raw contract, use the MCP protocol reference.
The execution boundary
Candidate actions travel through typed risk assessment, provenance checks, trust-tier rules, hard spend limits, and an explanation requirement. Untrusted-origin destructive work escalates to a person; absent provenance fails safe. The execution router selects only from admitted adapters and backs up the policy-engine decision rather than replacing it.
execution: null. No Gmail mutation caller, recovery
worker, or feedback projection is wired into runtime. Enabling its
development flag is not a support or execution claim.
Configuration transfer is not secret transfer
The DXT design describes moving capability configuration between machines. It intentionally excludes OAuth tokens, which must be re-authorized on the target. Live federation is deferred; read the DXT reference before treating a source artifact as a supported product feature.