Integrations
Integrations bind a wrapped outside Source to a System with credentials under an Agreement.
The record stays in db.sb; the outside tool reflects it or feeds it.
Contract
An Integration runs in one of two modes. In mirror, db.sb leads and the tool reflects it; in import, edits authored in the tool arrive as Changes. Neither mode makes the tool a second source of truth.
| Scope | Whose accounts | Example |
|---|---|---|
| Studio | Shared by every Startup in a Portfolio | One company-lookup Source for all |
| Startup | One Startup's own accounts | The team's chat workspace |
| Customer | A Customer's accounts, used on their behalf | A Customer's calendar, connected in the App |
Each Verb ranks its mappings to outside shapes, and a Policy picks one per call; the outside id is stored beside the platform id. Tokens are filled in at call time and never reach an Agent. Inbound signals arrive through the webhook ingress as Events and wake Triggers; a site with no API is reached through the Browser.
A code repository syncs with GitHub either way: db-first, where git is a projection rebuilt from db.sb, or git-first, where commits import as Changes.
Verbs
| Verb | Object | Event |
|---|---|---|
| Integration.create | Integration | Integration.created |
| Integration.sync | Integration | Integration.synced |
| Integration.call | Integration | Integration.called |
Interfaces
Example
hireloop.co runs interviews for growing teams as a Service. Each Customer connects their own calendar inside the App, at Customer scope. Revoking it ends every Agent's access at once, and every booking made through it stays on record.