The canonical shared RapidClaw foundation.

RCOC packages deployment, identity, SI models, connectors, agents, governance, Microsoft Teams, email enablement, monitoring, and operator controls into a guided product. It has no Business Central or Dataverse host dependency.

Business Central and Dataverse connectors remain available for operator-led setup later, but they are not activated automatically in the Base composition.

The installed product profile is immutable. Product upgrades may update the selected profile, but an RCOC deployment is not converted in place into RCBC or RCRS.

• Checkout Session identifiers are claim hints, not authorization by themselves.
• The deployment service verifies the session server-side, checks product and price, validates payment and subscription state, and binds entitlement to the authenticated tenant.
• The shared six-stage wizard is Connect, Deploy, OpenClaw, Agents, Teams, and Command Center.
• RCOC is sold as a monthly subscription with the first month free through the approved Stripe promotion flow.

• Setup discovers the deployable GPT family and selects up to three compatible variants from the same version and SKU.
• Variants are prioritized quality-first: sol, then terra, then luna.
• Arcy and builder workflows prefer the quality tier; balanced workloads can use lower-cost tiers.
• text-embedding-3-small supports memory search and indexing.
• Foundry Model Router availability is detected and reported, but the verified direct-model plan remains the default deployment path.

The customer runtime is isolated in the customer Azure subscription and includes the Ubuntu VM, OpenClaw extended-stable runtime, nginx and OAuth protection, Command Center, Arcy, memory, Microsoft Graph MCP, connector registry, governance services, Teams forwarding, and email controls.

Installation artifacts are immutable and checksum-verified. Runtime operations are retry-safe, and teardown is manifest-driven.

RCOC seeds two RapidClaw-managed agents: RapidClaw, the product orchestrator and general operating agent, and Arcy, the Command Center guide, builder, diagnostician, and governed operator assistant.

• Create or edit an agent.
• Create a skill.
• Configure an MCP connector.
• Draft a scheduled task.
• Create or revise a prompt or policy.
• Use live selectors for agents, models, data sources, connectors, tools, schedules, and policies.

Raw secrets do not enter Arcy chat, URLs, logs, persisted browser state, connector configuration, API responses, or dashboard rendering. Secret values are entered through protected dialogs and stored through Key Vault-backed handling.

Email infrastructure is shared Base capability. Mailbox creation occurs in Command Center, and external communications remain subject to policy and approval. Teams readiness remains false until publication and the forwarding path are functional.