Public proof status

Proof and capability status for safe commerce automation.

This page separates what is ready to show, what is approval-gated, and what still needs a live proof clip before stronger public claims.

Latest recorded AI quality gate: PASS (October 10, 2026; tested runtime 01eb7557). In isolated synthetic tests, 240 customer questions passed. Production AI performance and external channel behavior require separate live evidence. General launch readiness is not established. The statuses below describe scoped evidence only. Report: latest recorded result.

Capability matrix

What can be claimed and what still needs proof.

Capability
Status
Current proof
Next proof target
AI website widget
Technical path verified
Public widget, install paths, and deterministic checks exist for storefront support.
Pass the live AI release evaluation and repeat a storefront canary after release.
Knowledge-grounded support
Local/static proven
Answers can use store knowledge and show when a source is missing.
Add more merchant-specific policies before deeper automation.
WordPress / WooCommerce setup
Gated proof needed
A production path covers the WordPress plugin, WooCommerce order and authenticated inbox, but it is not independent merchant proof.
Repeat the full loop with one independent merchant and capture guarded-action receipts.
Shopify App Store workflow
Scoped live-review UAT
A development-store and live-review UAT covers install, embedded UI, order context, guarded action, webhooks and reviewer evidence.
Keep deployment health, widget canaries and Shopify UAT evidence fresh after each release.
Salla merchant workflow
Gated proof needed
One live Salla proof passes, but broad self-serve marketplace readiness needs repeated merchant evidence.
Repeat install, catalog sync, grounded widget answer and dashboard visibility across merchants.
Approval-gated commerce actions
Gated by default
Refunds, cancellations, order edits, and discounts stay behind merchant approval rules.
Record action receipts from live merchant workflows.
Stripe billing
Gated proof needed
Billing code exists, but full live checkout, signed webhook, reconciliation, dunning and canary evidence is incomplete.
Capture one checkout-to-recovery canary with usage reconciliation and signed webhook evidence.
Agent notification and reports
Local/static proven
Escalation and digest paths exist for agent review.
Tie channel notifications to verified sender and inbox proof.
Meeting booking
Controlled workflow
Booking can be treated as a low-risk support workflow with human-visible context.
Add one concrete chat booking proof clip.

Review rules

Proof clips must match the public claim.

aserva can move fast, but each public claim has to stay tied to evidence a merchant or reviewer can inspect.

Do not call a channel live until the inbound event, AI handling, outbound delivery, and human takeover path are verified.

Do not execute risky commerce actions unless the merchant has approved the workflow rule or specific action.

Do not use proof clips that hide the setup state, provider, or required verification step.

Start with one workflow proof.

Scan a store, connect the first channel, and keep risky actions under merchant control.

Start scan