Integrations and runtimes
Understand the proposed model for bringing an execution environment and connecting the services your work needs.
Separate the runtime from its connections
A runtime is the environment responsible for executing work. A connector gives that work access to a particular service. The proposed Autoglide model would let teams choose an execution environment and explicitly authorize the connections a mission needs.
The interface should make that responsibility visible. A role should know where it runs, which service account it can use, and what operations are permitted. No providers or connector compatibility are currently guaranteed.
Connect deliberately
A connection should name the service, account, requested permissions, and intended use. Reading calendar availability and creating an event are separate capabilities. A mission should request only the access needed for its work.
Authorization needs a defined scope and a way to revoke it. Credentials would belong in an appropriate credential system rather than mission text or shared notes.
A proposed scheduling flowSelect the environment responsible for execution. Permit a calendar connection to read availability. Prepare meeting options. Obtain permission before creating an event. Verify the event before reporting completion.
Report what actually happened
Prepared work, a requested operation, and a verified result are different states. A future connection should preserve that distinction instead of reporting success when a request merely begins.
- Identify the operation that was attempted.
- Show whether it was accepted and completed.
- Explain what remains unresolved after a failure.
- Leave a clear manual next step if the connection is unavailable.
Until these capabilities exist, the product preview demonstrates work and controls locally. It does not connect to your accounts, create events, or send information to another service.