An open receipt format for runtime assurance proof.

§ i · definition

What OVERT is.

OVERT defines a compact, cryptographically sealed record — a receipt — that records the relevant runtime event, control decision, outcome, and verification data without exposing the sensitive payload. Each receipt is signed and chained to the previous one, so a history of decisions can be reviewed as a tamper-evident sequence.

The specification covers three things: the schema of the receipt itself, the signing semantics that produce it, and the verification rules any third party can use to check it. That is all. OVERT deliberately does not prescribe the model, the policy language, or the enforcement engine — only what gets recorded and how it can be trusted.

§ ii · rationale

Why an open standard.

Attestation is only useful if someone who does not trust the vendor can still verify the claim. A closed, vendor-specific format does not meet that bar — it asks auditors, regulators, and insurers to take the vendor’s word for it. An open specification removes that dependency: any conformant verifier, in any jurisdiction, can check a receipt without GLACIS in the loop.

OVERT is published under terms that allow anyone to implement it, including competitors. The value of a standard grows as more parties adopt it, and we would rather compete on the quality of the runtime than on the walls of the format.

§ iii · scope

What is in v1.0.

• Receipt schema. Required and optional fields covering subject, probe, verdict, policy, witness, content hash, and chain pointer — enough to replay an evaluation and verify its result.
• Witness semantics. Signing rules for producing a valid receipt, signature algorithm profile, and the conditions under which no receipt is written rather than a partial one.
• Verification rules. The exact checks a verifier must perform to accept a receipt as valid, including schema validation, signature verification, and chain integrity.
• Versioning and profiles. How OVERT evolves without breaking older receipts, and how industry-specific profiles layer on top (healthcare, financial services, medical devices).

Spec · overt.is / v1.0.0·April 2026

§ iv · governance

GLACIS’s role.

GLACIS authored the initial draft of OVERT and maintains reference verification tooling. The specification itself is governed through the OVERT IPR policy published on overt.is, with contributions open to organizations that need portable runtime assurance evidence.

OVERT is the receipt format and verification layer behind Glacis. Runtime controls create the assurance. Signed receipts preserve the proof. OVERT makes that proof easier to verify and use.