Connectors & the vault

Connecting an account is the moment most agent systems quietly hand a credential to a language model and hope the prompt holds. oshal does not. The credential is consumed by a schema-bounded server operation, the call completes outside the model, and only the normalized result is allowed into reasoning.

That is the whole reason connectors are a platform concern rather than an app concern: an app declares what it needs, and the platform decides what the model gets to see.

• 310 connector definitions live as audited specs in the repo — a catalog you can read before you trust it, not a list of logos.
• Per-user encryption. One person connecting their mail does not give the swarm anybody else's mail. The scope is the individual, not the deployment.
• Two registration shapes only. An OAuth client with a fixed callback, or a pasted access token. Every partner integration follows the same documented path, so adding one is a form to fill in rather than a new design to review.
• No connectors to nowhere. A connector ships when its token drives a genuinely usable API. Integrations that would need a certification the project does not hold are documented as staged rather than shipped as a dead tile.