PSP-style mappings; no official affiliation or affiliation implied. Integrity-only packaging standard; no outcome/admissibility promise.
Open Pack (New)
New sector-supporting pack page for integrators. Interop checked status requires evidence: RunID + vector set + summary hash.
Conformance Hub
For a plain-language overview of the record model, status taxonomy, and export format — see ERF Record Model & Reference Layer →
Registry-style compatibility checks: validators + test vectors + a strict backward-compat contract. No user data.
Validators
Feed: /digest.json
Reality Audit: integrity-only (tamper-evident). No legal claims. No promise of admissibility/court acceptance.
Test vectors
Download deterministic JSON vectors (v1):
- erf_valid_provisional.json
- erf_valid_final.json
- erf_invalid_missing_fields.json
- erf_invalid_bad_types.json
- erf_unknown_missing_evidence.json
- erf_policy_snapshot_vector.json
- autopilot_woo_vector.json
- autopilot_education_vector.json
- autopilot_supplychain_vector.json
Vectors are static files. No tracking. No remote scripts.
Backward-compat contract
- Endpoints remain stable (no breaking changes).
- Receipt JSON shape remains stable (schema evolution is additive).
- Domain separation remains intact (issuance on www.vraimony.com; verify on verify.vraimony.com).
- Defensive Mode is explicit: no silent downgrades; responses include
reason_code.
Non-official compatibility note
This hub documents compatibility and integrity checks. It does not certify identity, delivery/condition, or legal admissibility.
Reality Audit
—
ERF conformance is governed by the ERF Foundation.
The ERF Foundation maintains the specification, test vectors, and Quality Stop rules. Conformance means your records follow the open standard — not a proprietary implementation. Additive-only backward-compat contract: existing records remain valid indefinitely.
ERF is designed for EU digital identity transition.
W3C Verifiable Credentials export (optional layer), ed25519 signing, independent timestamp anchoring, and open backward-compat contract — aligned with eIDAS 2.0 requirements from 2027.