Shared File Processing and Deferred Cleanup

Context

Pictures and private files must survive refused saves while eventually releasing storage no record uses.

Decision

Assets are prepared before record saves, attached within them and settled later by scheduled, reference-aware cleanup.

Alternatives Considered

Write raw storage references directly. Unprepared references would bypass lifecycle checks and cleanup tracking.

Delete replaced assets before committing the save. A rollback could leave the retained record referring to a removed file.

Consequences

Asset guards require references prepared for the saving record. Individual cleanup failures retry and eventually reach operator review. The console’s shared upload interaction remains deferred.