A source-carried record
A Memory Crystal retains the result and the original evidence included in its declared scope. It is useful because the source can travel with the saved object, instead of leaving only a screenshot or a link to a changing page.
Save what is already loaded
The public Ledger save uses the records and proofs already held in that view. Saving does not need another inventory fetch simply to reconstruct the visible result. The export should state its actual included scope rather than claim unseen history.
Local save and hosted retention
A local Ledger export is a file saved on your device. It does not by itself mean a cloud upload, remote admission or permanent hosting. A hosted byte service has its own availability, admission and retention evidence; a reachable URL cannot establish those properties.
Reopen and inspect
Keep the original file intact and use a matching supported reader. A reader checks the carried bytes, source relationships and relevant schema. A beautiful cover image is presentation; integrity and continuity come from the evidence inside the original.
Know what is retained
Private account identity, public Ledger evidence and an explicitly shared transaction have different disclosure scopes. Save and share only the intended source. An export is not spend authority, a substitute for device-bound Note custody or a promise that every private account event is included.
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.