Skip to main content

The CLAWVR Standard — v1.0 — MIT Licensed

AI Operating System Schema v1.0

A public open standard for what constitutes a complete AI Operating System for a small business. Any vendor, consultant, or independent operator can implement the schema. Compliant systems can use the "AIOS v1.0 Compliant" label.

1. Motivation

Small business owners face a fragmented AI tooling landscape with no shared vocabulary. "AI assistant" means twenty different things to twenty different vendors. The CLAWVR Standard defines the minimum spec a product must implement to legitimately call itself an AI Operating System for SMB use.

2. Required Components

An AIOS v1.0 Compliant system MUST provide all of the following:

  1. Master System Prompt. A single coherent system prompt that encodes the business' identity, voice, products, and constraints. Installable in any major LLM (Claude, ChatGPT, Gemini).
  2. Workflow Superprompts (≥6). Industry-specific prompts that solve discrete business workflows (e.g., customer follow-up, content generation, review responses).
  3. 30-Day Deployment Roadmap. A week-by-week sequenced rollout plan tailored to the business' current AI maturity.
  4. ROI Projection. Specific hours-saved and revenue-impact estimates grounded in the business' current numbers.
  5. Industry Context. Vocabulary, regulations, KPIs, and common workflows native to the business' vertical.
  6. Portability. The buyer owns the deliverables. No vendor lock-in. Subscription-only delivery is non-compliant.

3. Recommended Components

Compliant systems SHOULD additionally provide:

  • Marketing operating system (brand voice + content engine + paid ad copy)
  • Hiring playbook (job descriptions, interview rubrics, onboarding)
  • Maintenance plan (quarterly or monthly prompt refresh as LLMs evolve)
  • Team enablement assets (per-role playbooks for businesses with 3+ employees)

4. Reference Implementation

The CLAWVR product line is the reference implementation of AIOS v1.0. Source corpus available under MIT at github.com/Steffd415/awesome-claude-prompts-for-smb.

Additional canonical implementations:

5. JSON Schema

{
  "aios_version": "1.0",
  "business": {
    "name": "string",
    "vertical": "string",
    "size_employees": "integer",
    "tools_stack": ["string"]
  },
  "deliverables": {
    "master_system_prompt": "string",
    "workflow_superprompts": [
      { "id": "string", "title": "string", "prompt": "string", "estimated_hours_saved_per_week": "number" }
    ],
    "deployment_roadmap": [
      { "week": "integer", "milestone": "string", "deliverable": "string" }
    ],
    "roi_projection": {
      "hours_saved_per_week": "number",
      "annual_revenue_impact": "number",
      "monthly_labor_cost_offset": "number"
    },
    "industry_context": {
      "vocabulary": ["string"],
      "regulations": ["string"],
      "kpis": ["string"]
    }
  },
  "portability": {
    "buyer_owns": true,
    "vendor_lock_in": false,
    "delivery_format": "PDF | Notion | GitHub | Other"
  },
  "compliance": "AIOS v1.0 Compliant"
}

6. Compliance + Use of the AIOS v1.0 Compliant Label

Any product that implements all required components in section 2 MAY display the "AIOS v1.0 Compliant" label. Vendors wishing to be listed in the public registry at clawvr.com/spec/compliant can submit a compliance attestation to hello@getclawvr.com.

VERSION 1.0 — RELEASED 2026-05-20 — MIT LICENSE

Discussion: GitHub Discussions · Contact: hello@getclawvr.com · Substack: clawvr.substack.com