Full package when needed
The secure export flow can still generate the real file when the user needs it.
Privacy-aware exports
Redacted export history for sensitive tax records should be the default, not the nice extra.
Some export flows need sensitive details. That does not mean the normal history screen should keep every private identifier around forever. A cleaner design is to generate the full package when needed and keep the stored history lighter by default.
That is the idea behind redacted export history in InEx Ledger.
There is a difference between proving an export happened and storing everything about it forever.
Lighter stored history
The retained history can keep status, dates, and verification context without exposing full sensitive fields by default.
Stale-state awareness
If the underlying data changes later, the snapshot can be marked stale so old exports are not mistaken for current truth.
Use the full export when needed. Keep the saved trail cleaner by default.
That is simply a better default for sensitive tax records.