Loading...
RapidStart - Extension Specification
RapidClaw for Business CentralRCBC Extension Specification
RapidClaw Base plus a Business Central extension layer.
RapidClaw for Business Central is RCOC plus a Business Central extension layer. It inherits the shared Setup, Azure runtime, Command Center shell, Teams transport, email platform, and teardown engine, then adds Business Central context, connector policy, seeded finance agents and skills, status modules, licensing rules, and the thin AL host extension.
01
Inheritance Contract
The RCBC layer owns Business Central context, connector policy, seeded finance agents and skills, Command Center status modules, licensing rules, and the thin Business Central host extension. It does not fork shared Setup, Azure runtime, Command Center shell, Teams transport, email platform, or teardown engine.
02
Delta Summary
| Surface | RCBC addition or override |
|---|---|
| Entry point | Thin Business Central AL extension launches hosted Setup. |
| Product context | Tenant, environment, company, and Business Central region. |
| Entitlement | Sandbox included; production requires annual RCBC entitlement. |
| Required connector | Microsoft Graph plus official Microsoft Business Central MCP. |
| Agents | Adds the Business Central agent workspace. |
| Shared Base email; no RCBC-specific mailbox seeds. |
03
Business Central Host Integration
The signed AppSource extension is a thin launch and context surface. It does not contain a separate OpenClaw runtime or Command Center implementation.
The extension supplies or helps resolve tenant, environment name and type, selected company, Business Central Azure region, and the Business Central application/version context needed for setup and licensing.
AL update rule
A new AL package is required only when AL source, permissions, launcher contracts, or marketplace metadata change.
04
Business Central MCP Connector
RCBC uses the official Microsoft Business Central MCP endpoint at https://mcp.businesscentral.dynamics.com. The connector is required and automatically configured for RCBC, while Dataverse remains optional and independent.
- Streamable HTTP transport.
- OAuth 2.0 delegated authorization with PKCE and offline access.
- Tenant, environment, company, and configuration context through supported Business Central headers.
- Readiness probe for provider, OAuth material, and discovered tools.
05
Seeded Business Central Workspace
RCBC adds Business Central managed agents for cash flow, collections, credit, invoice research, payment reconciliation, finance briefings, exception monitoring, sales order fulfillment, inventory availability, master-data cleanup, and vendor follow-up.
The initial posture is read-first. Installing RCBC does not authorize autonomous posting, shipping, invoicing, payment, or master-data changes.
06
Licensing and Activation
- Sandbox Business Central environments are included without a paid RCBC subscription.
- Production Business Central environments require an active annual RCBC entitlement.
- Production fails closed if licensing cannot be verified.
- Financial writes, posting operations, external messages, and data-cleanup changes remain approval-controlled or blocked by default.
07
Data Ownership and Boundary
| Data | Authoritative owner |
|---|---|
| Business Central business records | Selected Business Central environment and company. |
| Setup orchestration and resume | Shared Azure Table deployment store. |
| Runtime policy, approvals, audit, memory, and deployment history | Deployment Azure PostgreSQL runtime store shared by Base and BC layer. |
| OpenClaw schedules and run history | OpenClaw SQLite. |
| OAuth tokens and connector secrets | Protected server-side and Key Vault path. |
Boundary
RCBC does not add a separate VM shape, operating system, model plan, wizard shell, Command Center application, Dataverse/RapidStart Apps Agent Packs, product-owned email infrastructure, seeded mailboxes, or a custom Business Central MCP provider.