Join the business plane and the AI plane
with Bridge v1.
Your business system remains the single source of truth. The AI plane (DSH) keeps only conversations and memory, and reads business data on the user's behalf when needed. The two planes are joined by Bridge v1, a versioned HTTP protocol, and the manifest.
🏢 Business system
- Business data · staff & roles
- Rules · approvals · amounts · audit
- Who gets notified
Bridge v1
🤖 AI plane
- Conversations · long-term memory
- Automatic tasks · scheduled reports
- 9 plugins
💬 Chat
- Slack
- LINE
- Teams and more
The business plane owns
Business data, staff and roles, rules, approvals, amounts, audit, recipients and each person's notification settings, the AI employee's profile (versions and audit), and the manual index. No conversations.
The AI plane owns
Conversations, AI employee settings (persona and tools), chat connections, the automatic-task ledger and long-term memory. No business data — it reads the latest values through tools when needed.
Five layers
Dependencies run L5 → L3 / L2 → L1. L3 does not know L2 and speaks only HTTP, so your system need not be Node.js.
| Layer | Package | Role |
|---|---|---|
| L1 protocol | @dsh-bridge/protocol | Bridge v1 OpenAPI 3.1, manifest and event JSON Schemas, validators, the bridge-validate CLI and the conformance suite (52 checks) |
| L2 server-kit | @dsh-bridge/server-kit | Node.js parts for the business side: link codes, delegation, outbox, notifications, approvals, reports, proposals, manifest serving, personal-data screening… You write only hooks |
| L3 AI plane | @dsh-bridge/dsh-core + 9 plugins | Application registry, business API client, delegation cache, tool parts, the AI-secretary message frame, outbound screening |
| L4 Web | gateway · web-kit | An authenticating gateway from your web app's BFF to the AI plane, and React UI parts |
| L5 adapter | Your system | Manifest, hooks (or aliases of existing APIs), hand-written tool and template modules, approval and proposal screens |
Main flows
① Business change → notification (rule-based, no model involved)
② Questions and delegation (the AI reads with the user's rights)
③ Proposals and approvals (people decide, once)
④ Automatic tasks and scheduled reports
Who calls, and what they may do
| Principal | Who | May do |
|---|---|---|
| Service | The AI plane (DSH) | Identity lookup, minting delegations, events, resolving notifications, approval cards, manifest. Cannot read business data |
| Delegation | The AI employee acting for an employee (≤ 5 min) | Only reads and proposals the employee's role allows. Writes, approvals and confirmations get 403 |
| Employee session | The person using your web app | Issue link codes, own links, notification settings, accept proposals, approve |
| BFF | Your web app's server | Assistant tickets, attachment conversion, registering one's own bot |
Several systems on one AI plane
Conversations, memory, automatic tasks and notifications are separated per application. Tokens and tools never cross applications.
A stateless Bridge v1
Sessions, rate limits, codes, delegations and events live in PostgreSQL, so the business side scales out.
An isolated AI plane
The AI plane runs in an isolated home; its admin token never reaches the browser.