Day one, nothing to install
Forward it. The named person confirms it was really them. Everyone on the thread gets a signed receipt that anyone can check, and any change to it shows. No connectors, no IT project.
CC or forward the approval to your decision address.
In development · try it belowA one-page list of who may approve what. VAC asks the right person before the action.
NextAny system or AI agent asks: may this go ahead?
In developmentInside the systems you run, once the value is proven.
LaterTry it
Pick a sample approval. The forwarding step is simulated here; the confirmation and the receipt are real.
Within a minute, to the approver
The From line of an email can be forged, so nothing is signed until the named person proves who they are.
Not only email
Forward or CC. Outlook, Gmail, any.
In development“Record a decision” page, as above.
Live previewUpload an export or a spreadsheet. Marked as recorded after the fact.
In development“Get a receipt” on the approval message.
NextA shortcut on the approval message.
NextForward the site message.
NextForward a recording; the words become the decision.
LaterDocuSign, Adobe Sign or a scan.
LaterServiceNow or Jira comment.
LaterOne line, or a tool any agent can call.
In developmentStep 3 · in development
No vendor involvement: call it from a Power Automate HTTP step, a script, or an agent.
POST /v1/decisions
{"decision": "Release lot SX-2291-B", "approver": "qp@site.example"}
→ {"status": "awaiting_confirmation", "confirm_url": "…"}
→ {"status": "confirmed", "receipt": "https://vacprotocol.org/vat/verify/…"}
Where it leads
A quality lead or asset manager starts this week, with the approvals they already give. A register of receipts builds up on its own.
The same receipts become the evidence for governing every AI-assisted decision: who may decide, how far AI may act alone, human oversight you can prove.
See a pharma release sealed → See a water decision sealed → Platform capability map →