Public receipts

The deployment identifies itself.

A deployment receipt ties this public site to the source and files used to build it. We publish these fields so a claim can be checked against something more durable than our word, and anyone can ask us to prove a claim by emailing hello@vetmycredit.com.

Current deploymentQC-SITE-POLISH-01

VetMyCredit public site

Deployment ID
QC-SITE-POLISH-01
Cloudflare deployment
Published in the post-deploy E-1 receipt
Source commit
54205cee0ffb0dda74cb31c1efd4b9b8fcbe4241
Content-manifest SHA-256
c73f7c9076df6d63f181232d18029e07a4f108d077be344e54f9db92a130e782
Deploy timestamp
2026-08-01 01:40:34 PDT (-0700)
Armed rollback target
479daa59-af9d-4aca-9d03-3f8505bcf7bf
manifest c73f7c90✓ Published receipt

What “13 findings” means

It is the finding count in the single illustrative audit identified by sample artifact SHA-256 2bbe3d345816fb1ab3bc726388e7b4f0662071d4aac06f52879e8943d8ed658d. It is the founder's own file, not a user count or a typical outcome.

Receipt: A5-G7.1 decision and deployment receipts, source hash prefix 2bbe3d34.

What “57 / 57” means

It is the receipted engine test gate recorded for the prior public release. It describes that named gate run; it is not a customer count, an accuracy percentage, or an outcome promise.

Receipt: Wave 1 deployment, content manifest f3990401…0609.

What the content hash covers

The manifest lists the public source files by SHA-256 before deployment-specific receipt fields are substituted. The E-1 evidence receipt records both the canonical manifest and the exact deployed-content hash.

See what the audit flow asks of you.

Start your free audit