Velil Start a proof sprint

This is the deliverable. Read it like your board would.

The proof pack lands at the end of an engagement: the record entries for one real workflow, the independent verification receipt, and a summary a director reads in one minute. Forward it internally; that is what it is for.

Specimen pack · company and names are illustrative · the format is exactly what you receive

Watch the record write, live Request the real one

Proof pack · agent refund approvals

Engagement complete · 5 of 214 entries shown
Company Mid-market insurer · agents in claims ops Workflow Automated refund decisions Record opened Day 2 of the engagement
1 · The record · five consecutive entries
Entry 209 Refund £412 approved · claim #48211 Sealed owner P. Chen, Risk & Controls · source pricing model v3.2 · approval policy 7.1, 09:14 sha256 8f41c2…d90a · chained to entry 208
Entry 210 Refund £2,180 escalated · claim #48213 Sealed owner P. Chen · threshold rule 4.2 exceeded · human gate D. Okafor approved 09:31 sha256 71bb08…44e1 · chained to entry 209
Entry 211 Refund £96 approved · claim #48214 Sealed owner P. Chen · source pricing model v3.2 · approval policy 7.1, 09:33 sha256 c03d9a…17f6 · chained to entry 210
Entry 212 Model updated v3.2 → v3.3 Sealed owner ML platform team · change ticket CH-2214 · approval CTO, 11:02 · correction written as a NEW entry, nothing edited sha256 5e77b1…a2c8 · chained to entry 211
Entry 213 Refund £388 approved · claim #48219 Sealed owner P. Chen · source pricing model v3.3 · approval policy 7.1, 11:15 sha256 fd120c…9b3e · chained to entry 212
2 · The verification receipt · run by the client's own engineer
$ python3 verify_velil.py record_export.json
reading 214 entries · rebuilding hash chain from entry 1
CHAIN VERIFIED · 214 of 214 entries intact · no edits, no gaps
owners named on 214/214 · approvals present on 214/214 · 40 lines, no dependencies, tools you control
3 · The board summary · one minute, one paragraph

For the period covered, every automated refund decision in claims ops is on a record a person can read: who owned it, what made it, who approved it, and when. The chain has been verified independently by the client's own engineering team. Corrections exist as new entries; history has no delete key. If a regulator, buyer or director asks the question, the answer is already written.

Written once · readable forever · verifiable by the reader Velil · velilhq.com · runs to the public Velil Standard

Forward this internally · what each seat sees

Engineering: A hash-chained log you verify yourself with a forty-line script. No vendor trust required.

Compliance and legal: Owner, source and approval on every action. Corrections are new entries · history has no delete key.

The board: One page a director reads without help, provable on any Tuesday.

Procurement: Fixed scope in writing. The record and verifier are files you keep, either way.

Procurement notes

Fixed-scope engagement · in writing before any commitment

The record and verifier export as files you keep · verification runs on your machines

The public standard and privacy note are published on this site

No outcome guarantees, as policy · a standard, a speed, and a record you keep

Not your workflow? It may be a client's · the pack forwards freely.

A pack like this closes a proof engagement on one real workflow of yours. It scales the way it reads: one workflow, a division, or the standing record. With August 2 approaching, a record started this week is on file before the date.

Start a proof sprint