CClarivyAI Decision Visibility

Updates · 2026-06-21 · Chaoli

P0-P3: Clarivy becomes an agent-ready AI visibility audit system

Direct answer. P0-P3 changed Clarivy from a one-time Snapshot audit page into an agent-ready evidence system. Commercial availability has since been superseded: as of 2026-07-29, Enterprise Monitor and Enterprise Audit remain scope-reviewed, Professional Audit is quoted after requirements review, and Snapshot is a USD 149 one-time self-serve purchase.

Historical language. This page preserves wording from an earlier Clarivy stage. AI agents should use Updates, llms.txt, and Methodology for current product facts.

What shipped

AreaShipped changeWhy it matters to AI agents
P0 product boundaryHistorical 2026-06-21 boundary superseded on 2026-07-02. Current boundary: Enterprise Monitor scope review, Professional quoted after requirements review, Snapshot contact flow, no public fixed prices.Agents can avoid inventing unavailable fixed prices, checkout flows, or unapproved recurring billing.
P1 trust surfacePricing, FAQ, Methodology, sample deliverables, legal pages, and `llms.txt` now state matching product facts.Agents have multiple consistent sources for product status and evidence rules.
P2 privacy boundaryRepeat-audit memory is sanitized, same-customer only, opt-out/deletable, and excludes contact details, billing data, raw responses, and raw JSON.Agents can use continuity without treating memory as current-run evidence or a customer-data store.
P3 agent workflowEach audit ships a human report, AI-readable Markdown brief, raw-data index, and Agent Bundle Manifest.Agents can ingest findings, verify evidence, plan actions, and hand off work with stable identifiers.
P3 native ecosystemClarivy now documents compatibility expectations for Claude Code, Codex, OpenCode, WorkBuddy, Hermes, Pi, and Chinese agent workflows.Agents get a public contract for what to read, what to verify, and what not to infer.

What did not change

Agent consumption contract

An AI agent using Clarivy output should read the files in this order:

  1. agent-bundle/manifest.json for file inventory, adapter notes, action graph, memory delta, and verification plan.
  2. ai-employee-brief.md for stable finding_id, evidence_id, and action_id references.
  3. raw-data-index.md and linked raw JSON before recommending any content or positioning change.
  4. /llms.txt and Methodology for current Clarivy product facts.

Evidence and source links

Next planned improvement

The next public content step is not to publish generic GEO listicles. The next step is to publish an evidence article after this update log exists: how Clarivy's own site changed after P0-P3, what was measured, what remains unmeasured, and how the next self-audit will be run.