A stated scope
Conformance evaluates an implementation against an identified contract and version. State the exact capability being assessed: source reading, ownership continuity, connected execution, qualified local custody or another defined profile. No result silently expands to every capability an institution offers.
Normative sources
Use the pinned Receiz schemas, registry, primitive contracts and matching implementation as the source of exact protocol requirements. These pages explain the integration; they do not invent a competing issuer or amend the pinned financial rules through marketing language.
Evidence before a verdict
A conforming result requires the complete applicable checks and required evidence. A reproduced failure is nonconforming within that assessed scope. Missing evidence is not assessed or not demonstrated. Out of scope means the capability was excluded, not that an institution declined adoption.
Adversarial cases
Assessment includes altered bytes, forged participants, changed amount or split, stale predecessors, replay, rollback, concurrent claims and interrupted execution. Test unknown namespaces and incomplete lineage too. A happy-path demo cannot replace evidence that these cases are refused.
Device custody
Continuous offline creation and onward transfer require non-exportable authority and irreversible, independently verifiable consumption bound to the exact predecessor, value and recipient. Writable browser storage, a derivation key, locks or a timestamp cannot establish that property alone.
Independent receiving
An independent receiver needs exact-byte sources, matching schemas, a stated trust policy and a reproducible verification result. Reference tests use declared fixtures. They do not automatically qualify a physical device, production funds or a separately deployed service.
The same rule for this implementation
Bankeiz’s release evidence must state what passed, what failed and what remains unassessed. A protocol-pinned report does not grant spend authority, legal recognition or universal certification. Publish corrections and rerun affected checks when implementation or policy changes.
Method, sources and assessment
This explanation describes the supported implementation. Exact protocol requirements come from the pinned Receiz contracts and original sources. A reference result does not qualify a production deployment or a physical device.