Formara
Sign inVerify a Receipt
Formara Standard v1

The open verification standard for compliance receipts

This standard defines the rules for issuing, verifying, and governing deterministic compliance receipts across operators, retailers, and ecosystem partners.

Its purpose is simple: counterparties must be able to verify a receipt without trusting the issuer’s internal process or reopening the underlying document packet.

Request design partner accessVerify a Receipt
Standard modules
Receipt. Verification. Governance.
The standard constrains what a receipt is, what verification means, and how rulepacks are versioned and trusted.
Receipt Specification
Verification Standard
Rulepack Governance Model
Why a standard is needed

Compliance cannot scale on document review

Documents can be transmitted, but they do not function as an independently verifiable result.

Without a standard, compliance outputs remain trapped inside local workflows, reviewer interpretation, and repeated packet review. The standard exists so a receipt can be issued once, verified directly, and reused across counterparties.

Receipt Specification

Defines what a valid compliance receipt is

The Receipt Specification defines the minimum structure, identity, determinism, and integrity requirements for a reusable compliance receipt.

Required behavior
A compliant receipt MUST bind to a specific rulepack version.
A compliant receipt MUST produce a stable receipt hash under canonical serialization.
A compliant receipt MUST include a verifiable signature.
A compliant receipt MUST remain interpretable independent of the issuing workflow.
Prohibited behavior
A receipt MUST NOT depend on presentation order.
A receipt MUST NOT require hidden reviewer judgment for basic verification.
A receipt MUST NOT imply certification, approval, or legal determination.
Verification Standard

Defines what verification means

Verification is the deterministic process of validating receipt integrity, rulepack identity, and verification state. Verification is not document review.

Required behavior
Verification MUST recompute the receipt hash from canonical receipt content.
Verification MUST verify receipt signature against published key material.
Verification MUST validate the declared rulepack identity.
Verification MUST produce the same result for the same receipt state.
Prohibited behavior
Verification MUST NOT depend on local reviewer interpretation.
Verification MUST NOT require reopening document packets to confirm receipt validity.
Verification MUST NOT imply product safety, legal sufficiency, or market approval.
Rulepack Governance Model

Defines how evaluation rules are versioned and trusted

The Rulepack Governance Model defines how rulepacks are identified, versioned, published, superseded, and interpreted across the ecosystem.

Required behavior
A governed rulepack SHOULD publish family and version.
A governed rulepack SHOULD publish authority source, effective date, and published date.
A governed rulepack SHOULD publish digest or catalog hash.
A receipt MUST bind to the exact rulepack version used at issuance.
Prohibited behavior
A rulepack MUST NOT be treated as interchangeable across versions.
A published receipt MUST NOT float to a newer rulepack version implicitly.
Governance metadata MUST NOT depend on undocumented local workflow state.
Governance classes

Three governance models for published rulepacks

EXECUTABLE_BASELINE

Deterministic rulepacks whose outcomes can be computed directly.

HASH_ANCHORED_STANDARD

Externally governed standards referenced through stable digests and bounded verification semantics.

GOVERNANCE_BASELINE

Governance-only frameworks that define obligations without direct executable evaluation.

Core invariants

Small set.
Non-negotiable.

A receipt MUST be deterministic.
A receipt MUST be rulepack-bound.
Verification MUST be reproducible.
Verification MUST be possible without reopening source documents for basic receipt validity.
Rulepacks MUST be versioned.
The standard MUST remain publishable independent of any one workflow implementation.
Versioning and openness

Published, versioned, and constrained

The Formara Standard is versioned so receipts remain interpretable over time. New versions may extend receipt fields, verification semantics, and governance metadata, but they cannot break the core invariants required for deterministic issuance and independent verification.

Implement the standard early

Shape issuance and verification around the standard

Formara works with operators, retailers, and ecosystem partners shaping early issuance and verification flows around the standard.

Request design partner accessVerify a Receipt