The standard of the proof-native economy
The open-source software, a proof-native operation and an online service have distinct terms. Understand the scope you are using and the action you authorize.
The supplied implementation and documentation are distributed under the published GPLv3 license, with the existing notices and separately stated component terms. The source distribution explains reproduction and attribution. The software license is distinct from a hosted service or a financial agreement.
Use only identities, originals and operations you are authorized to control. Keep private authority secure. A username, public proof or retained display does not grant a new person permission to spend, transfer or disclose private information.
Review the actual amount, recipient, quote, provider terms and subscription terms in the relevant operation. Connected services retain their published terms and applicable mandatory rights. This standard page does not issue a new bank charter, deposit-insurance commitment, custody guarantee or universal redemption right.
A verification result establishes the assertions covered by its exact format and rules. Physical custody, legal rights, current unspentness and successful financial execution each require their own evidence. Retain originals and recover uncertain attempts under the supported contract.
Source. Authority. Continuity.
The original carries the proof. The standard preserves its identity, ownership and supported history. Receiz provides the reality-grade infrastructure through its SDK, MCP and AI Skills.
Clear scope. Exact meaning.
No. Account access, proof inspection and financial approval are separate. A transaction uses its existing exact authorization and confirmation path.
Use the support route with the relevant original reference. The applicable service, order or subscription terms govern that service; the open-source license governs the supplied software.
Reality-grade banking