RECEIZ
What is a receiz?
A proof object: an original file carrying its own verification material. You can keep it, share it, and verify it independently.
A profile presents it. A player opens its media. A Twin helps people explore it. Those experiences use the same source; they do not become a new original. Verified additions extend its history without rewriting what came before.
The file verifies itself. Verify links (/v) are optional public convenience for that same file.
Proof and settlement: the exact authority model
Receiz is a proof-native artifact system: original bytes and embedded proof establish verification authority. Profiles, links, sessions, and server responses present or distribute that truth; they do not replace it. Every trust claim is mapped to code and evidence artifacts.
Settlement authority is append-only ledger replay over persisted integer value fields and deterministic rate math.
Flow: Record → Seal → Share → Verify.
Keep the evidence.
Let anyone check it.
What you preserved. When you sealed it. The proof stays inside the original you keep.
From your file to proof you can carry.
Start with the exact document, image, or other file you want to preserve.
Illustrated process. No file or account is changed here.
What do I save, and how do I check it?
After sealing, choose Save file. Keep the complete sealed file or package shown in the download panel, including its proof. A screenshot or a copied link is not that file.
Open the saved file in Verify. For an independent offline check, save the Offline Verifier HTML too. Open it locally, disconnect, and select your sealed file.
The check establishes the preserved content and sealing coordinate. It does not turn every statement inside the content into an observed fact. The first seal also carries creator and initial ownership; later verified handoffs preserve that history.
Keep the complete file.
Check its proof without an account.
- 1.(noun) A verifiable record of anything. Proof in the file.Example: “Send me the receiz.”
- 2.(verb) To create a verifiable record that can be checked later and cannot be changed.Example: “Payment requires a receiz.”
Beginner quick start
Start here for instant clarity. Open the expert section only when you need implementation depth.
Core definition
What Receiz is in one pass: file + match = verified.
How to use
Everyday flows: record moments, seal files/folders, share, verify, download.
Verification model
Plain-language checks: what passes, what fails, and why screenshots fail.
Front door and discovery
How public identity expands in Receiz.
Accounts and storage
Record, Seal, and Verify do not require accounts. Authenticated Receiz identity includes authorship, signing, receiving, ownership, custody, and business entity tools. Custom domains begin at Business.
Plans and upgrade
Free includes the proof, custody, identity, and ownership primitives. Premium is intelligence that stays with you, knows your work, and evolves with it. Business keeps the buyer journey on your domain. Automation keeps opportunities moving without waiting on you.
WireProof and API
WireProof turns outbound payments into sealed proof files. Automation keeps outreach, leads, introductions, APIs, webhooks, and workflows moving.
Login with Receiz ID
Passkey-first account access with magic-link fallback under one identity.
Institutions
How this supports audit, retention, and cross-party workflows.
Settlement authority
Deterministic custody math, replay-safe fields, and verified offline-note redemption.
Timestamp and pulse
The proof carries when it was sealed. Kai pulse is its causal coordinate; the timestamp is a readable reference.
Technical specification (expert)
For builders: verification guarantees and threat boundaries, without implementation leakage.
Choose the path.
Start from the file, open a live surface, or move the relationship onto your domain.