Platforms and providers

A platform is where a task, record, message, or file lives. A provider is the named service or source represented by a connection choice. An integration is the scoped connection that lets Lithi use that source for an approved purpose.

Use the terms together

The platform describes the surrounding service. The provider identifies the source. The integration joins one account, selected resources, permissions, local state, and workflow for one purpose. A provider name does not grant access, and an integration for one account or scope does not authorize another.

A compatible agent or application can use an integration only through a supported MCP or API path with approved access. Compatibility is qualified by the selected host, interface, account, and scope; a provider name alone does not establish it. Your agent keeps the goal, context, model, and final decision; the Compute Kit prepares permitted work and the approved interface; participating people's Macs perform supported work.

For example, a catalog row may describe a supported wire subset for a provider. That row tells you the source boundary; it does not confirm that your account, selected resources, or permissions are ready. Check the Compute integrations guide, choose the source, review its scope, and follow the visible next action.

Read catalog and connection status

The Compute integrations guide lists these boundary types: file adapter, compatible request format, supported wire subset, official SDK integration, and native live connector. The catalog status is an information signal, not a runtime health check. Evidence required means the relevant behavior still needs reviewable proof before a stronger statement is appropriate.

Useful evidence names what was checked, on which bounded surface, with what account and resource scope, when, and with what result. A badge or status word cannot replace those details.

Runtime state belongs to one connection on one Mac. It may be waiting, ready, unavailable, revoked, or unable to proceed. Treat the visible local state and next action as the authority for that connection.

Keep the connection scoped

Lithi for Mac handles connected-account setup and local work. Start authorization from the Mac, review the permission screen, and select only the resources your workflow needs. The source remains the authority for the account and permissions.

Keep credentials and local authorization material in the app's connection controls. Disconnecting, narrowing resources, or revoking authorization changes the connection decision; recheck the resulting state before relying on a task. If permission is missing, complete the requested authorization step instead of treating an earlier success as continuing permission.

Choose your next check

Use Privacy for data and authorization boundaries. When a local state needs attention, follow App or device problem and share only visible status, time, and next action.