Velil · Standards

The rules the record runs on.

Velil Record v1 is an open format: anyone can read one, and anyone can check that we kept our own rules. These are those rules, in the language we hold ourselves to.

S·01

Five fields, always

Action, owner, source, approval, next. A record missing a field is not a record, it is a note. Notes do not survive scrutiny; records do.

S·02

A named human owner

Software cannot own a consequence. Every record names the person accountable, even when the action was fully automated, especially then.

S·03

Approvals in writing

A rule, a gate or a person said yes before the action ran, and the record shows which. Where no approval path exists, building one is the work.

S·04

Readable by a director

Records are written in operator language. If it takes a data engineer to interpret, it fails the standard, whatever else it achieves.

S·05

The archive belongs to you

Your records are yours: exportable, readable, and kept whether or not we continue working together. Proof that locks you in is not proof.

S·06

No certification theatre

We do not issue compliance certificates and we do not claim regulatory outcomes. We keep operational records that make hard questions easy to answer.

The format specification, field definitions and a specimen record are shared in every engagement, before any payment, so your team can judge the standard before buying it. Read the specimen record now.

Start a proof brief
Start a proof brief · senior reply in one day