Connectors, Apps, Agents, And MCP

Principle

Prox OS should use the smallest surface that matches the job:

connector-first, app-when-visual, agent-everywhere, MCP-when-external-tooling

This document stays abstract. It does not define specific communication, schedule, weather, contact, or external social feed products.

Connectors

Connectors are for user-authorized data or tool boundaries. They should declare:

source identity
available scopes
read and write capabilities
refresh policy
secret handling
audit labels

Apps are for visual, interactive work. If a workflow needs inspection, comparison, editing, dashboards, or repeated human control, it should become an app or app surface instead of a hidden tool call.

Agents

Agents can help across apps and connectors, but they must remain:

observable
pausable
permissioned
auditable
scoped to workspace or app domain

MCP Gateway

Future MCP Gateway should expose approved tools and context boundaries. It should not bypass Prox OS permission policy or secret handling.

Alma Relationship

Alma is the shell surface that can see the declared apps, connectors, permissions, workflow cards, artifacts, and future MCP tools. It should present structured actions before execution.

Backend Direction

Future apps/api-worker can host a tool registry, provider adapters, model router, audit sink, secure key vault, workflow execution service, and permission policy engine. None are implemented in this task.