A specific handover
The authorized operation binds the object, predecessor and intended recipient. Changing those fields changes the action that must be verified. The resulting proof records the supported change rather than relying on an informal message or an updated profile label.
What the recipient keeps
The recipient retains the original and its carried history. The reader can inspect the previous source, authorized transition and new owner. Media access and a transferable right may have different scopes; the object’s actual terms determine what was conveyed.
Value at the moment
Where supported inputs exist, the Ledger reconstructs a card or other supported object’s value at its transfer pulse and shows its current valuation separately. That comparison is a valuation change, not evidence of a sale price or payment unless a financial record establishes one.
Avoid competing claims
Replay and stale predecessors must be rejected under the relevant execution rules. Connected execution and qualified protected offline custody establish exclusivity through different mechanisms. An ordinary timestamp or duplicate file cannot replace either mechanism.
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.