|
1 | | -# ClawForge on AgentCore |
| 1 | +# OpenClaw Enterprise on AgentCore |
2 | 2 |
|
3 | 3 | Turn [OpenClaw](https://github.com/openclaw/openclaw) from a personal AI assistant into an enterprise-grade digital workforce platform — without modifying a single line of OpenClaw source code. |
4 | 4 |
|
@@ -168,6 +168,61 @@ The merged SOUL.md is what the agent reads. An SA agent and a Finance agent use |
168 | 168 | └─────────────────────────────────────────────────────────────┘ |
169 | 169 | ``` |
170 | 170 |
|
| 171 | +## Gateway Architecture: One Bot, All Employees |
| 172 | + |
| 173 | +A single OpenClaw Gateway on EC2 serves as the unified IM connection layer for the entire organization. IT Admin creates one Bot per IM platform (one Discord Bot, one Telegram Bot, one Slack App), and all employees share it. |
| 174 | + |
| 175 | +``` |
| 176 | +IT Admin (one-time setup): |
| 177 | + Discord → Create 1 Bot "ACME Agent" → Connect to Gateway |
| 178 | + Telegram → Create 1 Bot @acme_bot → Connect to Gateway |
| 179 | + Slack → Create 1 App → Connect to Gateway |
| 180 | + WhatsApp → Link 1 number → Connect to Gateway |
| 181 | +
|
| 182 | +All employees use the same Bot, but get different Agents: |
| 183 | +
|
| 184 | + Carol DMs @ACME Agent → Gateway → H2 Proxy extracts user_id → Tenant Router |
| 185 | + → AgentCore microVM (Carol's Finance Analyst SOUL) → Bedrock → reply |
| 186 | +
|
| 187 | + Wang Wu DMs @ACME Agent → Gateway → H2 Proxy extracts user_id → Tenant Router |
| 188 | + → AgentCore microVM (Wang Wu's SDE SOUL) → Bedrock → reply |
| 189 | +``` |
| 190 | + |
| 191 | +The Gateway doesn't do AI inference — it only manages IM connections. When a message arrives, OpenClaw's AWS SDK call to Bedrock is intercepted by the H2 Proxy, which extracts the sender's platform user ID and forwards to the Tenant Router. The Router derives a unique `tenant_id` and invokes AgentCore, which creates an isolated Firecracker microVM with the employee's personalized SOUL. |
| 192 | + |
| 193 | +### Employee Onboarding Flow |
| 194 | + |
| 195 | +When a new employee joins the company and needs their AI agent: |
| 196 | + |
| 197 | +``` |
| 198 | +Step 1: Employee joins company Discord/Slack/Telegram |
| 199 | + (or IT sends them an invite link) |
| 200 | +
|
| 201 | +Step 2: Employee DMs the company Bot for the first time |
| 202 | + Bot replies: "Pairing code: KFDAF3GN" |
| 203 | +
|
| 204 | +Step 3: IT Admin opens Admin Console → Bindings → IM User Mappings |
| 205 | + Clicks "Add Mapping": |
| 206 | + Channel: Discord |
| 207 | + Platform User ID: 1460888812426363004 (from pairing message) |
| 208 | + Employee: Carol Zhang (Finance Analyst) |
| 209 | + → System writes SSM mapping + approves pairing |
| 210 | +
|
| 211 | +Step 4: Employee sends another message |
| 212 | + → Gateway allows it (pairing approved) |
| 213 | + → H2 Proxy extracts Discord user_id |
| 214 | + → Tenant Router resolves: user_id → emp-carol → pos-fa |
| 215 | + → AgentCore creates microVM with Finance Analyst SOUL |
| 216 | + → Agent responds as "ACME Corp Finance Analyst" |
| 217 | +
|
| 218 | +Step 5: From now on, every DM from Carol goes to her personal Agent |
| 219 | + with her SOUL identity, permissions, memory, and skills. |
| 220 | +``` |
| 221 | + |
| 222 | +Zero configuration for the employee. They just DM the Bot. IT Admin does a one-click approval + binding in the Admin Console. |
| 223 | + |
| 224 | +For employees who don't use IM tools, the Web Portal provides the same experience — login with employee ID, chat with their bound Agent directly in the browser. |
| 225 | + |
171 | 226 | ## Key Features |
172 | 227 |
|
173 | 228 | | Feature | How It Works | |
|
0 commit comments