# Competitive Platform

ClawOS is no longer just a local installer for OpenClaw. The product direction is now:

- OpenClaw-first migration
- local-first execution
- provider-neutral internals
- no paid product tier
- premium command-center UX

This document tracks the concrete primitives and surfaces that support that position.

## Product Surfaces

- `ClawOS Setup`
  - pack-first onboarding
  - provider profile selection
  - OpenClaw rescue/import
  - extension recommendations
- `ClawOS Command Center`
  - packs
  - providers
  - registry
  - traces
  - workflows
  - workbench
  - research
  - MCP manager
  - federation
  - studio
  - approvals
  - models
  - diagnostics
- `ClawOS Web Access`
  - browser-served version of the same product frontend

## Core Primitives

- `UseCasePack`
  - packaged outcome
  - setup defaults
  - dashboards
  - workflows
  - provider recommendations
  - policy defaults
  - eval suite
- `ProviderProfile`
  - local and cloud provider definitions
  - auth posture
  - default models
  - fallback order
  - cost and privacy labels
- `ExtensionManifest`
  - typed extension metadata
  - trust tier
  - permissions
  - network posture
  - pack dependencies
- `WorkflowProgram`
  - declarative workflow definition for long-term pack orchestration
- `TraceRecord`
  - local run record for packs, providers, setup, and extension activity
- `OpenClawImportManifest`
  - detected OpenClaw install
  - channels
  - skills
  - providers
  - migration actions
  - blockers and warnings

## Wave 1 Packs

- `daily-briefing-os`
- `sales-meeting-operator`
- `chat-app-command-center`
- `coding-autopilot`

These are the first packs ClawOS should make production-grade. Each one needs:

- a setup path
- seeded dashboards
- default workflows
- recommended extensions
- provider recommendations
- a policy pack
- an eval suite

## Provider Control Plane

The default provider posture is:

- `local-ollama` first
- explicit cloud profiles only when requested
- no provider credential leakage into agent context
- visible privacy and cost labels
- fallback routing instead of hard vendor dependence

Current profile targets:

- `local-ollama`
- `anthropic-api`
- `openai-api`
- `azure-openai`
- `openai-compatible`
- `openrouter`

## Registry and Trust Model

The registry must remain explicit about trust. Extensions should always surface:

- trust tier
- permission list
- network posture
- category
- pack fit

ClawOS uses three lanes:

- `Verified`
- `Community`
- `Quarantined`

## OpenClaw Rescue

ClawOS should be the easiest way to leave a fragile OpenClaw setup without losing the reason you installed it.

The rescue path should:

- inspect an existing OpenClaw home
- detect channels, providers, and skills
- summarize environment dependence
- recommend a primary ClawOS pack
- import safe configuration
- switch to a more stable provider posture when needed

## Current API Surface

Setup:

- `POST /api/setup/inspect`
- `POST /api/setup/select-pack`
- `POST /api/setup/import/openclaw`

Command Center:

- `GET /api/packs`
- `POST /api/packs/install`
- `GET /api/providers`
- `POST /api/providers/test`
- `POST /api/providers/switch`
- `GET /api/extensions`
- `POST /api/extensions/install`
- `GET /api/traces`
- `GET /api/evals`
- `POST /api/workbench/fetch`
- `POST /api/workbench/research`
- `GET /api/workbench/sessions`
- `POST /api/research/start`
- `GET /api/research/sessions`
- `GET /api/research/sessions/{id}`
- `POST /api/research/sessions/{id}/resume`
- `POST /api/research/sessions/{id}/pause`
- `DELETE /api/research/sessions/{id}`
- `GET /api/mcp/servers`
- `POST /api/mcp/servers`
- `PATCH /api/mcp/servers/{id}`
- `DELETE /api/mcp/servers/{id}`
- `POST /api/mcp/servers/{id}/connect`
- `GET /api/mcp/well-known`
- `GET /api/mcp/tools`
- `GET /api/mcp/resources`
- `POST /api/mcp/call`
- `POST /api/mcp/resources/read`
- `GET /api/studio/programs`
- `POST /api/studio/programs`
- `DELETE /api/studio/programs/{id}`
- `POST /api/studio/programs/{id}/deploy`
- `GET /api/a2a/agent-card`
- `POST /api/a2a/tasks`
- `GET /api/a2a/peers`
- `POST /api/a2a/peers`
- `DELETE /api/a2a/peers/{id}`
- `POST /api/a2a/peers/{id}/trust`
- `POST /api/a2a/peers/{id}/probe`
- `GET /api/a2a/signing-key`

## Current CLI Surface

- `clawctl packs list`
- `clawctl packs install <pack-id>`
- `clawctl providers list`
- `clawctl providers test <profile-id>`
- `clawctl providers switch <profile-id>`
- `clawctl extensions list`
- `clawctl extensions install <extension-id>`
- `clawctl rescue openclaw`
- `clawctl benchmark`

## What Comes Next

These surfaces are already wired into the repo; the next platform-depth work is making them
production-grade after the v0.1 release:

- Wave 1 packs completed end to end
- Browser Workbench for broader remote/mobile use
- stronger research depth and report quality
- richer MCP lifecycle management
- richer A2A federation and trust posture
- OTEL-native trace export
- stronger signed extension packaging and rollback support
