RapidClaw Base plus Dataverse and RapidStart Apps Agent Packs.
RapidClaw for RapidStart Apps is RCOC plus a Dataverse and RapidStart Apps extension layer. It inherits the shared Azure runtime, Command Center, Arcy, Teams, email, teardown, and model plan, then adds host context, Dataverse connector policy, app detection, and selected Agent Packs.
Inheritance Contract
RCRS owns Dataverse host context, custom Dataverse connector policy, RapidStart Apps detection and Agent Packs, product-specific Command Center pages, and the thin Dataverse solution launcher. It does not fork shared Setup, Azure runtime, Command Center shell, Teams transport, email platform, or teardown engine.
Delta Summary
| Surface | RCRS addition or override |
|---|---|
| Entry point | Dataverse solution/web resource launches hosted Setup in a new tab. |
| Product context | Dataverse organization, environment, tenant, and installed RapidStart Apps. |
| Entitlement | Included/free with RapidStart Apps; no separate runtime subscription gate. |
| Required connector | Microsoft Graph plus RapidClaw custom Dataverse MCP. |
| Agents | Adds only Agent Packs selected from detected installed apps. |
| Teams identity | RCRS prefix. |
Dataverse Host Integration
The managed Dataverse solution is a thin host integration and source-controlled configuration package. Its launcher opens the shared hosted Setup page and supplies product, host, organization URL, and environment unique name.
The web resource is not a second copy of the wizard and must not fall back to a stale embedded wizard.
Setup Differences
- Setup validates the exact Dataverse organization and tenant from launch and authenticated context.
- Deployment recovery is scoped to that environment and product composition.
- Step 4 detects supported RapidStart Apps solutions and presents only the corresponding Agent Packs.
- Email infrastructure belongs to Base; mailbox provisioning occurs later in Command Center.
Custom Dataverse Connector
RCRS uses the RapidClaw-owned Dataverse MCP provider. It is required and automatically configured for RCRS, while Business Central remains optional and operator-led.
- Exact Dataverse organization and tenant binding.
- Application-user access using an operator-selected least-privilege Dataverse role.
- Discovery of standard and custom Dataverse tables.
- Governed read and write operations with policy, approval, and audit enforcement.
RapidStart Apps Agent Packs
| Pack | Current managed agents |
|---|---|
| RapidStart CRM | Account Health, Contact Health, Relationship Intelligence, Prospect Qualification, Opportunity Follow-up, Service Support. |
| RapidStart Project | Project Health, Task Risk, Budget and Time. |
| RapidStart Field Service | Work Order Triage, Scheduling Readiness, Technician Schedule. |
Installation detection makes a pack available; it does not silently authorize every agent or tool. Base agents and shared assets are installed once, and pack manifests contribute only their product delta.
Data Ownership and Boundary
| Data | Authoritative owner |
|---|---|
| RapidStart business records and custom tables | Selected Dataverse environment. |
| Detected app and Agent Pack state | Current RCRS Dataverse integration tables. |
| 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 RCRS. |
| Secrets and connector credentials | Protected server-side and Key Vault path. |
RCRS does not add a separate VM shape, model plan, wizard shell, Command Center application, email platform, Teams transport, automatic Business Central binding, RCBC finance agents, or a second authoritative deployment-history store.