Skip to content
EVIDENCE-GROUNDED COMMERCE

VeriCommerce AI

Versioned catalog evidence, cited quotations and approved drafts across account roles and multi-format ingestion.

VeriCommerce AI public evidence-commerce website
CURRENT SCOPE

Deployed release 02 · 102 browser cases pass

WHO IT'S FOR

Independent build

My commerce evidence platform. The deployed core handles catalog evidence and approved JSON exports; Shopify publishing and model training remain roadmap work.

THE ENGINEERING

An independently built commerce evidence platform. Live release 02 (October 18) adds persistent account workspaces with four roles, bounded JSON/CSV/PDF/image ingestion, current-source retrieval with context inspection, cited quotations, temporal review, durable jobs, explicit approval and provenance export. React/TypeScript and FastAPI/PostgreSQL run together; Shopify access is read-products-only. Hosted checks on the newer published source passed 155 PostgreSQL/CPU/infrastructure checks, 17 Node checks and 102 desktop/mobile browser cases with zero skips. The live release matched 228 local/archive/live artifacts, passed 46 public browser cases and reproduced 27 SQL table snapshots with restricted-role/RLS probes. A newer release 03 was stopped before promotion at the owner's request, so its source-only assistant changes are not live. Shopify publishing and model training remain roadmap work; million-user capacity and 99% availability are future targets, not measurements.

ReactTypeScriptFastAPIPostgreSQLONNX

BEFORE → AFTER

Real problems from this build, what I changed and the verified result.

  1. CASE 01
    Before

    Catalog changes can leave an answer or approved draft pointing to obsolete evidence.

    After

    The deployed evidence workflow retains cited quotations and provenance; recorded browser journeys cover changed-source rejection.

    How I fixed it

    Preserved immutable source revisions and checked draft approval against current source identities.

  2. CASE 02
    Before

    A successful deployment does not prove stored evidence survives restoration or a release rollback.

    After

    Recorded restoration matched table payload counts/hashes; the approved draft retained its exact content hash and final deployment matched 84 artifacts.

    How I fixed it

    Rehearsed populated database restoration and actual runtime rollback followed by forward recovery.

Evidence reviewed: Google Doc release record reviewed October 25, 2026; October 18 release evidence and open gates stated above